diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x.json b/i18n/de/docusaurus-plugin-content-docs/version-7.x.json
new file mode 100644
index 000000000..3a82dac87
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x.json
@@ -0,0 +1,398 @@
+{
+  "version.label": {
+    "message": "rolling",
+    "description": "The label for version current"
+  },
+  "sidebar.user.category.Manage Files and Folders": {
+    "message": "Verwalten von Dateien und Ordnern",
+    "description": "The label for category 'Manage Files and Folders' in sidebar 'user'"
+  },
+  "sidebar.user.category.Working in teams with Spaces": {
+    "message": "Arbeiten im Team mit Spaces",
+    "description": "The label for category 'Working in teams with Spaces' in sidebar 'user'"
+  },
+  "sidebar.user.category.User Interface and Navigation": {
+    "message": "Benutzeroberfläche und Navigation",
+    "description": "The label for category 'User Interface and Navigation' in sidebar 'user'"
+  },
+  "sidebar.user.category.Administration of OpenCloud": {
+    "message": "Administration von OpenCloud",
+    "description": "The label for category 'Administration of OpenCloud' in sidebar 'user'"
+  },
+  "sidebar.user.category.Roles": {
+    "message": "Rollen",
+    "description": "The label for category 'Roles' in sidebar 'user'"
+  },
+  "sidebar.user.category.OpenCloud Desktop": {
+    "message": "OpenCloud Desktop",
+    "description": "The label for category 'OpenCloud Desktop' in sidebar 'user'"
+  },
+  "sidebar.admin.category.Getting Started": {
+    "message": "Getting Started",
+    "description": "The label for category 'Getting Started' in sidebar 'admin'"
+  },
+  "sidebar.admin.category.Other": {
+    "message": "Other",
+    "description": "The label for category 'Other' in sidebar 'admin'"
+  },
+  "sidebar.admin.category.Configuration": {
+    "message": "Configuration",
+    "description": "The label for category 'Configuration' in sidebar 'admin'"
+  },
+  "sidebar.admin.category.Maintenance": {
+    "message": "Maintenance",
+    "description": "The label for category 'Maintenance' in sidebar 'admin'"
+  },
+  "sidebar.admin.category.Resources": {
+    "message": "Resources",
+    "description": "The label for category 'Resources' in sidebar 'admin'"
+  },
+  "sidebar.dev.category.Development": {
+    "message": "Development",
+    "description": "The label for category 'Development' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Testing": {
+    "message": "Testing",
+    "description": "The label for category 'Testing' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Extension System": {
+    "message": "Extension System",
+    "description": "The label for category 'Extension System' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Extension Types": {
+    "message": "Extension Types",
+    "description": "The label for category 'Extension Types' in sidebar 'dev'"
+  },
+  "sidebar.user.category.OpenCloud iOS App": {
+    "message": "OpenCloud iOS App",
+    "description": "The label for category 'OpenCloud iOS App' in sidebar 'user'"
+  },
+  "sidebar.user.category.Common functionality": {
+    "message": "Allgemeine Funktionen",
+    "description": "The label for category 'Common functionality' in sidebar 'user'"
+  },
+  "sidebar.admin.category.Container": {
+    "message": "Container",
+    "description": "The label for category 'Container' in sidebar 'admin'"
+  },
+  "sidebar.admin.category.Authentication and Identity Management": {
+    "message": "Authentication and Identity Management",
+    "description": "The label for category 'Authentication and Identity Management' in sidebar 'admin'"
+  },
+  "sidebar.admin.category.Storage": {
+    "message": "Storage",
+    "description": "The label for category 'Storage' in sidebar 'admin'"
+  },
+  "sidebar.admin.category.Upgrade": {
+    "message": "Upgrade",
+    "description": "The label for category 'Upgrade' in sidebar 'admin'"
+  },
+  "sidebar.user.category.Desktop Client for Windows": {
+    "message": "Desktop Client for Windows",
+    "description": "The label for category 'Desktop Client for Windows' in sidebar 'user'"
+  },
+  "sidebar.user.category.Desktop Client for Windows.link.generated-index.description": {
+    "message": "OpenCloud Desktop Client for Windows.",
+    "description": "The generated-index page description for category 'Desktop Client for Windows' in sidebar 'user'"
+  },
+  "sidebar.user.category.Desktop Client for MacOS": {
+    "message": "Desktop Client for MacOS",
+    "description": "The label for category 'Desktop Client for MacOS' in sidebar 'user'"
+  },
+  "sidebar.user.category.Desktop Client for MacOS.link.generated-index.description": {
+    "message": "OpenCloud Desktop Client for MacOS.",
+    "description": "The generated-index page description for category 'Desktop Client for MacOS' in sidebar 'user'"
+  },
+  "sidebar.user.category.Desktop Client for Linux": {
+    "message": "Desktop Client for Linux",
+    "description": "The label for category 'Desktop Client for Linux' in sidebar 'user'"
+  },
+  "sidebar.user.category.Desktop Client for Linux.link.generated-index.description": {
+    "message": "OpenCloud Desktop Client for Linux.",
+    "description": "The generated-index page description for category 'Desktop Client for Linux' in sidebar 'user'"
+  },
+  "sidebar.user.category.Common functionality.link.generated-index.description": {
+    "message": "Common functionalities for the OpenCloud Desktop Client.",
+    "description": "The generated-index page description for category 'Common functionality' in sidebar 'user'"
+  },
+  "sidebar.user.category.ios-general": {
+    "message": "Allgemein",
+    "description": "The label for category 'General' in sidebar 'user'"
+  },
+  "sidebar.user.category.ios-general.link.generated-index.description": {
+    "message": "Tutorials about installing, setup and overview of the OpenCloud iOS App.",
+    "description": "The generated-index page description for category 'General' in sidebar 'user'"
+  },
+  "sidebar.user.category.ios-overview": {
+    "message": "Übersicht",
+    "description": "The label for category 'Overview' in sidebar 'user'"
+  },
+  "sidebar.user.category.ios-overview.link.generated-index.description": {
+    "message": "Overview of the user interface of the OpenCloud iOS App.",
+    "description": "The generated-index page description for category 'Overview' in sidebar 'user'"
+  },
+  "sidebar.user.category.ios-files-folders": {
+    "message": "Dateien und Ordner",
+    "description": "The label for category 'Files and Folders' in sidebar 'user'"
+  },
+  "sidebar.user.category.ios-files-folders.link.generated-index.description": {
+    "message": "Tutorials for managing your files and folders in the OpenCloud iOS App.",
+    "description": "The generated-index page description for category 'Files and Folders' in sidebar 'user'"
+  },
+  "sidebar.user.category.ios-shares": {
+    "message": "Teilen",
+    "description": "The label for category 'Shares' in sidebar 'user'"
+  },
+  "sidebar.user.category.ios-shares.link.generated-index.description": {
+    "message": "Anleitungen zum Teilen von Dateien und Ordner in der OpenClous iOS App.",
+    "description": "The generated-index page description for category 'Shares' in sidebar 'user'"
+  },
+  "sidebar.user.category.OpenCloud Android App": {
+    "message": "OpenCloud Android App",
+    "description": "The label for category 'OpenCloud Android App' in sidebar 'user'"
+  },
+  "sidebar.user.category.android-general": {
+    "message": "Allgemein",
+    "description": "The label for category 'General' in sidebar 'user'"
+  },
+  "sidebar.user.category.android-general.link.generated-index.description": {
+    "message": "Tutorials about installing, setup and overview of the OpenCloud Android App.",
+    "description": "The generated-index page description for category 'General' in sidebar 'user'"
+  },
+  "sidebar.user.category.android-overview": {
+    "message": "Übersicht",
+    "description": "The label for category 'Overview' in sidebar 'user'"
+  },
+  "sidebar.user.category.android-overview.link.generated-index.description": {
+    "message": "Overview of the user interface of the OpenCloud Android App.",
+    "description": "The generated-index page description for category 'Overview' in sidebar 'user'"
+  },
+  "sidebar.user.category.android-files-folders": {
+    "message": "Dateien und Ordner",
+    "description": "The label for category 'Files and Folders' in sidebar 'user'"
+  },
+  "sidebar.user.category.android-files-folders.link.generated-index.description": {
+    "message": "Tutorials for managing your files and folders in the OpenCloud Android App.",
+    "description": "The generated-index page description for category 'Files and Folders' in sidebar 'user'"
+  },
+  "sidebar.user.category.android-shares": {
+    "message": "Teilen",
+    "description": "The label for category 'Shares' in sidebar 'user'"
+  },
+  "sidebar.user.category.android-shares.link.generated-index.description": {
+    "message": "Tutorials about creating shares the OpenCloud Android App.",
+    "description": "The generated-index page description for category 'Shares' in sidebar 'user'"
+  },
+  "sidebar.dev.category.Server": {
+    "message": "Server",
+    "description": "The label for category 'Server' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Apis": {
+    "message": "Apis",
+    "description": "The label for category 'Apis' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.HTTP": {
+    "message": "HTTP",
+    "description": "The label for category 'HTTP' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.LibreGraph": {
+    "message": "LibreGraph",
+    "description": "The label for category 'LibreGraph' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Configuration": {
+    "message": "Configuration",
+    "description": "The label for category 'Configuration' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Services": {
+    "message": "Services",
+    "description": "The label for category 'Services' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Activitylog": {
+    "message": "Activitylog",
+    "description": "The label for category 'Activitylog' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Antivirus": {
+    "message": "Antivirus",
+    "description": "The label for category 'Antivirus' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.App-provider": {
+    "message": "App-provider",
+    "description": "The label for category 'App-provider' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.App-registry": {
+    "message": "App-registry",
+    "description": "The label for category 'App-registry' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Audit": {
+    "message": "Audit",
+    "description": "The label for category 'Audit' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Auth-app": {
+    "message": "Auth-app",
+    "description": "The label for category 'Auth-app' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Auth-basic": {
+    "message": "Auth-basic",
+    "description": "The label for category 'Auth-basic' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Auth-bearer": {
+    "message": "Auth-bearer",
+    "description": "The label for category 'Auth-bearer' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Auth-machine": {
+    "message": "Auth-machine",
+    "description": "The label for category 'Auth-machine' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Auth-service": {
+    "message": "Auth-service",
+    "description": "The label for category 'Auth-service' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Clientlog": {
+    "message": "Clientlog",
+    "description": "The label for category 'Clientlog' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Collaboration": {
+    "message": "Collaboration",
+    "description": "The label for category 'Collaboration' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Eventhistory": {
+    "message": "Eventhistory",
+    "description": "The label for category 'Eventhistory' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Frontend": {
+    "message": "Frontend",
+    "description": "The label for category 'Frontend' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Gateway": {
+    "message": "Gateway",
+    "description": "The label for category 'Gateway' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Graph": {
+    "message": "Graph",
+    "description": "The label for category 'Graph' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Groups": {
+    "message": "Groups",
+    "description": "The label for category 'Groups' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Idm": {
+    "message": "Idm",
+    "description": "The label for category 'Idm' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Idp": {
+    "message": "Idp",
+    "description": "The label for category 'Idp' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Invitations": {
+    "message": "Invitations",
+    "description": "The label for category 'Invitations' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Nats": {
+    "message": "Nats",
+    "description": "The label for category 'Nats' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Notifications": {
+    "message": "Notifications",
+    "description": "The label for category 'Notifications' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Ocm": {
+    "message": "Ocm",
+    "description": "The label for category 'Ocm' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Ocs": {
+    "message": "Ocs",
+    "description": "The label for category 'Ocs' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Policies": {
+    "message": "Policies",
+    "description": "The label for category 'Policies' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Postprocessing": {
+    "message": "Postprocessing",
+    "description": "The label for category 'Postprocessing' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Proxy": {
+    "message": "Proxy",
+    "description": "The label for category 'Proxy' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Search": {
+    "message": "Search",
+    "description": "The label for category 'Search' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Settings": {
+    "message": "Settings",
+    "description": "The label for category 'Settings' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Sharing": {
+    "message": "Sharing",
+    "description": "The label for category 'Sharing' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Sse": {
+    "message": "Sse",
+    "description": "The label for category 'Sse' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Storage-publiclink": {
+    "message": "Storage-publiclink",
+    "description": "The label for category 'Storage-publiclink' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Storage-shares": {
+    "message": "Storage-shares",
+    "description": "The label for category 'Storage-shares' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Storage-system": {
+    "message": "Storage-system",
+    "description": "The label for category 'Storage-system' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Storage-users": {
+    "message": "Storage-users",
+    "description": "The label for category 'Storage-users' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Thumbnails": {
+    "message": "Thumbnails",
+    "description": "The label for category 'Thumbnails' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Userlog": {
+    "message": "Userlog",
+    "description": "The label for category 'Userlog' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Users": {
+    "message": "Users",
+    "description": "The label for category 'Users' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.dev-server-services-web": {
+    "message": "Web",
+    "description": "The label for category 'Web' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Webdav": {
+    "message": "Webdav",
+    "description": "The label for category 'Webdav' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Webfinger": {
+    "message": "Webfinger",
+    "description": "The label for category 'Webfinger' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.dev-web": {
+    "message": "Web",
+    "description": "The label for category 'Web' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Development.link.generated-index.description": {
+    "message": "👩‍💻 Development",
+    "description": "The generated-index page description for category 'Development' in sidebar 'dev'"
+  },
+  "sidebar.dev.category.Testing.link.generated-index.description": {
+    "message": "✅ Testing",
+    "description": "The generated-index page description for category 'Testing' in sidebar 'dev'"
+  },
+  "sidebar.user.category.Share files and folders": {
+    "message": "Dateien und Ordner teilen",
+    "description": "The label for category 'Share files and folders' in sidebar 'user'"
+  },
+  "sidebar.admin.category.Docker Compose": {
+    "message": "Docker Compose",
+    "description": "The label for category 'Docker Compose' in sidebar 'admin'"
+  },
+  "sidebar.admin.category.Collabora": {
+    "message": "Collabora",
+    "description": "The label for category 'Collabora' in sidebar 'admin'"
+  }
+}
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/_category_.json b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/_category_.json
new file mode 100644
index 000000000..8284cba06
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/_category_.json
@@ -0,0 +1,8 @@
+{
+  "label": "Administration von OpenCloud",
+  "position": 10,
+  "link": {
+    "type": "doc",
+    "id": "admin-overview"
+  }
+}
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/app-tokens.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/app-tokens.md
new file mode 100644
index 000000000..c18b5d660
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/app-tokens.md
@@ -0,0 +1,74 @@
+---
+sidebar_position: 2
+id: app-tokens
+title: App Tokens
+description: App Tokens in OpenCLoud
+draft: false
+---
+
+# App-Tokens
+
+App-Tokens ermöglichen es Ihnen, externe Apps und Dienste (z. B. WebDAV-Clients) zu verbinden, ohne Ihr Hauptpasswort zu verwenden.
+
+Dies verbessert die Sicherheit auf mehrere Arten:
+
+- Ihr Login-Passwort muss nicht an Drittanbieter-Anwendungen weitergegeben werden.
+- App-Tokens können widerrufen werden. Wenn Sie befürchten, dass ein Token kompromittiert wurde, löschen Sie es einfach.
+- App-Tokens können ein Ablaufdatum haben. Das reduziert potenzielle Angriffsflächen.
+
+Zusätzlich zur erhöhten Sicherheit verbessern App-Tokens auch die Kompatibilität mit Drittanbieter-Anwendungen. Viele
+Anwendungen unterstützen moderne Login-Verfahren wie OpenID Connect nicht und akzeptieren nur Standard-Logins mit Benutzername
+und Passwort. Ihr Benutzername in Kombination mit einem App-Token dient genau diesem Zweck.
+
+:::important
+App-Tokens ermöglichen Drittanbieter-Anwendungen Zugriff auf all Ihre Daten. Erstellen Sie daher
+für jede Anwendung ein eigenes App-Token und wählen Sie ein angemessenes Ablaufdatum.  
+Wenn Sie keinen vollständigen Zugriff gewähren möchten, verwenden Sie stattdessen einen öffentlichen Link.
+:::
+
+## App-Token erstellen
+
+- Gehen Sie in Ihren OpenCloud-Kontoeinstellungen zum Bereich „App-Tokens“.
+- Klicken Sie auf „+ Neu“, um ein neues Token zu erstellen.
+
+  <img src={require("./img/app-tokens/create.png").default} alt="Create App Token" width="400"/>
+
+- Geben Sie einen Namen für das Token ein (z. B. „WebDAV Client“).
+- Wählen Sie ein Ablaufdatum, um die Sicherheit zu erhöhen.
+- Klicken Sie auf „Bestätigen“.
+
+  <img src={require("./img/app-tokens/enter-name.png").default} alt="Namen eingeben und Ablaufdatum wählen" width="400"/>
+
+## App-Token kopieren
+
+- Nach der Erstellung wird das Token nur ein einziges Mal angezeigt.
+- Kopieren Sie es sofort und bewahren Sie es sicher auf.
+
+  <img src={require("./img/app-tokens/copy-token.png").default} alt="Copy Token" width="400"/>
+
+:::note
+Wenn Sie das Token verlieren, müssen Sie es löschen und ein neues erstellen.
+:::
+
+## App-Token verwenden
+
+Sie können das Token nun anstelle Ihres Passworts verwenden, zum Beispiel bei:
+
+- WebDAV
+- Externen Apps
+- Drittanbieter-Diensten
+
+:::info
+Der Benutzername entspricht in der Regel dem Benutzernamen Ihres regulären Logins.  
+Wenn der Identity Provider jedoch im Autoprovisioning-Modus läuft, kann nur die UUID verwendet werden.  
+Diese finden Sie in der Übersicht der Einstellungen.
+:::
+
+## App-Token löschen
+
+Wenn ein Token nicht mehr benötigt wird:
+
+- Gehen Sie erneut zum Bereich „App-Tokens“.
+- Klicken Sie auf das Papierkorb-Symbol neben dem entsprechenden Token, um es zu entfernen.
+
+So stellen Sie sicher, dass ungenutzte Tokens nicht missbraucht werden können.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/app-tokens/copy-token.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/app-tokens/copy-token.png
new file mode 100644
index 000000000..1ea6fc6be
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/app-tokens/copy-token.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/app-tokens/create.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/app-tokens/create.png
new file mode 100644
index 000000000..7f57f552c
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/app-tokens/create.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/app-tokens/enter-name.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/app-tokens/enter-name.png
new file mode 100644
index 000000000..20c30bec1
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/app-tokens/enter-name.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/settings/admin-einstellungen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/settings/admin-einstellungen.png
new file mode 100644
index 000000000..1ed8d0d61
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/settings/admin-einstellungen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/settings/allgemein.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/settings/allgemein.png
new file mode 100644
index 000000000..e8fb7d142
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/settings/allgemein.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/settings/gruppen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/settings/gruppen.png
new file mode 100644
index 000000000..cdf911319
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/settings/gruppen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/settings/personen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/settings/personen.png
new file mode 100644
index 000000000..71a000f46
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/settings/personen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/settings/spaces.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/settings/spaces.png
new file mode 100644
index 000000000..0e234f214
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/settings/spaces.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/webdav/preferences.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/webdav/preferences.png
new file mode 100644
index 000000000..4f26606c1
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/webdav/preferences.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/webdav/webdav-url.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/webdav/webdav-url.png
new file mode 100644
index 000000000..4cea59fcb
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/img/webdav/webdav-url.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/index.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/index.md
new file mode 100644
index 000000000..4aa99ed0a
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/index.md
@@ -0,0 +1,22 @@
+---
+sidebar_position: 0
+id: admin-overview
+title: Administration von OpenCloud
+---
+
+# Administration von OpenCloud
+
+Dieser Abschnitt erklärt die Administrationsfunktionen in OpenCloud. Je nach Ihren Berechtigungen können Sie
+Kontoeinstellungen verwalten, Benutzer, Gruppen und Spaces administrieren, App-Tokens erstellen und externe Werkzeuge
+wie WebDAV-Clients anbinden.
+
+## In diesem Abschnitt
+
+- [Einstellungen](./settings.md)  
+  Rufen Sie den Administrationsbereich auf und verwalten Sie Benutzer, Gruppen und Spaces, je nach Ihren Berechtigungen.
+
+- [App-Tokens](./app-tokens.md)  
+  Erstellen und verwalten Sie sichere Tokens für Drittanbieter-Anwendungen und WebDAV-Clients.
+
+- [WebDAV](./web-dav.md)  
+  Verbinden Sie OpenCloud-Dateien und Spaces per WebDAV mit Ihrem Betriebssystem oder Dateimanager.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/settings.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/settings.md
new file mode 100644
index 000000000..688c75014
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/settings.md
@@ -0,0 +1,61 @@
+---
+sidebar_position: 1
+id: settings
+title: Einstellungen
+description: Einstellungen
+draft: false
+---
+
+# Überblick über den Admin-Bereich
+
+Im Admin-Bereich von OpenCloud haben Sie umfangreiche Verwaltungsoptionen für Ihre Organisation. Hier sind die wichtigsten Bereiche:
+<img src={require("./img/settings/admin-einstellungen.png").default} alt="Admin settings" width="400"/>
+
+## Allgemein
+
+- Versionsübersicht:
+  Im Bereich Allgemein kannst du Informationen zu deiner aktuellen OpenCloud-Version einsehen und prüfen, ob eine neuere Version verfügbar ist.
+  <img src={require("./img/settings/allgemein.png").default} alt="Admin general" width="1920"/>
+
+:::note
+Wenn ein sicherheitskritisches Upgrade verfügbar ist, können Administratoren zusätzlich eine Warnung unten links in der Weboberfläche sehen.
+Die Versionsprüfung kann von einem Administrator deaktiviert worden sein.
+Wenn diese Option ausgeschaltet ist, werden Informationen über neuere Versionen nicht angezeigt.
+:::
+
+## Benutzer
+
+- Übersicht der Benutzer
+  Hier haben Sie einen Überblick über alle Benutzer von Ihre OpenCloud.
+- Benutzer verwalten:
+  Abhängig von Ihren Benutzerverwaltungseinstellungen können Sie:
+  - Benutzer erstellen oder löschen
+  - Benutzer bearbeiten (z.B. Rechte oder Einstellungen ändern)
+  - Quota (Speicherplatz) von Benutzern ändern
+  - Benutzer in Gruppen hinzufügen oder entfernen
+  - Allow or prohibit logins (for individual users)
+    <img src={require("./img/settings/personen.png").default} alt="Admin users" width="1920"/>
+
+:::note
+Wenn OpenCloud mit einem externen IdP verbunden ist, können Sie die Benutzer hier weiterhin sehen, die Benutzerverwaltung muss jedoch im IdP erfolgen.
+:::
+
+## Gruppen
+
+- Übersicht der Gruppen
+  Hier können Sie die vorhandenen Gruppen Ihrer OpenCloud anzeigen.
+- Gruppen verwalten:
+  Sie können lokale Gruppen erstellen, bearbeiten oder löschen und Mitglieder hinzufügen oder entfernen.
+- Importierte Gruppen: Externe Gruppen, die über ein externes Benutzerverwaltungssystem importiert wurden, können hier nicht bearbeitet werden. Diese Gruppen sind mit einem Sperrsymbol  
+   gekennzeichnet, um anzuzeigen, dass sie gesperrt sind.
+  <img src={require("./img/settings/gruppen.png").default} alt="Admin groups" width="1920"/>
+
+## Spaces
+
+- Übersicht der Spaces
+  Hier sehen Sie alle vorhandenen Spaces in Ihrer OpenCloud.
+  - Space Management: Als Administrator haben Sie volle Rechte auf:
+  - Bearbeiten
+  - Deaktivieren oder aktivieren
+  - Löschen
+    <img src={require("./img/settings/spaces.png").default} alt="Admin spaces" width="1920"/>
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/web-dav.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/web-dav.md
new file mode 100644
index 000000000..2c1c4f4a5
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/admin/web-dav.md
@@ -0,0 +1,92 @@
+---
+sidebar_position: 3
+id: web-dav
+title: WebDAV
+description: Verbindung zu einem Space via WebDAV
+draft: false
+---
+
+# Verbindung zu einem Space via WebDAV herstellen
+
+Mit WebDAV kannst du OpenCloud-Spaces als Netzlaufwerke auf deinem Gerät einbinden und deine Dateien direkt über den Dateimanager verwalten – ganz ohne Browser.
+
+## Voraussetzungen
+
+- Ein gültiges OpenCloud-Konto mit aktivierter WebDAV-Information in den Einstellungen
+- Zugriff auf einen Space in OpenCloud
+- Ein WebDAV-Client (z. B. integrierte Unterstützung des Betriebssystems oder [Mountain Duck](https://mountainduck.io/))
+- (Optional, aber empfohlen) Ein App-Token  
+  → [So erstellst du ein App-Token](./app-tokens.md)
+
+## Schritt-für-Schritt-Anleitung
+
+### WebDAV-Informationen in der Oberfläche aktivieren
+
+Um die WebDAV-Informationen für deine Spaces anzuzeigen:
+
+- Gehe zu den Kontoeinstellungen
+- Aktiviere „WebDAV-Info in der Detailansicht anzeigen“
+
+  <img src={require("./img/webdav/preferences.png").default} alt="WebDAV-Info aktivieren" width="1920"/>
+
+### App-Token erstellen (falls erforderlich)
+
+Einige WebDAV-Clients (insbesondere solche ohne OIDC-Unterstützung wie Mountain Duck) benötigen ein App-Token zur Authentifizierung.
+
+:::note
+Wir empfehlen aus Sicherheitsgründen die Verwendung eines App-Tokens anstelle deines Passworts.
+:::
+
+- Gehe zu Einstellungen > App-Tokens
+- Klicke auf „+ Neu“, gib einen Namen ein und wähle ein Ablaufdatum
+- Kopiere den Token sofort – er wird nur einmal angezeigt  
+  → [Siehe App-Token-Anleitung](./app-tokens.md)
+
+### WebDAV-URL abrufen
+
+Öffne das Info-Panel deines Spaces in der OpenCloud-Weboberfläche.
+
+Du findest dort einen Abschnitt „WebDAV“ – kopiere die vollständige URL. Diese sieht beispielsweise so aus:
+
+`https://cloud.example.de/remote.php/dav/spaces/12345678-abcd-efgh-ijkl-987654321000/`
+
+<img src={require("./img/webdav/webdav-url.png").default} alt="WebDAV-URL" width="1920"/>
+
+### Verbindung via WebDAV herstellen
+
+Stelle nun die Verbindung zu deinem Gerät über die WebDAV-URL her:
+
+- Benutzername: dein OpenCloud-Benutzername
+- Passwort: dein App-Token (oder Passwort, falls erlaubt)
+
+Du kannst je nach Betriebssystem unterschiedliche Clients verwenden:
+
+## Windows
+
+- Öffne den Datei-Explorer → Klicke auf „Dieser PC“ → Wähle „Netzlaufwerk verbinden“
+- Gib die WebDAV-URL ein
+- Authentifiziere dich mit Benutzername und App-Token
+
+## macOS
+
+- Wähle im Finder „Gehe zu“ > „Mit Server verbinden…“
+- Gib die WebDAV-URL ein
+- Melde dich mit deinen Zugangsdaten oder dem App-Token an
+
+## Linux
+
+- Nutze die Funktion „Mit Server verbinden“ deines Dateimanagers
+- Format der URL:  
+  `davs://cloud.beispiel.de/remote.php/dav/spaces/<SPACE-ID>/`
+
+:::note
+Nach erfolgreicher Verbindung verhält sich dein Space wie ein normaler Ordner.
+:::
+
+:::note
+
+- Wenn dein WebDAV-Client OIDC unterstützt, ist ein App-Token eventuell nicht erforderlich
+- Verwende immer `https://` für einen sicheren Zugriff
+- App-Tokens können jederzeit in den Kontoeinstellungen widerrufen werden
+
+:::
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/_category_.json b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/_category_.json
new file mode 100644
index 000000000..37b070912
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/_category_.json
@@ -0,0 +1,8 @@
+{
+  "label": "OpenCloud Android App",
+  "position": 8,
+  "link": {
+    "type": "doc",
+    "id": "android-app-overview"
+  }
+}
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/files-and-folders/create-rename-move.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/files-and-folders/create-rename-move.md
new file mode 100644
index 000000000..e8e0fbed0
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/files-and-folders/create-rename-move.md
@@ -0,0 +1,85 @@
+---
+sidebar_position: 1
+id: create-rename-move
+title: Erstellen - Umbenennen - Verschieben
+description: Erstellen - Umbenennen - Verschieben
+draft: false
+---
+
+# Erstellen, Umbenennen und Verschieben von Dateien und Ordnern
+
+Mit der OpenCloud Android-App können Sie Ihre Inhalte ganz einfach verwalten. Sie können neue Ordner und Dateien erstellen, Elemente umbenennen und an andere Speicherorte verschieben – direkt von Ihrem Android-Smartphone oder -Tablet aus.
+
+## Dateien und Ordner erstellen
+
+Tippen Sie auf das „+“-Symbol unten rechts.
+
+<img src={require("../img/files-and-folders/create-rename-move-android/create-new.png").default} alt="Neu erstellen" height="400"/>
+
+Wählen Sie im Menü aus, was Sie erstellen möchten:
+
+### Ordner erstellen
+
+- Tippen Sie auf „Neuer Ordner“
+- Geben Sie einen Namen für Ihren Ordner ein
+- Tippen Sie auf „OK“
+
+<img src={require("../img/files-and-folders/create-rename-move-android/create-folder.png").default} alt="Ordner erstellen" height="400"/>
+
+### Dokument erstellen (erfordert Collabora)
+
+Wenn Collabora Online in Ihrer OpenCloud-Instanz aktiviert ist:
+
+- Tippen Sie auf „Neues Dokument“
+- Wählen Sie den Dokumenttyp (Text, Tabelle, Präsentation)
+- Geben Sie einen Dateinamen ein und bestätigen Sie
+
+<img src={require("../img/files-and-folders/create-rename-move-android/choose-file-type.png").default} alt="Dateityp wählen" height="400"/>
+
+Das Dokument wird in einem integrierten Browserfenster mit **Collabora** zur Bearbeitung geöffnet.
+
+<img src={require("../img/files-and-folders/create-rename-move-android/open-collabora.png").default} alt="Collabora öffnen" height="400"/>
+<img src={require("../img/files-and-folders/create-rename-move-android/edit-collabora.png").default} alt="Collabora bearbeiten" height="400"/>
+
+## Dateien oder Ordner umbenennen
+
+So benennen Sie eine Datei oder einen Ordner in der OpenCloud Android-App um:
+
+- Tippen Sie auf die „drei Punkte (…)“ neben dem Element, das Sie umbenennen möchten
+
+<img src={require("../img/files-and-folders/create-rename-move-android/three-dots.png").default} alt="Drei-Punkte-Menü" height="400"/>
+
+- Wählen Sie „Umbenennen“ aus dem Menü
+
+<img src={require("../img/files-and-folders/create-rename-move-android/select-rename.png").default} alt="Umbenennen wählen" height="400"/>
+
+- Geben Sie den neuen Namen für die Datei oder den Ordner ein
+
+<img src={require("../img/files-and-folders/create-rename-move-android/enter-rename.png").default} alt="Neuen Namen eingeben" height="400"/>
+
+- Tippen Sie auf „OK“, um die Änderungen zu übernehmen
+
+<img src={require("../img/files-and-folders/create-rename-move-android/tap-ok.png").default} alt="OK tippen" height="400"/>
+<img src={require("../img/files-and-folders/create-rename-move-android/new-name-applied.png").default} alt="Neuer Name übernommen" height="400"/>
+
+Der neue Name wird sofort gespeichert.
+
+## Dateien oder Ordner verschieben
+
+So verschieben Sie eine Datei oder einen Ordner in der OpenCloud Android-App:
+
+- Tippen Sie auf die „drei Punkte (…)“ neben der Datei oder dem Ordner, die bzw. den Sie verschieben möchten
+
+<img src={require("../img/files-and-folders/create-rename-move-android/three-dots-move.png").default} alt="Drei-Punkte-Menü auswählen" height="400"/>
+
+- Wählen Sie „Verschieben“ oder „Kopieren“ aus dem Menü
+
+<img src={require("../img/files-and-folders/create-rename-move-android/select-move-or-copy.png").default} alt="Verschieben oder Kopieren wählen" height="400"/>
+
+Navigieren Sie zum Zielordner  
+Tippen Sie auf „Hierher verschieben“ oder „Hierher kopieren“
+
+<img src={require("../img/files-and-folders/create-rename-move-android/select-paste.png").default} alt="Einfügen auswählen" height="400"/>
+<img src={require("../img/files-and-folders/create-rename-move-android/file-moved.png").default} alt="Datei wurde verschoben" height="400"/>
+
+Die Datei oder der Ordner wird nun am neuen Speicherort angezeigt.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/files-and-folders/upload-make-available-offline.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/files-and-folders/upload-make-available-offline.md
new file mode 100644
index 000000000..c47cde205
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/files-and-folders/upload-make-available-offline.md
@@ -0,0 +1,65 @@
+---
+sidebar_position: 2
+id: upload-make-available-offline
+title: Hochladen - Offline verfügbar machen
+description: Dateien hochladen in Android
+draft: false
+---
+
+# Dateien hochladen in Android
+
+Mit der OpenCloud Android-App können Sie ganz einfach Dateien hochladen und für die Offline-Nutzung verfügbar machen.
+
+## Dateien hochladen
+
+### Gewünschten Ordner öffnen
+
+Navigieren Sie zu dem Ordner, in dem Sie eine Datei hochladen möchten.
+
+### Tippen Sie auf das „+“-Symbol unten rechts
+
+und wählen Sie „Hochladen“
+
+<img src={require("../img/files-and-folders/upload-make-available-offline-android/upload-plus-button.png").default} alt="Plus-Schaltfläche" height="400"/>
+
+### Upload-Option wählen
+
+Im Menü können Sie wählen:
+
+- „Hochladen“ – eine Datei aus dem Gerätespeicher hochladen
+- „Bild von Kamera“ – ein Foto oder Video mit der Kamera des Smartphones oder Tablets aufnehmen und hochladen
+
+<img src={require("../img/files-and-folders/upload-make-available-offline-android/upload-options.png").default} alt="Upload-Optionen" height="400"/>
+
+### Auswahl bestätigen
+
+Wählen Sie die Datei oder das Medium aus, das Sie hochladen möchten. Der Upload startet automatisch.
+
+## Dateien offline verfügbar machen
+
+Sie können Dateien offline verfügbar machen, damit Sie auch ohne Internetverbindung darauf zugreifen können.
+
+### Tippen Sie auf die drei Punkte (...) neben der Datei
+
+<img src={require("../img/files-and-folders/upload-make-available-offline-android/three-dots.png").default} alt="Drei-Punkte-Menü" height="400"/>
+
+### Wählen Sie „Offline verfügbar machen“
+
+Die Datei wird heruntergeladen und lokal auf Ihrem Gerät gespeichert.
+
+<img src={require("../img/files-and-folders/upload-make-available-offline-android/make-available-offline.png").default} alt="Offline verfügbar machen" height="400"/>
+
+:::info
+Offline-Dateien sind mit einem rosa Kreis mit weißem Häkchen markiert.
+:::
+
+<img src={require("../img/files-and-folders/upload-make-available-offline-android/marked-offline.png").default} alt="Als offline markiert" height="400"/>
+
+## Offline-Verfügbarkeit entfernen
+
+Um Speicherplatz freizugeben:
+
+- Tippen Sie auf die drei Punkte (...) bei einer offline gespeicherten Datei
+- Wählen Sie „Offline-Verfügbarkeit aufheben“
+
+Diese Funktionen helfen Ihnen, auch ohne Internet produktiv zu bleiben!
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/general/installation.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/general/installation.md
new file mode 100644
index 000000000..5e9a8d276
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/general/installation.md
@@ -0,0 +1,37 @@
+---
+sidebar_position: 1
+id: installation
+title: Installieren der Android App
+description: Installieren derOpenCloud Android app
+draft: false
+---
+
+# Installieren der OpenCloud Android app
+
+Anleitung zur Installation der OpenCloud Android-App.
+
+## Play Store
+
+Öffne den Play Store auf deinem Android-Smartphone oder Tablet.
+
+## OpenCloud
+
+Suche nach „OpenCloud“ oder klicke auf folgenden Link, um direkt zur App zu gelangen:
+
+[OpenCloud im Play Store](https://play.google.com/store/apps/details?id=eu.opencloud.android)
+
+<img src={require(".././img/installation/android-installation.png").default} alt="Android Installation" height="400"/>
+
+## Installieren
+
+Tippe auf „Installieren“, um die App herunterzuladen.
+
+## App Icon
+
+Nach der Installation findest du die OpenCloud-App auf deinem Startbildschirm.
+
+<img src={require(".././img/installation/icon-on-screen.png").default} alt="Icon" height="400"/>
+
+## Einrichten
+
+Öffne die App und folge den Anweisungen auf dem Bildschirm, um sie einzurichten.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/general/overview/account-fileslist.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/general/overview/account-fileslist.md
new file mode 100644
index 000000000..ca886c530
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/general/overview/account-fileslist.md
@@ -0,0 +1,61 @@
+---
+sidebar_position: 2
+id: account-fileslist
+title: Dateilisten-Menü
+description: Dateilisten-Menü
+draft: false
+---
+
+# Hier ist eine Übersicht über das Dateilisten-Menü der OpenCloud Android-App
+
+Dieser Abschnitt erklärt die zentralen Elemente der Benutzeroberfläche der OpenCloud Android-App und deren Funktionen.
+
+<img src={require("../../img/overview/fileslist.png").default} alt="Fileslist-Overview" style={{ width: '400px', marginRight: '60px' }} />
+
+## 1. Account Menu
+
+Bietet Zugriff auf die Kontoeinstellungen.
+
+## 2. Search
+
+Ermöglicht die Suche nach Dateien, Ordnern oder geteilten Elementen innerhalb der App.
+
+## 3. Manage Accounts
+
+Zeigt das aktive Konto an und ermöglicht das Hinzufügen eines weiteren Kontos.
+
+## 4. Sort by
+
+Ermöglicht das Sortieren von Dateien nach Name, Datum, Größe oder anderen Kriterien.
+
+## 5. View Mode
+
+Erlaubt das Umschalten zwischen verschiedenen Ansichtsmodi.
+
+## 6. Files List
+
+Zeigt den Inhalt des aktuellen Ordners als Liste von Dateien und Ordnern an.
+
+## 7. Add Button
+
+Öffnet Optionen zum Hochladen von Dateien, Erstellen von Ordnern oder Hinzufügen neuer Inhalte.
+
+## 8. Personal
+
+Ermöglicht den schnellen Wechsel zum persönlichen Bereich.
+
+## 9. Shares
+
+Ermöglicht den schnellen Wechsel zur Liste der geteilten Elemente.
+
+## 10. Spaces
+
+Ermöglicht den schnellen Wechsel zur Liste der Bereiche (Spaces).
+
+## 11. Uploads
+
+Ermöglicht den schnellen Wechsel zur Liste der Uploads.
+
+## 12. Offline
+
+Ermöglicht den schnellen Zugriff auf eine Liste von Dateien und Ordnern, die offline verfügbar sind.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/general/overview/account-overview.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/general/overview/account-overview.md
new file mode 100644
index 000000000..46b6235e6
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/general/overview/account-overview.md
@@ -0,0 +1,43 @@
+---
+sidebar_position: 1
+id: account-overview
+title: Account-Menü
+description: Account-Menü
+draft: false
+---
+
+# Account Menu
+
+Hier ist ein Überblick über das Kontomenü in der OpenCloud Android-App
+
+<img src={require("../../img/overview/account-1.png").default} alt="Account Menue Button" style={{ width: '300px', marginRight: '60px' }} />
+
+<img src={require("../../img/overview/account-2.png").default} alt="Account Menue" style={{ width: '300px', marginRight: '60px' }} />
+
+## 1. Account Menu Item
+
+Öffnet die Hauptoptionen und Einstellungen des Kontos.
+
+## 2. Active Account
+
+Zeigt an, welches Benutzerkonto derzeit aktiv ist.
+
+## 3. Settings Menu Item
+
+Öffnet die allgemeinen Einstellungen und Konfigurationsoptionen.
+
+## 4. Feedback Item
+
+Hier kannst du uns Feedback zu deiner Erfahrung mit der OpenCloud Android-App senden.
+
+## 5. Help Menu Item
+
+Hier findest du Links zu unserer Dokumentationsseite und weiteren Hilfeseiten.
+
+## 6. Privacy Policy Item
+
+Hier findest du den vollständigen Eintrag zu unserer Datenschutzrichtlinie.
+
+## 7. Used Quota
+
+Zeigt an, wie viel deines Speicherplatzes du bisher genutzt hast.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/general/set-up.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/general/set-up.md
new file mode 100644
index 000000000..e9c4ee774
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/general/set-up.md
@@ -0,0 +1,46 @@
+---
+sidebar_position: 2
+id: set-up
+title: Einrichten der OpenCloud Android App
+description: Einrichten der OpenCloud Android App
+draft: false
+---
+
+# Einrichtung deines OpenCloud-Kontos
+
+Nach der Installation der App kannst du jetzt dein OpenCloud-Konto einrichten.
+
+## Einrichtung starten
+
+- Wenn du die OpenCloud Android-App zum ersten Mal startest, erscheint folgender Bildschirm.
+
+  <img src={require(".././img/set-up/start-setup.png").default} alt="Einrichtung starten" height="400"/>
+
+- Um ein zusätzliches Konto einzurichten, tippe auf die Schaltfläche „Konten verwalten“ und wähle „Konto hinzufügen“.
+
+  <img src={require(".././img/set-up/additional-account.png").default} alt="Zusätzliches Konto" height="400"/>
+
+## Deine Server-URL eingeben
+
+- Gib die URL deines OpenCloud-Servers ein (z. B. `https://cloud.beispiel.de`)
+- Tippe auf „>“, um fortzufahren.
+
+  <img src={require(".././img/set-up/enter-server-url.png").default} alt="Server-URL eingeben" height="400"/>
+
+## Die Login-Seite
+
+- Die Login-Seite öffnet sich, und du musst deinen Benutzernamen und dein Passwort eingeben.
+- Tippe anschließend auf „Einloggen“.
+
+- Im folgenden Bildschirm gibst du der App die Berechtigung, auf deine Benutzerinformationen zuzugreifen und eine dauerhafte Verbindung zu deinem Konto herzustellen, indem du auf die Schaltfläche „Zulassen“ tippst.
+
+  <img src={require(".././img/set-up/open-login-page.png").default} alt="Login-Seite öffnen" height="400"/>
+  <img src={require(".././img/set-up/continue-sign-in.png").default} alt="Anmeldung fortsetzen" height="400"/>
+
+## Einrichtung abschließen
+
+Sobald der Login abgeschlossen ist, wird dein Konto zur App hinzugefügt.
+
+Dein OpenCloud-Konto ist jetzt vollständig eingerichtet und einsatzbereit!
+
+<img src={require(".././img/set-up/account-set-up.png").default} alt="Konto ist eingerichtet" height="400"/>
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/general/settings.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/general/settings.md
new file mode 100644
index 000000000..e4ec9d1ad
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/general/settings.md
@@ -0,0 +1,89 @@
+---
+sidebar_position: 4
+id: settings
+title: Einstellungen
+description: Einstellungen der OpenCloud Android App
+draft: false
+---
+
+# Einstellungen
+
+In den Einstellungen der Android-App können Änderungen vorgenommen werden, wie z. B.:
+
+- Sicherheit
+- Benachrichtigungen verwalten
+- Protokollierung
+- Erweiterte Einstellungen  
+  und mehr
+
+<img src={require(".././img/settings/settings.png").default} alt="Settings" width="400"/>
+
+## Userinterface
+
+### 1. Security
+
+Hier kannst du Sperren für den Zugriff auf die App festlegen und Berührungen mit anderen sichtbaren Fenstern zulassen.
+
+### 2. Manage notifications
+
+Hier kannst du Benachrichtigungen der OpenCloud Android-App zulassen.
+
+### 3. Logging
+
+Hier kannst du die Protokollierungsfunktion aktivieren oder deaktivieren und den Speicherort der Protokolldatei festlegen.
+
+### 4. Automatic picture uploads
+
+Hier kannst du Speicherort und Verhalten der automatisch hochgeladenen Bilder verwalten.
+
+### 5. Automatic video uploads
+
+Hier kannst du Speicherort und Verhalten der automatisch hochgeladenen Videos verwalten.
+
+### 6. Advanced
+
+Hier kannst du folgende Optionen einstellen:<br/>
+
+#### Show hidden files
+
+- Anzeige versteckter Dateien aktivieren oder deaktivieren.
+
+#### Delete local copies
+
+- Automatisch heruntergeladene Dateien, die nicht offline verfügbar sind, werden entfernt, wenn sie für eine bestimmte Zeit nicht verwendet wurden.
+
+### 7. More
+
+Hier kannst du folgende Optionen einstellen:<br/>
+
+#### Help
+
+- Hier findest du Links zu unserer Dokumentationsseite und zu Hilfethemen.
+
+#### Sync your contacts, calendars and tasks
+
+- Hier kannst du einstellen, welche Kontakte, Kalender und Aufgaben mit der OpenCloud Android-App synchronisiert werden.
+
+#### Access document provider
+
+- Vorgeschlagene App, um Dateien über den nativen Android-Dateibrowser zu durchsuchen.
+
+#### Send feedback
+
+- Hier kannst du uns Feedback zu deiner Erfahrung mit der OpenCloud Android-App senden.
+
+#### Recommend to a friend
+
+- Hier kannst du einen Link zum Herunterladen der Android-App weiterleiten.
+
+### 8. Privacy Policy
+
+Hier findest du den vollständigen Eintrag zu unserer Datenschutzrichtlinie.
+
+### 9. What's new in the latest version?
+
+Hier findest du Informationen zu Änderungen und Neuerungen in der neuesten Version der OpenCloud Android-App.
+
+### 10. App version
+
+Hier siehst du, welche App-Version verwendet wird.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/choose-file-type.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/choose-file-type.png
new file mode 100644
index 000000000..c332d51ac
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/choose-file-type.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/create-folder.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/create-folder.png
new file mode 100644
index 000000000..fe378e07f
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/create-folder.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/create-new.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/create-new.png
new file mode 100644
index 000000000..27f5c999f
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/create-new.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/edit-collabora.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/edit-collabora.png
new file mode 100644
index 000000000..a45531129
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/edit-collabora.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/enter-rename.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/enter-rename.png
new file mode 100644
index 000000000..bd21dc413
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/enter-rename.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/file-moved.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/file-moved.png
new file mode 100644
index 000000000..1e3e7882d
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/file-moved.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/new-name-applied.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/new-name-applied.png
new file mode 100644
index 000000000..9cd1a3bf7
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/new-name-applied.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/open-collabora.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/open-collabora.png
new file mode 100644
index 000000000..2cd160b02
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/open-collabora.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/select-move-or-copy.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/select-move-or-copy.png
new file mode 100644
index 000000000..7502f321e
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/select-move-or-copy.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/select-paste.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/select-paste.png
new file mode 100644
index 000000000..d4ad9ec67
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/select-paste.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/select-rename.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/select-rename.png
new file mode 100644
index 000000000..a7b912180
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/select-rename.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/tap-ok.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/tap-ok.png
new file mode 100644
index 000000000..e03c214c8
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/tap-ok.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/three-dots-move.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/three-dots-move.png
new file mode 100644
index 000000000..1e0a44267
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/three-dots-move.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/three-dots.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/three-dots.png
new file mode 100644
index 000000000..1e0a44267
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/three-dots.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/make-available-offline.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/make-available-offline.png
new file mode 100644
index 000000000..48deeab38
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/make-available-offline.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/marked-offline.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/marked-offline.png
new file mode 100644
index 000000000..4fcffecdb
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/marked-offline.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/three-dots.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/three-dots.png
new file mode 100644
index 000000000..081c1bf88
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/three-dots.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/upload-options.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/upload-options.png
new file mode 100644
index 000000000..1079de399
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/upload-options.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/upload-plus-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/upload-plus-button.png
new file mode 100644
index 000000000..cfabce3fd
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/upload-plus-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/installation/android-installation.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/installation/android-installation.png
new file mode 100644
index 000000000..b516c104e
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/installation/android-installation.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/installation/icon-on-screen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/installation/icon-on-screen.png
new file mode 100644
index 000000000..1d0422dec
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/installation/icon-on-screen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/overview/account-1.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/overview/account-1.png
new file mode 100644
index 000000000..c153b76aa
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/overview/account-1.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/overview/account-2.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/overview/account-2.png
new file mode 100644
index 000000000..f4415c9a0
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/overview/account-2.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/overview/fileslist.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/overview/fileslist.png
new file mode 100644
index 000000000..3a11d07e4
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/overview/fileslist.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/search/search-result.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/search/search-result.png
new file mode 100644
index 000000000..8bf41bec2
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/search/search-result.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/search/search-symbol.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/search/search-symbol.png
new file mode 100644
index 000000000..f5f78e601
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/search/search-symbol.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/search/searchbar.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/search/searchbar.png
new file mode 100644
index 000000000..2b85d863c
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/search/searchbar.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/set-up/account-set-up.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/set-up/account-set-up.png
new file mode 100644
index 000000000..6ca0dc7cd
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/set-up/account-set-up.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/set-up/additional-account.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/set-up/additional-account.png
new file mode 100644
index 000000000..639edd194
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/set-up/additional-account.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/set-up/continue-sign-in.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/set-up/continue-sign-in.png
new file mode 100644
index 000000000..6128f26e0
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/set-up/continue-sign-in.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/set-up/enter-server-url.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/set-up/enter-server-url.png
new file mode 100644
index 000000000..35d49b60d
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/set-up/enter-server-url.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/set-up/open-login-page.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/set-up/open-login-page.png
new file mode 100644
index 000000000..ac3243f44
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/set-up/open-login-page.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/set-up/start-setup.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/set-up/start-setup.png
new file mode 100644
index 000000000..cb68cc513
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/set-up/start-setup.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/settings/settings.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/settings/settings.png
new file mode 100644
index 000000000..fb087e6b3
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/settings/settings.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/invite/invite-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/invite/invite-menue.png
new file mode 100644
index 000000000..cf6edd318
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/invite/invite-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/invite/invite-option.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/invite/invite-option.png
new file mode 100644
index 000000000..2eeb23f15
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/invite/invite-option.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/invite/permissions.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/invite/permissions.png
new file mode 100644
index 000000000..bd1be6770
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/invite/permissions.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/invite/searchbar.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/invite/searchbar.png
new file mode 100644
index 000000000..cf83b2fb7
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/invite/searchbar.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/invite/shared-with.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/invite/shared-with.png
new file mode 100644
index 000000000..25e881a5b
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/invite/shared-with.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/invite/sharing-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/invite/sharing-button.png
new file mode 100644
index 000000000..2e025f7fb
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/invite/sharing-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/invite/three-dot-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/invite/three-dot-menue.png
new file mode 100644
index 000000000..667b47de3
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/invite/three-dot-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/create-link-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/create-link-button.png
new file mode 100644
index 000000000..aa0f502f6
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/create-link-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/create-link-options.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/create-link-options.png
new file mode 100644
index 000000000..77bff0c7b
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/create-link-options.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/created-link.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/created-link.png
new file mode 100644
index 000000000..6491ab9f4
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/created-link.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/expiration-date.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/expiration-date.png
new file mode 100644
index 000000000..3ff37f3ab
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/expiration-date.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/password.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/password.png
new file mode 100644
index 000000000..b949382dd
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/password.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/share-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/share-button.png
new file mode 100644
index 000000000..d2d3a4352
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/share-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/sharing-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/sharing-button.png
new file mode 100644
index 000000000..2e025f7fb
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/sharing-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/three-dot-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/three-dot-menue.png
new file mode 100644
index 000000000..667b47de3
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shares/links/three-dot-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shortcuts/create-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shortcuts/create-button.png
new file mode 100644
index 000000000..153f12615
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shortcuts/create-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shortcuts/created-shortcut.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shortcuts/created-shortcut.png
new file mode 100644
index 000000000..0e78f28f1
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shortcuts/created-shortcut.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shortcuts/plus-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shortcuts/plus-button.png
new file mode 100644
index 000000000..41268f1a8
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shortcuts/plus-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shortcuts/shortcut-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shortcuts/shortcut-menue.png
new file mode 100644
index 000000000..b3b0e52b6
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shortcuts/shortcut-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shortcuts/shortcut-name.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shortcuts/shortcut-name.png
new file mode 100644
index 000000000..e5869e75d
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shortcuts/shortcut-name.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shortcuts/url.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shortcuts/url.png
new file mode 100644
index 000000000..2b595881f
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/shortcuts/url.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/spaces/search-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/spaces/search-button.png
new file mode 100644
index 000000000..51cb9a766
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/spaces/search-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/spaces/search-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/spaces/search-menue.png
new file mode 100644
index 000000000..996affaef
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/spaces/search-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/spaces/spaces-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/spaces/spaces-button.png
new file mode 100644
index 000000000..49706c6b7
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/spaces/spaces-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/spaces/spaces-overview.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/spaces/spaces-overview.png
new file mode 100644
index 000000000..ca0964dca
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/spaces/spaces-overview.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/spaces/spaces-plus-symbol-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/spaces/spaces-plus-symbol-menue.png
new file mode 100644
index 000000000..44e50695e
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/spaces/spaces-plus-symbol-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/spaces/spaces-plus-symbol.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/spaces/spaces-plus-symbol.png
new file mode 100644
index 000000000..d6bcb82a4
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/img/spaces/spaces-plus-symbol.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/index.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/index.md
new file mode 100644
index 000000000..f3fb0795a
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/index.md
@@ -0,0 +1,30 @@
+---
+sidebar_position: 0
+id: android-app-overview
+title: OpenCloud Android App
+---
+
+# OpenCloud Android App
+
+Die OpenCloud Android App bietet mobilen Zugriff auf Ihre Dateien, Spaces und Freigaben. Sie ist für den schnellen
+Zugriff unterwegs ausgelegt und unterstützt die Einrichtung, Suche, Verknüpfungen und die Dateiverwaltung.
+
+## In diesem Abschnitt
+
+- [Allgemeines](./general/)  
+  Installieren Sie die App, richten Sie sie ein und lernen Sie die wichtigsten Bereiche und Einstellungen kennen.
+
+- [Dateien und Ordner](./files-and-folders/)  
+  Erstellen und bearbeiten Sie Inhalte, laden Sie Dateien hoch und machen Sie Elemente offline verfügbar.
+
+- [Spaces](./spaces.md)  
+  Arbeiten Sie mit Spaces und den verfügbaren Aktionen in Android.
+
+- [Suche](./search.md)  
+  Finden Sie Dateien und Ordner direkt in der Android App.
+
+- [Verknüpfungen](./shortcuts.md)  
+  Erstellen Sie Verknüpfungen zu Dateien oder Weblinks.
+
+- [Freigaben](./shares/)  
+  Laden Sie Personen ein und erstellen Sie Freigabelinks direkt in der Android App.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/search.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/search.md
new file mode 100644
index 000000000..7fca128dd
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/search.md
@@ -0,0 +1,29 @@
+---
+sidebar_position: 4
+id: search
+title: Suche
+description: Suche in der Android-App
+draft: false
+---
+
+# Suchfunktion
+
+Hier erklären wir, wie du die Suchfunktion in der OpenCloud Android-App verwendest.
+
+## Suchsymbol
+
+Wechsle in den Space, in dem du suchen möchtest, und tippe auf das Suchsymbol, um die Suchfunktion zu öffnen.
+
+<img src={require("./img/search/search-symbol.png").default} alt="Lupensymbol" width="300"/>
+
+## Suchleiste
+
+In der Suchleiste kannst du nach Datei- oder Ordnernamen suchen.
+
+<img src={require("./img/search/searchbar.png").default} alt="Suchleiste" width="300"/>
+
+## Suchergebnis
+
+In diesem Bereich werden die Suchergebnisse angezeigt.
+
+<img src={require("./img/search/search-result.png").default} alt="Suchergebnisse" width="300"/>
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/shares/invite.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/shares/invite.md
new file mode 100644
index 000000000..7003599cb
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/shares/invite.md
@@ -0,0 +1,55 @@
+---
+sidebar_position: 1
+id: invite
+title: Einladen zum Teilen
+description: Einladen zum Teilen
+draft: false
+---
+
+# Dateien und Ordner per Einladung mit Personen und Gruppen teilen
+
+Hier erklären wir, wie man Dateien und Ordner per Einladung mit anderen Personen und Gruppen innerhalb deiner OpenCloud in der OpenCloud Android-App teilen kann.
+
+## Drei-Punkte-Menü
+
+Klicke auf das „Drei-Punkte-Menü“ neben der Datei oder dem Ordner.
+
+<img src={require("../img/shares/invite/three-dot-menue.png").default} alt="Three-dot menue" height="400"/>
+
+## Teilen
+
+Wähle nun den Menüpunkt „Teilen“ aus.
+
+<img src={require("../img/shares/invite/sharing-button.png").default} alt="Shareing-Button" height="400"/>
+
+## Benutzer und Gruppen
+
+In der folgenden Auswahl klicke auf das Plus bei „Benutzer und Gruppen“.
+
+<img src={require("../img/shares/invite/invite-option.png").default} alt="Share with" height="400"/>
+
+## Teilen-Menü
+
+Das Teilen-Menü öffnet sich, dort kannst du in der Suchleiste nach Personen oder Gruppen suchen, die du einladen möchtest.
+
+<img src={require("../img/shares/invite/invite-menue.png").default} alt="Share with menue" height="400"/>
+<img src={require("../img/shares/invite/searchbar.png").default} alt="Search bar" height="400"/>
+
+## Berechtigungen
+
+Um die Freigabeberechtigungen einzustellen, klicke auf das Stiftsymbol neben dem Papierkorb-Symbol.
+
+<img src={require("../img/shares/invite/permissions.png").default} alt="Permissions" height="400"/>
+
+- Erstellen:  
+  Nutzer können Dateien und Ordner erstellen und hochladen.
+- Ändern:  
+  Nutzer können Dateien und Ordner bearbeiten.
+- Löschen:  
+  Nutzer können Dateien und Ordner löschen.
+
+## Erstellen
+
+Sobald die Einladung erstellt ist, siehst du sie in der Datei- oder Ordnerübersicht.
+
+<img src={require("../img/shares/invite/shared-with.png").default} alt="Shared with" height="400"/>
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/shares/links.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/shares/links.md
new file mode 100644
index 000000000..70b6c2bf8
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/shares/links.md
@@ -0,0 +1,63 @@
+---
+sidebar_position: 2
+id: links
+title: Per Link teilen
+description: Per Link teilen
+draft: false
+---
+
+# Dateien und Ordner per Link teilen
+
+Hier erklären wir, wie man Dateien und Ordner per Link mit anderen in der OpenCloud Android-App teilen kann.
+
+## Drei-Punkte-Menü
+
+Klicke auf das Drei-Punkte-Menü neben der Datei oder dem Ordner.
+
+<img src={require("../img/shares/links/three-dot-menue.png").default} alt="Three-dot menue" height="400"/>
+
+## Teilen
+
+Wähle nun den Menüpunkt „Teilen“ aus.
+
+<img src={require("../img/shares/links/sharing-button.png").default} alt="Share" height="400"/>
+
+## Öffentlicher Link
+
+In der folgenden Auswahl klicke auf „Öffentliche Links“.
+
+<img src={require("../img/shares/links/create-link-button.png").default} alt="Create link" height="400"/>
+
+## Link erstellen
+
+Hier kannst du verschiedene Optionen für den zu erstellenden Link auswählen und festlegen.
+
+<img src={require("../img/shares/links/create-link-options.png").default} alt="Overview link menue" height="400"/>
+
+- Linkname
+
+  Gib hier einen Namen für deinen Link ein.
+
+- Passwort
+
+  Ein Passwort ist erforderlich. Bitte gib eines ein, um fortzufahren.
+
+<img src={require("../img/shares/links/password.png").default} alt="Password" height="400"/>
+
+- Ablaufdatum
+
+  Hier kannst du eine Zeitspanne festlegen, wie lange der Link verfügbar sein soll.
+
+<img src={require("../img/shares/links/expiration-date.png").default} alt="Link expiration date" height="400"/>
+
+## Link speichern
+
+Um den Link zu erstellen, musst du nun auf „Speichern“ klicken.
+
+<img src={require("../img/shares/links/share-button.png").default} alt="Share" height="400"/>
+
+## Erstellter Link
+
+Sobald der Link erstellt ist, siehst du ihn mit dem vergebenen Namen in der Datei- oder Ordnerübersicht.
+
+<img src={require("../img/shares/links/created-link.png").default} alt="created link" height="400"/>
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/shortcuts.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/shortcuts.md
new file mode 100644
index 000000000..4c623e18f
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/shortcuts.md
@@ -0,0 +1,47 @@
+---
+sidebar_position: 5
+id: shortcuts
+title: Verlinkungen in der OpenCloud Android App
+description: Verlinkungen
+draft: false
+---
+
+# Verlinkung in der OpenCloud Android-App
+
+Hier zeigen wir dir, wie du Verlinkungen in der Android-App erstellen kannst.
+
+## Plus-Symbol
+
+Klicke auf das „Plus-Symbol“ und wähle „New Shortcut“ aus.
+
+<img src={require("./img/shortcuts/plus-button.png").default} alt="Plus button" width="300"/>
+
+## Verlinkungs-Menü
+
+Ein Menü öffnet sich mit Optionen für Verlinkungen.
+
+<img src={require("./img/shortcuts/shortcut-menue.png").default} alt="Shortcut menue" width="300"/>
+
+## URL eingeben
+
+Um eine Verlinkung zu einer Webseite zu erstellen, gib die Adresse der Webseite unter „URL“ ein.
+
+<img src={require("./img/shortcuts/url.png").default} alt="URL" width="300"/>
+
+## Verlinkungsnamen eingeben
+
+Hier gibst du einen Namen für die Verlinkung ein, unter dem sie angezeigt wird.
+
+<img src={require("./img/shortcuts/shortcut-name.png").default} alt="Name of the shortcut" width="300"/>
+
+## Erstellen-Button
+
+Um die Verlinkung zu erstellen, klicke auf „Create“.
+
+<img src={require("./img/shortcuts/create-button.png").default} alt="Create button" width="300"/>
+
+## Erstellte Verlinkung
+
+Deine erstellte Verlinkung wird nun angezeigt und kann verwendet werden.
+
+<img src={require("./img/shortcuts/created-shortcut.png").default} alt="Shortcut" width="300"/>
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/spaces.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/spaces.md
new file mode 100644
index 000000000..155f85776
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/android-app/spaces.md
@@ -0,0 +1,57 @@
+---
+sidebar_position: 6
+id: spaces
+title: Spaces
+description: Spaces in der OpenCloud Android App
+draft: false
+---
+
+# Der Bereich „Verlinkungen“ in der OpenCloud Android-App
+
+Der Bereich „Verlinkungen“ bietet einen zentralen Ort für die Zusammenarbeit in Gruppen oder Teams. In einem Space können mehrere Nutzer gemeinsam auf Dateien und Ordner zugreifen, Inhalte organisieren und Änderungen nachvollziehen.
+
+## Space-Übersicht
+
+Um die Space-Übersicht zu öffnen, tippe auf den „Spaces-Button“ in der unteren Leiste des Bildschirms.
+
+<img src={require("./img/spaces/spaces-button.png").default} alt="Spaces Button" style={{ width: '300px', marginRight: '60px' }} />
+
+Anschließend erscheint die Space-Übersicht, in der alle Spaces aufgelistet sind, in denen du Mitglied bist oder die du selbst erstellt hast.
+
+<img src={require("./img/spaces/spaces-overview.png").default} alt="Spaces Overview" style={{ width: '300px', marginRight: '60px' }} />
+
+## Suchfunktion
+
+Durch Tippen auf das Suchsymbol öffnet sich die Suchleiste sowie das Suchmenü für Spaces.
+
+<img src={require("./img/spaces/search-button.png").default} alt="Search Function" style={{ width: '300px', marginRight: '60px' }} />
+
+<img src={require("./img/spaces/search-menue.png").default} alt="Search Menue" style={{ width: '300px', marginRight: '60px' }} />
+
+## Funktionen innerhalb eines Spaces
+
+Durch Tippen auf das Plus-Symbol erscheinen die verfügbaren Funktionen innerhalb eines Spaces.
+
+<img src={require("./img/spaces/spaces-plus-symbol.png").default} alt="Plus Icon" style={{ width: '300px', marginRight: '60px' }} />
+
+<img src={require("./img/spaces/spaces-plus-symbol-menue.png").default} alt="Functions in Spaces" style={{ width: '400px', marginRight: '60px' }} />
+
+## Erstellen-Menü
+
+Dieser Abschnitt beschreibt die verfügbaren Aktionen im Erstellen-Menü eines Spaces.
+
+### 1. Hochladen
+
+Dateien vom Gerät auswählen und in den Space hochladen.
+
+### 2. Neuer Ordner
+
+Neue Ordner erstellen, um Inhalte übersichtlich zu strukturieren.
+
+### 3. Neues Dokument
+
+Ein neues Dokument direkt im Space erstellen – ohne separate App.
+
+### 4. Neue Verlinkung
+
+Eine Verlinkung zu einer Datei oder einem Ordner im Space erstellen, um schnellen Zugriff zu ermöglichen.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/collabora.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/collabora.md
new file mode 100644
index 000000000..081d52661
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/collabora.md
@@ -0,0 +1,39 @@
+---
+sidebar_position: 10
+id: collabora
+title: Collabora in OpenCloud
+description: Collabora in OpenCloud
+draft: false
+---
+
+# Collabora Online in OpenCloud
+
+Collabora Online ermöglicht es Ihnen, Dokumente (Textdokumente, Tabellenkalkulationen, Präsentationen) direkt in Ihrem Browser zu erstellen und zu bearbeiten – ganz ohne zusätzliche Software.  
+Die Integration mit OpenCloud bietet einen nahtlosen Zugriff auf Ihre Dateien und ermöglicht die Zusammenarbeit in Echtzeit.
+
+## Funktionen in OpenCloud
+
+### Dateien direkt aus der Cloud öffnen
+
+Alle in OpenCloud gespeicherten Dokumente können direkt in Collabora geöffnet werden.
+
+### Gemeinsame Bearbeitung
+
+Mehrere Benutzer können gleichzeitig am selben Dokument arbeiten, wobei Änderungen in Echtzeit synchronisiert werden.
+
+### Bilder aus OpenCloud einfügen
+
+Sie können Bilder, die in OpenCloud gespeichert sind, direkt in Ihre Dokumente einfügen.
+
+### Automatisches Speichern und Versionierung
+
+Änderungen werden automatisch gespeichert, und alle Versionen bleiben innerhalb von OpenCloud erhalten.
+
+### Unterstützte Formate
+
+Collabora Online unterstützt gängige Office-Formate wie `.odt`, `.docx`, `.ods`, `.xlsx`, `.odp` und weitere.
+
+## Hinweise
+
+- Die Leistung hängt von Ihrer Internetverbindung und der Größe des Dokuments ab.
+- Für erweiterte Funktionen oder detaillierte Anleitungen verweisen wir auf die [offizielle Collabora-Online-Dokumentation](https://www.collaboraoffice.com/collabora-online/).
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/common-issues.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/common-issues.md
new file mode 100644
index 000000000..fe884261a
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/common-issues.md
@@ -0,0 +1,60 @@
+---
+sidebar_position: 11
+id: common-issues
+title: Häufige Probleme & Hilfe
+description: Häufige Probleme & Hilfe
+draft: false
+---
+
+# Häufige Probleme & Hilfe
+
+## Symlinks werden mit dem Desktop-Client nicht synchronisiert
+
+### Problem
+
+Symbolische Links (Symlinks) werden vom OpenCloud Desktop-Client nicht synchronisiert. Nutzer stellen häufig fest, dass verlinkte Ordner oder Dateien fehlen oder nicht zugänglich sind.
+
+### Erklärung
+
+Symlinks werden aus mehreren wichtigen Gründen bewusst von der Synchronisation ausgeschlossen:
+
+- Nicht portabel: Symlinks verweisen oft auf Pfade, die nur auf dem ursprünglichen Rechner existieren. Auf einem anderen Gerät ist der Zielpfad in der Regel nicht vorhanden.
+- Nicht im Webinterface nutzbar: Das Webinterface kann Symlinks nicht interpretieren oder darstellen.
+- Problematisch unter Windows: Die Unterstützung von Symlinks unter Windows ist eingeschränkt und inkonsistent.
+- Gefahr von Endlosschleifen: Symlinks könnten aufeinander verweisen und so zu einer endlosen Synchronisationsschleife führen.
+- Identitätsverlust: Wenn der Client dem Symlink folgen und das Ziel synchronisieren würde, entstünde lediglich eine reguläre Kopie. Die Eigenschaft als Symlink ginge dabei verloren.
+
+### Lösung
+
+#### Ordner außerhalb des Synchronisationsverzeichnisses mit Symlinks einbinden
+
+Wenn Sie einen Ordner außerhalb Ihres Synchronisationsverzeichnisses (Sync-Root) synchronisieren möchten, können Sie diesen in die Sync-Root verschieben und am ursprünglichen Ort durch einen Symlink ersetzen.
+
+##### Beispiel
+
+Sie möchten den Ordner `/foo/A` synchronisieren, aber Ihre Sync-Root ist `/home/bar/OpenCloud/Personal`.
+
+1. Verschieben Sie den Ordner in die Sync-Root (in ein geeignetes Unterverzeichnis):
+
+   ```bash
+   mkdir -p /home/bar/OpenCloud/Personal/foo/
+   mv /foo/A /home/bar/OpenCloud/Personal/foo/A
+   ```
+
+2. Erstellen Sie einen Symlink:
+
+   ```bash
+   ln -s /home/bar/OpenCloud/Personal/foo/A /foo/A
+   ```
+
+## Dateien mit "~$" im Namen werden nicht synchronisiert
+
+Der OpenCloud Desktop Client synchronisiert keine Dateien, die mit `~$` beginnen, wie z. B. `~$document.docx`.
+Dabei handelt es sich um temporäre Sperrdateien, die von Microsoft Office-Anwendungen (Word, Excel, PowerPoint) erstellt werden, solange ein Dokument geöffnet ist.
+
+<img src={require("./img/common-issues/desktop-excluded.png").default} alt="Anzeige, dass ~$ Dateien von der Synchronisierung ausgeschlossen sind" width="500"/>
+
+Es sind keine eigentlichen Inhaltsdateien, sondern interne Marker, die verhindern sollen, dass mehrere Benutzer gleichzeitig dasselbe Dokument bearbeiten.  
+Sobald die Datei geschlossen wird, entfernt Office die `~$`-Datei automatisch.
+
+Weitere Informationen finden Sie in dem [Microsoft-Supportartikel zu temporären Office-Sperrdateien von Word/Excel/PowerPoint](https://support.microsoft.com/en-gb/topic/-the-document-is-locked-for-editing-by-another-user-error-message-when-you-try-to-open-a-document-in-word-10b92aeb-2e23-25e0-9110-370af6edb638?).
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/_category_.json b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/_category_.json
new file mode 100644
index 000000000..f1046237c
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/_category_.json
@@ -0,0 +1,8 @@
+{
+  "label": "OpenCloud Desktop Client",
+  "position": 6,
+  "link": {
+    "type": "doc",
+    "id": "desktop-client-overview"
+  }
+}
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/common-functionality/conflict-files.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/common-functionality/conflict-files.md
new file mode 100644
index 000000000..ef3cf4da0
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/common-functionality/conflict-files.md
@@ -0,0 +1,54 @@
+---
+sidebar_position: 10
+id: file-conflicts
+title: Dateikonflikte handhaben
+description: Wie Dateikonflikte handhaben
+draft: false
+---
+
+# Behebung von Dateikonflikten im OpenCloud Desktop-Client
+
+Wenn Dateien sowohl lokal als auch auf dem Server geändert werden, bevor eine Synchronisierung stattfindet, erstellt der Desktop-Client sogenannte „Konfliktkopien“. Beispiele:
+
+- `conflict.txt` (Server-Version)
+- `conflict (conflicted copy  JJJJ-MM-TT HHMMSS).txt` (lokale Version)
+
+<img src={require(".././img/conflict-files/conflict-file.png").default} alt="Konfliktdateien im Explorer" width="1920"/>
+
+Dies passiert in der Regel, wenn:
+
+- sich die lokale und die Server-Version einer Datei gleichzeitig verändern,
+- und die App diese Änderungen nicht automatisch zusammenführen kann.
+
+## Wie Sie benachrichtigt werden
+
+In der Übersicht des Desktop-Clients erscheint eine Benachrichtigung, wenn Konfliktdateien erkannt wurden.  
+Das bedeutet, dass mehrere Versionen derselben Datei existieren – häufig, weil Änderungen auf verschiedenen Geräten vorgenommen wurden, bevor eine Synchronisierung erfolgen konnte.  
+Die Benachrichtigung dient als Hinweis, dass Sie die Konflikte prüfen und entscheiden sollten, wie die Versionen zusammengeführt oder behalten werden.
+
+<img src={require(".././img/conflict-files/conflict-info.png").default} alt="Benachrichtigung zu Dateikonflikten im Desktop-Client" width="500"/>
+
+## So lösen Sie Dateikonflikte manuell
+
+1. Öffnen Sie beide Dateien (das Original und die Konfliktkopie).
+2. Vergleichen und kombinieren Sie die Unterschiede manuell.
+3. Bearbeiten Sie die ursprüngliche Datei (`conflict.txt`), um alle relevanten Änderungen zu übernehmen.
+4. Löschen Sie die Konfliktkopie, sobald die Änderungen zusammengeführt wurden.
+5. Lassen Sie die aktualisierte Originaldatei bestehen – die Synchronisierung wird dann wie gewohnt fortgesetzt.
+
+## Good Practices zur Vermeidung von Konflikten
+
+- Vermeiden Sie es, dieselbe Datei gleichzeitig auf mehreren Geräten zu bearbeiten.
+- Warten Sie immer, bis die Synchronisierung abgeschlossen ist, bevor Sie lokale Änderungen vornehmen.
+
+## Warum Konfliktdateien entstehen
+
+Der Desktop-Client erkennt einen Konflikt, wenn:
+
+- sowohl die lokale als auch die Server-Version einer Datei seit der letzten Synchronisierung geändert wurden,
+- der Abgleich anhand von Datei-IDs und Checksummen erfolgt – nicht nur anhand von Zeitstempeln.
+- zur Sicherheit beide Versionen erhalten bleiben, wobei die lokale Datei mit `"(conflicted copy ...)"` umbenannt wird.
+
+Konfliktdateien entstehen lokal und erscheinen nicht automatisch auf dem Server – es sei denn, sie werden ausdrücklich hochgeladen.
+
+Treten Konflikte häufig auf – auch bei einfachen Änderungen – kann dies auf Berechtigungsprobleme, schreibgeschützte Dateien oder darauf hinweisen, dass dieselben Dateien zusätzlich über andere Tools synchronisiert werden. In diesem Fall sollten Sie die Protokolle und Dateiattribute prüfen.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/common-functionality/desktop-client-states.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/common-functionality/desktop-client-states.md
new file mode 100644
index 000000000..0f1eba704
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/common-functionality/desktop-client-states.md
@@ -0,0 +1,106 @@
+---
+sidebar_position: 5
+id: desktop-client-states
+title: Status des Desktop-Clients
+description: Symbole des Desktop-Client-Status
+draft: false
+---
+
+## Symbole des Desktop-Client-Status verstehen
+
+Der OpenCloud Desktop-Client verwendet Tray-Symbole, um den aktuellen Synchronisations- und Verbindungsstatus anzuzeigen. So erkennen Sie schnell, ob alles normal funktioniert oder ob Handlungsbedarf besteht.
+
+## Kurzübersicht
+
+| Symbol                                                                                                                                | Status                 | Bedeutung                                                                             | Typische Aktion                                                        |
+| ------------------------------------------------------------------------------------------------------------------------------------- | ---------------------- | ------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
+| <img src={require(".././img/desktop-client-states/ocl-ui_logo-petrol.png").default} alt="Bereit-Status" width="28"/>                  | Bereit                 | Der Client ist verbunden und alle Dateien sind auf dem neuesten Stand.                | Keine Aktion erforderlich.                                             |
+| <img src={require(".././img/desktop-client-states/ocl-ui_sync-petrol-colour.png").default} alt="Synchronisierung-Status" width="28"/> | Synchronisierung läuft | Dateien werden gerade hoch- oder heruntergeladen.                                     | Warten Sie, bis die Synchronisierung abgeschlossen ist.                |
+| <img src={require(".././img/desktop-client-states/ocl-ui_pause-petrol-colour.png").default} alt="Pausiert-Status" width="28"/>        | Pausiert               | Die Synchronisierung wurde vorübergehend angehalten.                                  | Setzen Sie die Synchronisierung fort, wenn Sie bereit sind.            |
+| <img src={require(".././img/desktop-client-states/ocl-ui_offline-petrol-colour.png").default} alt="Offline-Status" width="28"/>       | Offline                | Der Client kann keine Verbindung zum OpenCloud-Server herstellen.                     | Prüfen Sie Ihre Netzwerkverbindung und die Erreichbarkeit des Servers. |
+| <img src={require(".././img/desktop-client-states/ocl-ui_info-petrol-colour.png").default} alt="Informations-Status" width="28"/>     | Information            | Der Client zeigt eine nicht kritische Informationsmeldung an.                         | Lesen Sie die Meldung bei Bedarf im Detail.                            |
+| <img src={require(".././img/desktop-client-states/ocl-ui_error-petrol-colour.png").default} alt="Fehler-Status" width="28"/>          | Fehler                 | Der Client ist auf ein Problem gestoßen, das die normale Synchronisierung verhindert. | Öffnen Sie den Client und beheben Sie das gemeldete Problem.           |
+
+## Bereit
+
+Das Symbol „Bereit“ wird angezeigt, wenn der Desktop-Client mit OpenCloud verbunden ist und keine Synchronisierung stattfindet.
+
+- Mit OpenCloud verbunden
+- Keine aktiven Dateiübertragungen
+- Alle Dateien sind auf dem neuesten Stand
+
+<img src={require(".././img/desktop-client-states/ocl-ui_logo-petrol.png").default} alt="Bereit-Status" width="100"/>
+
+Es ist keine Aktion erforderlich. Ihre Dateien sind vollständig synchronisiert.
+
+## Synchronisierung
+
+Das Symbol „Synchronisierung“ zeigt an, dass Dateien gerade hoch- oder heruntergeladen werden.
+
+- Dateien werden synchronisiert
+- Änderungen werden gerade verarbeitet
+- Der Client kommuniziert mit dem Server
+
+<img src={require(".././img/desktop-client-states/ocl-ui_sync-petrol-colour.png").default} alt="Synchronisierung-Status" width="100"/>
+
+Warten Sie, bis die Synchronisierung abgeschlossen ist, bevor Sie Ihr Gerät herunterfahren.
+
+## Pausiert
+
+Das Symbol „Pausiert“ erscheint, wenn die Synchronisierung vorübergehend angehalten wurde.
+
+- Die Synchronisierung ist gestoppt
+- Es werden keine Dateien übertragen
+- Lokale und entfernte Änderungen werden nicht synchronisiert
+
+<img src={require(".././img/desktop-client-states/ocl-ui_pause-petrol-colour.png").default} alt="Pausiert-Status" width="100"/>
+
+Setzen Sie die Synchronisierung über das Menü des Desktop-Clients fort, wenn Sie wieder synchronisieren möchten.
+
+## Offline
+
+Das Symbol „Offline“ zeigt an, dass der Desktop-Client derzeit keine Verbindung zum OpenCloud-Server herstellen kann.
+
+- Keine Verbindung zum Server
+- Synchronisierung ist nicht verfügbar
+- Lokale Dateien bleiben zugänglich
+
+<img src={require(".././img/desktop-client-states/ocl-ui_offline-petrol-colour.png").default} alt="Offline-Status" width="100"/>
+
+Häufige Ursachen sind:
+
+- Keine Internetverbindung
+- Server nicht verfügbar
+- DNS- oder Netzwerkprobleme
+- Firewall-Einschränkungen
+
+Prüfen Sie Ihre Netzwerkverbindung und stellen Sie sicher, dass der OpenCloud-Server erreichbar ist.
+
+## Information
+
+Das Symbol „Information“ wird für Hinweise verwendet, die keine sofortige Aktion erfordern.
+
+- Allgemeine Hinweise
+- Nicht kritische Ereignisse
+- Informationsmeldungen des Clients
+
+<img src={require(".././img/desktop-client-states/ocl-ui_info-petrol-colour.png").default} alt="Informations-Status" width="100"/>
+
+Prüfen Sie die Meldung bei Bedarf für weitere Details.
+
+## Fehler
+
+Das Symbol „Fehler“ zeigt an, dass der Desktop-Client auf ein Problem gestoßen ist, das die normale Synchronisierung verhindert.
+
+- Synchronisierung fehlgeschlagen
+- Probleme mit der Authentifizierung
+- Konfigurationsprobleme
+- Fehler beim Dateizugriff oder bei Berechtigungen
+
+<img src={require(".././img/desktop-client-states/ocl-ui_error-petrol-colour.png").default} alt="Fehler-Status" width="100"/>
+
+Öffnen Sie den Desktop-Client und prüfen Sie den gemeldeten Fehler. Die Synchronisierung kann erst fortgesetzt werden, wenn das Problem behoben wurde.
+
+:::info
+Das visuelle Erscheinungsbild und die Farbgebung der Symbole in der Taskleiste (Windows), im Dock (macOS) oder im System-Tray bzw. Panel (Linux) können je nach Betriebssystem variieren.
+:::
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/common-functionality/file-names.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/common-functionality/file-names.md
new file mode 100644
index 000000000..a0d210ce5
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/common-functionality/file-names.md
@@ -0,0 +1,67 @@
+---
+sidebar_position: 11
+id: file-names
+title: Dateinamensbeschränkungen
+description: Dateinamensbeschränkungen im OpenCloud Desktop-Client
+draft: false
+---
+
+# Dateinamensbeschränkungen im OpenCloud Desktop-Client
+
+Bei der Verwendung des OpenCloud Desktop-Clients müssen Datei- und Ordnernamen bestimmte Anforderungen des Betriebssystems (OS) erfüllen, um eine reibungslose Synchronisierung zwischen verschiedenen Plattformen zu gewährleisten.  
+Diese Einschränkungen werden nicht von OpenCloud erzwungen, sondern stammen aus systembedingten Beschränkungen.
+
+## Wichtige Richtlinien
+
+- Verwenden Sie keine verbotenen Zeichen oder reservierten Namen in Dateinamen – unabhängig vom Betriebssystem.
+- Wenn Sie von Linux/macOS zu einer Windows-basierten Freigabe synchronisieren, stellen Sie sicher, dass die Dateinamen mit den Windows-Benennungsregeln kompatibel sind.
+- Um unter Linux/macOS beim Synchronisieren mit Windows nur die Groß-/Kleinschreibung zu ändern (z. B. `File.txt` → `file.txt`), benennen Sie die Datei zunächst in einen komplett neuen Namen um, lassen Sie sie synchronisieren und benennen Sie sie danach in den gewünschten Namen um.
+
+## Häufige Einschränkungen
+
+### a. Maximale Pfadlänge
+
+Windows begrenzt Dateipfade standardmäßig auf 260 Zeichen.  
+Wenn Ihr Synchronisierungs-Stammverzeichnis diesen Wert überschreitet, zeigt der Desktop-Client folgende Warnung an:  
+„The path 'YOUR.LONG.PATH' is too long. Please enable long paths in the Windows settings or choose a different folder.“
+
+Unter Windows 10 und neuer kann diese Beschränkung aufgehoben werden, indem "Long Paths" aktiviert werden. Siehe [Microsoft-Dokumentation](https://learn.microsoft.com/de-de/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#enable-long-paths-in-windows-10-version-1607-and-later).
+
+### b. Verbotene Zeichen
+
+| Betriebssystem | Verbotene Zeichen               |
+| -------------- | ------------------------------- | ------------ |
+| Windows        | `<`, `>`, `:`, `"`, `/`, `\`, ` | `, `?`, `\*` |
+
+### c. Nicht druckbare ASCII-Zeichen
+
+- Linux/macOS: NUL (Zeichencode 0)
+- Windows: ASCII 0 – 31
+
+Auch wenn diese Zeichen auf manchen Systemen gültig sind, führen sie häufig zu Problemen bei der Synchronisierung.
+
+### d. Reservierte Dateinamen (Windows)
+
+Vermeiden Sie die Verwendung folgender Dateinamen:  
+`CON`, `PRN`, `AUX`, `NUL`, `COM1` – `COM9`, `LPT1` – `LPT9`
+
+### e. Besondere Regeln
+
+- Unter Linux/macOS beim Synchronisieren zu SMB können Dateinamen, die sich nur in der Groß-/Kleinschreibung unterscheiden, zu Konflikten führen – benennen Sie Dateien eindeutig, um Fehler zu vermeiden.
+- Unter Windows dürfen Dateinamen nicht mit einem Leerzeichen oder Punkt (`.`) enden.
+
+## Beispiel
+
+Das Erstellen einer Datei mit dem Namen `example.` oder `example.LPT1` unter macOS kann zwar erfolgreich mit OpenCloud synchronisiert werden.  
+Beim Zugriff über einen Windows-Client werden diese Dateien jedoch möglicherweise abgelehnt, da sie gegen reservierte Namens- oder Formatregeln verstoßen, was zu inkonsistentem Synchronisierungsverhalten zwischen Geräten führt.
+
+## Zusammenfassung
+
+| Einschränkungstyp         | Maßnahme                                               |
+| ------------------------- | ------------------------------------------------------ |
+| Pfadlänge                 | Pfade unter ~260 Zeichen halten (außer bei Long Paths) |
+| Verbotene Zeichen         | Nicht erlaubte Zeichen aus Namen entfernen             |
+| Steuerzeichen             | Nicht druckbare ASCII-Zeichen vermeiden                |
+| Reservierte Dateinamen    | Keine Windows-reservierten Namen verwenden             |
+| Nur Groß-/Kleinschreibung | Vorher temporär umbenennen, dann synchronisieren       |
+| Endzeichen                | Keine Dateinamen mit Leerzeichen oder Punkt beenden    |
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/common-functionality/logging.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/common-functionality/logging.md
new file mode 100644
index 000000000..4f4702095
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/common-functionality/logging.md
@@ -0,0 +1,61 @@
+---
+sidebar_position: 5
+id: logging
+title: Logfiles sammeln
+description: Logfiles sammeln in OpenCloud
+draft: false
+---
+
+# Protokollierung in einem temporären Verzeichnis in OpenCloud Desktop
+
+Wenn Sie Protokolle für die Fehlersuche erstellen müssen, gehen Sie wie folgt vor:
+
+## Öffnen Sie die Log-Einstellungen
+
+- Klicken Sie auf Einstellungen → Erweitert → Log-Einstellungen
+
+<img src={require(".././img/logging/logging-access.png").default} alt="logging access" width="400"/>
+
+## Aktivieren Sie die Protokollierung
+
+- Aktivieren Sie im Fenster Protokollausgabe das Kontrollkästchen Protokollierung in temporärem Ordner aktivieren.
+- Um dem Support-Team und den Entwicklern zu helfen, ist es hilfreich, das Log Http traffic zu aktivieren
+
+<img src={require(".././img/logging/logging-enable.png").default} alt="enable logging" width="400"/>
+
+## Finden Sie die Log-Dateien
+
+- Klicken Sie auf Ordner öffnen, um auf die Protokolle zuzugreifen.
+
+<img src={require(".././img/logging/logging-open-folder.png").default} alt="open logfile folder" width="400"/>
+
+- Wählen Sie die Protokolldateien für den Zeitraum aus, in dem das Problem aufgetreten ist.
+
+<img src={require(".././img/logging/logging-logfiles.png").default} alt="logfiles overview" width="400"/>
+
+:::note
+Diese Protokolle können helfen, Probleme mit OpenCloud Desktop zu diagnostizieren und zu beheben.
+:::
+
+### Log Inhalt Beschreibung
+
+`25-02-17 09:02:35:174 [ info sync.httplogger ]: REQUEST 3710cc12-7391-4793-8e89-00499dc11983 {„request“:{„body“:{„length“:0},„header“:{„accept“:„*/*“,„accept-language“:„en_DE“,„original-request-id“:„3710cc12-7391-4793-8e89-00499dc11983“,„user-agent“:"Mozilla/5. 0 (Macintosh) mirall/1.0.0-git (OpenCloud, macos-24. 3.0 ClientArchitecture: x86_64 OsArchitecture: arm64)„,“x-request-id„:“3710cc12-7391-4793-8e89-00499dc11983„},“info„:{“cached„:false,“id„:“3710cc12-7391-4793-8e89-00499dc11983„,“method„:“GET„,“url„:“https://cloud.opencloud.test/.well-known/openid-configuration"}}}`
+
+| Log Inhalt                           | Beschreibung                                                          |
+| ------------------------------------ | --------------------------------------------------------------------- |
+| 25-02-17 09:02:35:174                | Zeitstempel der Anfrage                                               |
+| [ info sync.httplogger ]             | Bezeichnung der Protokollkategorie                                    |
+| 3710cc12-7391-4793-8e89-00499dc11983 | X-REQUEST-ID (wird verwendet, um Anfragen und Antworten abzugleichen) |
+| Header: { }                          | Liste der HTTP-Header                                                 |
+| Data: []                             | HTTP-Bodies (JSON, XML)                                               |
+| (112ms)                              | Antwortzeit (seit Absenden der Anfrage)                               |
+
+### X-REQUEST-ID für die Fehlersuche verwenden
+
+- Die OpenCloud-Desktop-Anwendung sendet mit jeder Anfrage einen X-REQUEST-ID-Header.
+- Diese ID hilft bei der Suche nach entsprechenden Anfragen und Antworten in den Protokollen.
+- Sie können Ihren Webserver so konfigurieren, dass er die X-REQUEST-ID zu seinen Protokollen hinzufügt, um eine tiefere Analyse zu ermöglichen.
+
+:::note
+Diese Funktion ist nützlich für die Fehlersuche bei Synchronisationsproblemen, die Überwachung von Netzwerkaktivitäten und die Behebung von Verbindungsproblemen.
+:::
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/common-functionality/multiple-accounts.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/common-functionality/multiple-accounts.md
new file mode 100644
index 000000000..17f6139af
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/common-functionality/multiple-accounts.md
@@ -0,0 +1,44 @@
+---
+sidebar_position: 8
+id: multiple-accounts
+title: Mehrere Konten einrichten
+description: Nutzung von mehreren Konten in OpenCloud Desktop
+draft: false
+---
+
+# Mehrere Konten in OpenCloud Desktop verwenden
+
+Sie können mehrere Konten von verschiedenen OpenCloud-Servern mit Ihrem lokalen Rechner synchronisieren. Dies ermöglicht Ihnen, Dateien von verschiedenen Instanzen innerhalb desselben Desktop-Clients zu verwalten.
+
+## Wie man ein neues Konto hinzufügt
+
+- Öffnen Sie den OpenCloud Desktop
+- Klicken Sie auf Konto hinzufügen
+
+<img src={require(".././img/multiple-accounts/multiple-accounts-add-account.png").default} alt="add accounts" width="400"/>
+
+- Folgen Sie dem standard Einrichtungsprozess:
+  - Geben Sie die Server-URL ein
+  - Melden Sie sich mit Ihren Anmeldedaten an
+  - Autorisieren Sie den Zugang
+
+## Wechseln zwischen Konten
+
+- Nachdem Sie mehrere Konten hinzugefügt haben, werden diese in der Kontoübersicht im Einstellungsmenü angezeigt
+- Sie können einfach zwischen ihnen wechseln, um die Synchronisierungseinstellungen für jedes Konto separat zu verwalten
+
+<img src={require(".././img/multiple-accounts/multiple-accounts-switch-accounts.png").default} alt="switch accounts" width="400"/>
+
+## Wie Dateien lokal gespeichert werden
+
+- In Ihrem Datei-Explorer hat jedes Konto einen eigenen Ordner
+- Standardmäßig sind die Ordner benannt:
+  - OpenCloud (für das erste Konto)
+  - OpenCloud (2) (für das zweite Konto)
+  - OpenCloud (3) (für das dritte Konto), und so weiter
+
+<img src={require(".././img/multiple-accounts/multiple-accounts-locally.png").default} alt="multiple accounts in explorer or finder" width="400"/>
+
+:::note
+Diese Einrichtung stellt sicher, dass Dateien von verschiedenen Konten organisiert bleiben und nicht vermischt werden.
+:::
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/conflict-files/conflict-file.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/conflict-files/conflict-file.png
new file mode 100644
index 000000000..444ed1d0c
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/conflict-files/conflict-file.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/conflict-files/conflict-info.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/conflict-files/conflict-info.png
new file mode 100644
index 000000000..f2f2de293
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/conflict-files/conflict-info.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_error-petrol-colour.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_error-petrol-colour.png
new file mode 100644
index 000000000..d56597ca7
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_error-petrol-colour.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_info-petrol-colour.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_info-petrol-colour.png
new file mode 100644
index 000000000..a88ac03e0
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_info-petrol-colour.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_logo-petrol.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_logo-petrol.png
new file mode 100644
index 000000000..7e3bb5e64
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_logo-petrol.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_offline-petrol-colour.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_offline-petrol-colour.png
new file mode 100644
index 000000000..24f10f8b9
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_offline-petrol-colour.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_pause-petrol-colour.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_pause-petrol-colour.png
new file mode 100644
index 000000000..f97c08fe5
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_pause-petrol-colour.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_sync-petrol-colour.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_sync-petrol-colour.png
new file mode 100644
index 000000000..90e82d173
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_sync-petrol-colour.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/logging/logging-access.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/logging/logging-access.png
new file mode 100644
index 000000000..a5ff0436e
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/logging/logging-access.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/logging/logging-enable.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/logging/logging-enable.png
new file mode 100644
index 000000000..5b8cdc414
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/logging/logging-enable.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/logging/logging-logfiles.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/logging/logging-logfiles.png
new file mode 100644
index 000000000..47731da84
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/logging/logging-logfiles.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/logging/logging-open-folder.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/logging/logging-open-folder.png
new file mode 100644
index 000000000..3ae406ad2
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/logging/logging-open-folder.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/multiple-accounts/multiple-accounts-add-account.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/multiple-accounts/multiple-accounts-add-account.png
new file mode 100644
index 000000000..64b46fd13
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/multiple-accounts/multiple-accounts-add-account.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/multiple-accounts/multiple-accounts-locally.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/multiple-accounts/multiple-accounts-locally.png
new file mode 100644
index 000000000..9e4ccc9f4
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/multiple-accounts/multiple-accounts-locally.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/multiple-accounts/multiple-accounts-switch-accounts.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/multiple-accounts/multiple-accounts-switch-accounts.png
new file mode 100644
index 000000000..c6385e7fd
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/multiple-accounts/multiple-accounts-switch-accounts.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/set-up-accept-access.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/set-up-accept-access.png
new file mode 100644
index 000000000..72d6a5034
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/set-up-accept-access.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/set-up-advanced-configuration.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/set-up-advanced-configuration.png
new file mode 100644
index 000000000..c3da82191
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/set-up-advanced-configuration.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/set-up-all-set.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/set-up-all-set.png
new file mode 100644
index 000000000..296c632fc
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/set-up-all-set.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/set-up-enter-url.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/set-up-enter-url.png
new file mode 100644
index 000000000..2caf368ea
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/set-up-enter-url.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/set-up-login.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/set-up-login.png
new file mode 100644
index 000000000..17be764d5
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/set-up-login.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/set-up-user-password.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/set-up-user-password.png
new file mode 100644
index 000000000..8122b278c
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/set-up-user-password.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/windows/set-up-advanced-configuration.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/windows/set-up-advanced-configuration.png
new file mode 100644
index 000000000..5ca66f4fc
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/windows/set-up-advanced-configuration.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/windows/set-up-all-set.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/windows/set-up-all-set.png
new file mode 100644
index 000000000..1a139f8bb
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/set-up/windows/set-up-all-set.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/settings/settings-advanced.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/settings/settings-advanced.png
new file mode 100644
index 000000000..5a1bc2479
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/settings/settings-advanced.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/settings/settings-bandwidth.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/settings/settings-bandwidth.png
new file mode 100644
index 000000000..607b8f7d8
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/settings/settings-bandwidth.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/settings/settings-general.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/settings/settings-general.png
new file mode 100644
index 000000000..c414893f2
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/settings/settings-general.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/settings/settings-network.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/settings/settings-network.png
new file mode 100644
index 000000000..531ddb4b5
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/settings/settings-network.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/settings/settings-overview.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/settings/settings-overview.png
new file mode 100644
index 000000000..589974594
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/settings/settings-overview.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/settings/windows/settings-general.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/settings/windows/settings-general.png
new file mode 100644
index 000000000..88049dbf4
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/settings/windows/settings-general.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/sync-settings/sync-settings-choose-what-to-sync.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/sync-settings/sync-settings-choose-what-to-sync.png
new file mode 100644
index 000000000..5ef70a994
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/sync-settings/sync-settings-choose-what-to-sync.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/sync-settings/sync-settings-menu.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/sync-settings/sync-settings-menu.png
new file mode 100644
index 000000000..fedf5ca6e
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/sync-settings/sync-settings-menu.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/sync-settings/sync-settings-three-dot.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/sync-settings/sync-settings-three-dot.png
new file mode 100644
index 000000000..14b38e296
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/sync-settings/sync-settings-three-dot.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/uninstall/uninstall-manage-account.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/uninstall/uninstall-manage-account.png
new file mode 100644
index 000000000..f94c6edfa
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/uninstall/uninstall-manage-account.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/uninstall/uninstall-remove.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/uninstall/uninstall-remove.png
new file mode 100644
index 000000000..b9310b151
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/uninstall/uninstall-remove.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/vfs/always-keep-on-this-device.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/vfs/always-keep-on-this-device.png
new file mode 100644
index 000000000..b4172d487
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/vfs/always-keep-on-this-device.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/vfs/free-up-space.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/vfs/free-up-space.png
new file mode 100644
index 000000000..68bab6b7a
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/vfs/free-up-space.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/vfs/full-pinned.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/vfs/full-pinned.png
new file mode 100644
index 000000000..398b77906
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/vfs/full-pinned.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/vfs/full.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/vfs/full.png
new file mode 100644
index 000000000..2bca9d9ad
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/vfs/full.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/vfs/placeholder.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/vfs/placeholder.png
new file mode 100644
index 000000000..c3db85f28
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/img/vfs/placeholder.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/index.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/index.md
new file mode 100644
index 000000000..966abf9b7
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/index.md
@@ -0,0 +1,25 @@
+---
+sidebar_position: 0
+id: desktop-client-overview
+title: OpenCloud Desktop Client
+---
+
+# OpenCloud Desktop Client
+
+Der OpenCloud Desktop Client synchronisiert Dateien zwischen Ihrem Computer und OpenCloud. Er ist für Windows, macOS
+und Linux verfügbar und bietet Offline-Zugriff, automatische Synchronisierung und eine einheitliche Arbeitsweise mit
+lokalen Dateien.
+
+## In diesem Abschnitt
+
+- [Windows](./windows/installation.md)  
+  Installieren, einrichten und konfigurieren Sie den Desktop Client unter Windows.
+
+- [macOS](./macos/installation.md)  
+  Installieren, einrichten und konfigurieren Sie den Desktop Client unter macOS.
+
+- [Linux](./linux/installation.md)  
+  Installieren, einrichten und konfigurieren Sie den Desktop Client unter Linux.
+
+- [Gemeinsame Funktionen](./common-functionality/multiple-accounts.md)  
+  Erfahren Sie mehr über gemeinsame Funktionen wie mehrere Konten, Dateinamenregeln, Konfliktbehandlung und Logging.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/linux/installation.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/linux/installation.md
new file mode 100644
index 000000000..a385b0388
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/linux/installation.md
@@ -0,0 +1,68 @@
+---
+sidebar_position: 1
+id: installation
+title: Installation
+description: Install OpenCloud Desktop Client on Linux
+draft: false
+---
+
+# Installation on Linux (AppImage with AppImageLauncher)
+
+The OpenCloud Desktop Client is available as an AppImage for Linux.  
+Using AppImageLauncher is recommended to ensure proper system integration, menu entries, and simplified updates.
+
+## Install AppImageLauncher
+
+AppImageLauncher integrates AppImages into your system and manages them like regular applications.
+
+Follow the installation instructions here:
+
+[AppImageLauncher Installation Guide](https://github.com/TheAssassin/AppImageLauncher/releases/tag/v3.0.0-beta-3)
+lation
+
+## Download the OpenCloud AppImage
+
+Download the latest or desired `.AppImage` version from the official release page:
+
+- [OpenCloud Desktop Releases on GitHub](https://github.com/opencloud-eu/desktop/releases)
+
+Save the file to your preferred download directory.
+
+## Integrate the AppImage
+
+Once AppImageLauncher is installed:
+
+1. Right-click the downloaded `OpenCloud.AppImage`.
+2. Select “Open with AppImageLauncher”.
+3. Confirm integration when prompted.
+
+AppImageLauncher will automatically:
+
+- store the AppImage in the correct location
+- register a menu entry
+- ensure the app behaves like a native application
+
+## Launching OpenCloud Desktop
+
+After integration, you can start the client as usual through your application menu:
+
+- open your Application Launcher
+- search for OpenCloud Desktop
+- start the application
+
+The client will guide you through the initial setup.
+
+## Updating the AppImage
+
+When a new version is available, download the updated AppImage from GitHub.  
+AppImageLauncher will detect it and offer to replace the existing version automatically.
+
+## Uninstallation
+
+To remove the OpenCloud Desktop Client:
+
+1. Open your application menu.
+2. Search for OpenCloud Desktop
+3. Select the option to remove or uninstall the AppImage (menu wording may vary depending on distribution and launcher).
+
+AppImageLauncher will cleanly remove the integrated AppImage.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/linux/set-up.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/linux/set-up.md
new file mode 100644
index 000000000..6acc84662
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/linux/set-up.md
@@ -0,0 +1,55 @@
+---
+sidebar_position: 2
+id: set-up
+title: OpenCloud Desktop einrichten
+description: Einrichtung Ihres OpenCloud Desktop
+draft: false
+---
+
+# OpenCloud Desktop einrichten
+
+Folgen Sie diesen einfachen Schritten, um Ihren OpenCloud Desktop zu installieren, zu konfigurieren und Ihre Dateien mühelos zu synchronisieren.
+
+## Server-URL eingeben
+
+- Öffnen Sie Ihren OpenCloud Desktop
+- Geben Sie die URL Ihrer OpenCloud-Instanz ein
+- Klicken Sie auf **„Weiter“**
+
+  <img src={require(".././img/set-up/set-up-enter-url.png").default} alt="URL eingeben" width="400"/>
+
+## Anmeldung über den Webbrowser
+
+- Klicken Sie auf „Webbrowser öffnen“, um sich automatisch anzumelden
+- Alternativ können Sie die angezeigte URL kopieren und manuell in Ihren Browser einfügen
+
+  <img src={require(".././img/set-up/set-up-login.png").default} alt="Browser öffnen zur Anmeldung" width="400"/>
+
+## Zugangsdaten eingeben
+
+- Geben Sie Ihren Benutzernamen und Ihr Passwort ein
+- Klicken Sie auf „Login“
+
+  <img src={require(".././img/set-up/set-up-user-password.png").default} alt="Zugangsdaten eingeben" width="400"/>
+
+## Zugriff gewähren
+
+- Bestätigen Sie die Zugriffsanfrage, um Ihr Konto mit OpenCloud Desktop zu verknüpfen.
+
+  <img src={require(".././img/set-up/set-up-accept-access.png").default} alt="Zugriff gewähren" width="400"/>
+
+## Einrichtung abschließen
+
+## Optionale erweiterte Konfiguration
+
+- Wählen Sie aus, ob alle Dateien synchronisiert werden sollen oder nur bestimmte Ordner (dies kann später angepasst werden).
+- Ändern Sie den lokalen Download-Ordner, in dem Ihre Dateien gespeichert werden.
+
+  <img src={require(".././img/set-up/set-up-advanced-configuration.png").default} alt="Erweiterte Konfiguration" width="400"/>
+
+Wenn alles bereit ist, klicken Sie auf „Fertig“, um die Einrichtung abzuschließen.
+
+<img src={require(".././img/set-up/set-up-all-set.png").default} alt="Einrichtung abgeschlossen" width="400"/>
+
+Der OpenCloud Desktop ist nun erfolgreich eingerichtet.  
+Sie können jetzt Ihre Dateien nahtlos zwischen Ihrem Gerät und dem OpenCloud-Server synchronisieren!
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/linux/settings.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/linux/settings.md
new file mode 100644
index 000000000..13dc09c69
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/linux/settings.md
@@ -0,0 +1,53 @@
+---
+sidebar_position: 3
+id: settings
+title: Einstellungen in Linux
+description: Einstellungen in OpenCloud Desktop für Linux
+draft: false
+---
+
+# Einstellungen in OpenCloud Desktop ändern
+
+Sie können die Einstellungen des OpenCloud Desktop mit den folgenden Schritten anpassen:
+
+## Einstellungen öffnen
+
+- Klicken Sie auf "Einstellungen“ in der oberen rechten Ecke von OpenCloud Desktop
+
+<img src={require(".././img/settings/settings-overview.png").default} alt="settings overview" width="400"/>
+
+## Übersicht der Einstellungen
+
+### Allgemeine Einstellungen
+
+- Aktivieren oder Deaktivieren des automatischen Starts bei der Anmeldung
+- Legen Sie Ihre bevorzugte Sprache fest
+
+  <img src={require(".././img/settings/settings-general.png").default} alt="settings-general" width="400"/>
+
+### Erweiterte Einstellungen
+
+- Versteckte Dateien synchronisieren
+- Entscheiden Sie, ob gelöschte Dateien in den lokalen Papierkorb verschoben werden sollen
+- Bearbeiten Sie die Liste der ignorierten Dateien
+- Aktivieren Sie eine Debug-Protokolldatei für die Fehlersuche
+
+  <img src={require(".././img/settings/settings-advanced.png").default} alt="settings advanced" width="400"/>
+
+### Netzwerkeinstellungen
+
+- Wählen Sie aus, wie der Client mit Proxy-Einstellungen umgehen soll:
+  - Kein Proxy
+  - Systemproxy verwenden (Standard)
+  - Manuelles Eingeben eines Proxys
+
+  <img src={require(".././img/settings/settings-network.png").default} alt="settings network" width="400"/>
+
+  ### Download- und Upload-Bandbreite
+
+- Legen Sie Bandbreitenlimits fest:
+  - Kein Limit (Standard)
+  - Automatische Anpassung des Limits
+  - Ein bestimmtes Limit manuell einstellen
+
+  <img src={require(".././img/settings/settings-bandwidth.png").default} alt="settings bandwith" width="400"/>
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/linux/sync-settings.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/linux/sync-settings.md
new file mode 100644
index 000000000..2cd30a2d6
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/linux/sync-settings.md
@@ -0,0 +1,57 @@
+---
+sidebar_position: 3
+id: sync-settings-linux
+title: Synchronisationseinstellungen unter Linux
+description: Synchronisationseinstellungen unter Linux
+draft: false
+---
+
+# Linux: Synchronisationseinstellungen
+
+Auf Linux werden die Dateien auf Ihr System heruntergeladen. Über den OpenCloud Desktop Client können Sie festlegen, was synchronisiert werden soll und wie oft.
+
+## Zugriff auf die Synchronisationseinstellungen
+
+1. Öffnen Sie den OpenCloud Desktop Client.
+2. Gehen Sie zur Account-Ansicht.
+3. Klicken Sie auf das Drei-Punkte-Menü (...) neben dem Space, den Sie konfigurieren möchten.
+
+<img src={require(".././img/sync-settings/sync-settings-three-dot.png").default} alt="Account-Spaces-Menü" width="400"/>
+
+## Synchronisationsoptionen
+
+<img src={require(".././img/sync-settings/sync-settings-menu.png").default} alt="Synchronisationsoptionen-Menü" width="400"/>
+
+### In Linux Dateimanager anzeigen
+
+- Öffnet den Space im Dateimanager Ihrer Linux-Desktopumgebung.
+
+### Im Webbrowser anzeigen
+
+- Öffnet den Space in Ihrem Webbrowser.
+- Eine Anmeldung kann erforderlich sein, falls Sie noch nicht eingeloggt sind.
+
+### Jetzt synchronisieren
+
+- Löst eine sofortige manuelle Synchronisation aus.
+
+### Synchronisation pausieren
+
+- Stoppt die Synchronisation vorübergehend.
+- Kann jederzeit über Synchronisation fortsetzen wieder aktiviert werden.
+
+### Synchronisationsverbindung entfernen
+
+- Beendet die Synchronisation des Spaces, löscht jedoch nicht die lokalen Dateien.
+- Der Space bleibt auf dem Server erhalten.
+
+### Auswahl der zu synchronisierenden Dateien
+
+- Wählen Sie bestimmte Ordner aus, die lokal synchronisiert werden sollen.
+- Spart Speicherplatz, indem nur die benötigten Dateien synchronisiert werden.
+
+<img src={require(".././img/sync-settings/sync-settings-choose-what-to-sync.png").default} alt="Zu synchronisierende Dateien auswählen" width="400"/>
+
+:::note
+Dateien und Ordner, die nicht zur Synchronisation ausgewählt wurden, sind lokal nicht verfügbar.
+:::
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/macos/installation.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/macos/installation.md
new file mode 100644
index 000000000..007925851
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/macos/installation.md
@@ -0,0 +1,63 @@
+---
+sidebar_position: 1
+id: installation
+title: Installation
+description: OpenCloud Client installieren
+draft: false
+---
+
+# Installation auf macOS (.pkg-Datei)
+
+Der OpenCloud Desktop Client wird als signierte `.pkg`-Installer-Datei für macOS bereitgestellt.  
+Diese Installationsmethode integriert die Anwendung sauber ins System und folgt dem Standard-Installationsprozess von macOS.
+
+## Installer herunterladen
+
+Laden Sie die neueste oder gewünschte `.pkg`-Datei von der offiziellen Release-Seite herunter:
+
+- [OpenCloud Desktop Releases auf GitHub](https://github.com/opencloud-eu/desktop/releases)
+
+Speichern Sie die Datei in Ihrem Downloads-Ordner.
+
+## Installer ausführen
+
+1. Doppelklicken Sie auf die heruntergeladene `.pkg`-Datei.
+2. Der macOS-Installer öffnet sich automatisch.
+3. Folgen Sie den Anweisungen auf dem Bildschirm, um die Installation abzuschließen.
+
+Der Installer legt OpenCloud Desktop im Applications-Ordner ab.
+
+## Anwendung starten
+
+Nach der Installation können Sie OpenCloud Desktop starten über:
+
+- den Applications-Ordner
+- Launchpad
+- oder über Spotlight (drücken Sie `Cmd + Leertaste` und suchen Sie nach „OpenCloud Desktop“)
+
+## Erster Start
+
+Beim ersten Start führt der Client Sie durch:
+
+- die Anmeldung mit Ihrem OpenCloud-Konto
+- die Auswahl der Synchronisationseinstellungen
+- die Konfiguration grundlegender Optionen
+
+Die Anwendung ist nun einsatzbereit auf macOS.
+
+## Deinstallation
+
+Um den OpenCloud Desktop Client vom System zu entfernen:
+
+1. Öffnen Sie den Applications-Ordner.
+2. Suchen Sie nach OpenCloud Desktop.app.
+3. Ziehen Sie die Anwendung in den Papierkorb oder klicken Sie mit der rechten Maustaste und wählen Sie In den Papierkorb legen.
+4. Leeren Sie den Papierkorb, um die Deinstallation abzuschließen.
+
+Optionale Konfigurationsdateien können im Benutzerverzeichnis verbleiben:
+
+- `~/Library/Application Support/OpenCloud/`
+- `~/Library/Preferences/eu.opencloud.desktop.plist`
+- `~/Library/Logs/OpenCloud/`
+
+Diese Dateien können manuell gelöscht werden, wenn eine vollständige Bereinigung gewünscht ist.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/macos/set-up.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/macos/set-up.md
new file mode 100644
index 000000000..36bd8c140
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/macos/set-up.md
@@ -0,0 +1,55 @@
+---
+sidebar_position: 2
+id: set-up
+title: OpenCloud Desktop einrichten
+description: Einrichtung Ihres OpenCloud Desktop
+draft: false
+---
+
+# OpenCloud Desktop einrichten
+
+Folgen Sie diesen einfachen Schritten, um Ihren OpenCloud Desktop zu installieren, zu konfigurieren und Ihre Dateien mühelos zu synchronisieren.
+
+## Server-URL eingeben
+
+- Öffnen Sie Ihren OpenCloud Desktop
+- Geben Sie die URL Ihrer OpenCloud-Instanz ein
+- Klicken Sie auf „Weiter“
+
+  <img src={require(".././img/set-up/set-up-enter-url.png").default} alt="URL eingeben" width="400"/>
+
+## Anmeldung über den Webbrowser
+
+- Klicken Sie auf „Webbrowser öffnen“, um sich automatisch anzumelden
+- Alternativ können Sie die angezeigte URL kopieren und manuell in Ihren Browser einfügen
+
+  <img src={require(".././img/set-up/set-up-login.png").default} alt="Browser öffnen zur Anmeldung" width="400"/>
+
+## Zugangsdaten eingeben
+
+- Geben Sie Ihren Benutzernamen und Ihr Passwort ein
+- Klicken Sie auf **„Login“**
+
+  <img src={require(".././img/set-up/set-up-user-password.png").default} alt="Zugangsdaten eingeben" width="400"/>
+
+## Zugriff gewähren
+
+- Bestätigen Sie die Zugriffsanfrage, um Ihr Konto mit dem OpenCloud Desktop zu verknüpfen.
+
+  <img src={require(".././img/set-up/set-up-accept-access.png").default} alt="Zugriff gewähren" width="400"/>
+
+## Einrichtung abschließen
+
+## Optionale erweiterte Konfiguration
+
+- Wählen Sie aus, ob alle Dateien synchronisiert werden sollen oder nur bestimmte Ordner (dies kann später angepasst werden).
+- Ändern Sie den lokalen Download-Ordner, in dem Ihre Dateien gespeichert werden.
+
+  <img src={require(".././img/set-up/set-up-advanced-configuration.png").default} alt="Erweiterte Konfiguration" width="400"/>
+
+Wenn alles bereit ist, klicken Sie auf „Fertig“, um die Einrichtung abzuschließen.
+
+<img src={require(".././img/set-up/set-up-all-set.png").default} alt="Einrichtung abgeschlossen" width="400"/>
+
+Der OpenCloud Desktop ist nun erfolgreich eingerichtet.  
+Sie können jetzt nahtlos Ihre Dateien zwischen Ihrem Gerät und dem OpenCloud-Server synchronisieren!
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/macos/settings.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/macos/settings.md
new file mode 100644
index 000000000..0904ac047
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/macos/settings.md
@@ -0,0 +1,53 @@
+---
+sidebar_position: 3
+id: settings
+title: Einstellungen in macOS
+description: Einstellungen in OpenCloud Desktop für macOS
+draft: false
+---
+
+# Einstellungen in OpenCloud Desktop ändern
+
+Sie können die Einstellungen des OpenCloud Desktop mit den folgenden Schritten anpassen:
+
+## Einstellungen öffnen
+
+- Klicken Sie auf "Einstellungen“ in der oberen rechten Ecke von OpenCloud Desktop
+
+<img src={require(".././img/settings/settings-overview.png").default} alt="settings overview" width="400"/>
+
+## Übersicht der Einstellungen
+
+### Allgemeine Einstellungen
+
+- Aktivieren oder Deaktivieren des automatischen Starts bei der Anmeldung
+- Legen Sie Ihre bevorzugte Sprache fest
+
+  <img src={require(".././img/settings/settings-general.png").default} alt="settings-general" width="400"/>
+
+### Erweiterte Einstellungen
+
+- Versteckte Dateien synchronisieren
+- Entscheiden Sie, ob gelöschte Dateien in den lokalen Papierkorb verschoben werden sollen
+- Bearbeiten Sie die Liste der ignorierten Dateien
+- Aktivieren Sie eine Debug-Protokolldatei für die Fehlersuche
+
+  <img src={require(".././img/settings/settings-advanced.png").default} alt="settings advanced" width="400"/>
+
+### Netzwerkeinstellungen
+
+- Wählen Sie aus, wie der Client mit Proxy-Einstellungen umgehen soll:
+  - Kein Proxy
+  - Systemproxy verwenden (Standard)
+  - Manuelles Eingeben eines Proxys
+
+  <img src={require(".././img/settings/settings-network.png").default} alt="settings network" width="400"/>
+
+  ### Download- und Upload-Bandbreite
+
+- Legen Sie Bandbreitenlimits fest:
+  - Kein Limit (Standard)
+  - Automatische Anpassung des Limits
+  - Ein bestimmtes Limit manuell einstellen
+
+  <img src={require(".././img/settings/settings-bandwidth.png").default} alt="settings bandwith" width="400"/>
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/macos/sync-settings.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/macos/sync-settings.md
new file mode 100644
index 000000000..50e028599
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/macos/sync-settings.md
@@ -0,0 +1,57 @@
+---
+sidebar_position: 3
+id: sync-settings-mac
+title: Synchronisationseinstellungen unter macOS
+description: Synchronisationseinstellungen unter macOS
+draft: false
+---
+
+# macOS: Synchronisationseinstellungen
+
+Auf macOS werden die Dateien auf Ihr System heruntergeladen. Über den OpenCloud Desktop Client können Sie festlegen, was synchronisiert werden soll und wie oft.
+
+## Zugriff auf die Synchronisationseinstellungen
+
+1. Öffnen Sie den OpenCloud Desktop Client.
+2. Gehen Sie zur Account-Ansicht.
+3. Klicken Sie auf das Drei-Punkte-Menü neben dem Space, den Sie konfigurieren möchten.
+
+<img src={require(".././img/sync-settings/sync-settings-three-dot.png").default} alt="Account-Spaces-Menü" width="400"/>
+
+## Synchronisationsoptionen
+
+<img src={require(".././img/sync-settings/sync-settings-menu.png").default} alt="Synchronisationsoptionen-Menü" width="400"/>
+
+### In Finder anzeigen
+
+- Öffnet den Space im Finder.
+
+### Im Webbrowser anzeigen
+
+- Öffnet den Space in Ihrem Webbrowser.
+- Eine Anmeldung kann erforderlich sein, falls Sie noch nicht eingeloggt sind.
+
+### Jetzt synchronisieren
+
+- Löst eine sofortige manuelle Synchronisation aus.
+
+### Synchronisation pausieren
+
+- Stoppt die Synchronisation vorübergehend.
+- Kann jederzeit über Synchronisation fortsetzen wieder aktiviert werden.
+
+### Synchronisationsverbindung entfernen
+
+- Beendet die Synchronisation des Spaces, löscht jedoch nicht die lokalen Dateien.
+- Der Space bleibt auf dem Server erhalten.
+
+### Auswahl der zu synchronisierenden Dateien
+
+- Wählen Sie bestimmte Ordner aus, die lokal synchronisiert werden sollen.
+- Spart Speicherplatz, indem nur die benötigten Dateien synchronisiert werden.
+
+<img src={require(".././img/sync-settings/sync-settings-choose-what-to-sync.png").default} alt="Zu synchronisierende Dateien auswählen" width="400"/>
+
+:::note
+Dateien und Ordner, die nicht zur Synchronisation ausgewählt wurden, sind lokal nicht verfügbar.
+:::
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/settings.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/settings.md
new file mode 100644
index 000000000..de491308f
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/settings.md
@@ -0,0 +1,58 @@
+---
+sidebar_position: 3
+id: settings
+title: Einstellungen
+description: Ändern der Einstellungen in OpenCloud Desktop
+draft: false
+---
+
+# Einstellungen in OpenCloud Desktop ändern
+
+Sie können die Einstellungen des OpenCloud Desktop mit den folgenden Schritten anpassen:
+
+## Einstellungen öffnen
+
+- Klicken Sie auf "Einstellungen“ in der oberen rechten Ecke von OpenCloud Desktop
+
+<img src={require("./img/settings/settings-overview.png").default} alt="settings overview" width="400"/>
+
+## Übersicht der Einstellungen
+
+### Allgemeine Einstellungen
+
+- Aktivieren oder Deaktivieren des automatischen Starts bei der Anmeldung
+- Wählen Sie, ob Desktop-Benachrichtigungen angezeigt werden sollen
+- Legen Sie Ihre bevorzugte Sprache fest
+
+  <img src={require("./img/settings/settings-general.png").default} alt="settings-general" width="400"/>
+
+### Erweiterte Einstellungen
+
+- Versteckte Dateien synchronisieren
+- Entscheiden Sie, ob gelöschte Dateien in den lokalen Papierkorb verschoben werden sollen
+- Bearbeiten Sie die Liste der ignorierten Dateien
+- Aktivieren Sie eine Debug-Protokolldatei für die Fehlersuche
+
+  <img src={require("./img/settings/settings-advanced.png").default} alt="settings advanced" width="400"/>
+
+### Netzwerkeinstellungen
+
+- Wählen Sie aus, wie der Client mit Proxy-Einstellungen umgehen soll:
+  - Kein Proxy
+  - Systemproxy verwenden (Standard)
+  - Manuelles Eingeben eines Proxys
+
+  <img src={require("./img/settings/settings-network.png").default} alt="settings network" width="400"/>
+
+  ### Download- und Upload-Bandbreite
+
+- Legen Sie Bandbreitenlimits fest:
+  - Kein Limit (Standard)
+  - Automatische Anpassung des Limits
+  - Ein bestimmtes Limit manuell einstellen
+
+  <img src={require("./img/settings/settings-bandwidth.png").default} alt="settings bandwith" width="400"/>
+
+:::note
+Indem Sie diese Einstellungen anpassen, können Sie OpenCloud Desktop nach Ihren Bedürfnissen optimieren!
+:::
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/windows/installation.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/windows/installation.md
new file mode 100644
index 000000000..151074b9c
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/windows/installation.md
@@ -0,0 +1,57 @@
+---
+sidebar_position: 1
+id: installation
+title: Installation
+description: Installiere den OpenCloud Client
+draft: false
+---
+
+# Installation unter Windows
+
+Der OpenCloud Desktop Client für Windows ist über den Microsoft Store verfügbar.  
+Die Installation über den Store sorgt für einen einfachen Installationsprozess, automatische Updates und eine nahtlose Integration in Windows.
+
+## Microsoft Store öffnen
+
+Öffne den Microsoft Store auf deinem Windows-Gerät und suche nach OpenCloud Desktop,  
+oder klicke auf den untenstehenden Button, um direkt zur App-Seite zu gelangen:
+
+<a href="https://apps.microsoft.com/detail/9pbx43hcmldq?mode=direct">
+  <img alt="Download from Microsoft Store" src="https://get.microsoft.com/images/en-us%20dark.svg" width="200"/>
+</a>
+
+## „Installieren“ klicken
+
+Klicke auf der App-Seite auf Installieren, um den OpenCloud Desktop Client herunterzuladen und zu installieren.
+
+Der Microsoft Store übernimmt die Installation automatisch und legt die Anwendung an der richtigen Stelle im System ab.
+
+## Anwendung starten
+
+Nach Abschluss der Installation kannst du den Client über das Startmenü öffnen, indem du nach OpenCloud Desktop suchst.  
+Die Anwendung führt dich durch die erste Einrichtung, einschließlich der Anmeldung mit deinem Konto.
+
+## Automatische Updates
+
+Der Microsoft Store hält den OpenCloud Desktop Client automatisch auf dem neuesten Stand.  
+Updates werden im Hintergrund installiert und erfordern keine manuellen Schritte.
+
+Dies stellt sicher, dass:
+
+- immer die neuesten Funktionen verfügbar sind
+- Sicherheitsverbesserungen zeitnah angewendet werden
+- volle Kompatibilität mit aktuellen Windows-Versionen gewährleistet ist
+
+:::note
+Die Installation über den Microsoft Store sorgt für automatische Updates, eine bessere Systemintegration und reduziert den Bedarf an manueller Wartung.
+:::
+
+## Deinstallation (optional)
+
+Falls du den Client deinstallieren möchtest:
+
+1. Öffne das Startmenü.
+2. Suche nach OpenCloud Desktop.
+3. Klicke mit der rechten Maustaste auf die Anwendung und wähle Deinstallieren.
+
+Windows entfernt den Client und dessen Komponenten sauber über
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/windows/set-up.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/windows/set-up.md
new file mode 100644
index 000000000..dd44b11d3
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/windows/set-up.md
@@ -0,0 +1,55 @@
+---
+sidebar_position: 2
+id: set-up
+title: OpenCloud Desktop einrichten
+description: Einrichtung Ihres OpenCloud Desktop
+draft: false
+---
+
+# OpenCloud Desktop einrichten
+
+Folgen Sie diesen einfachen Schritten, um Ihren OpenCloud Desktop zu installieren und zu konfigurieren und Ihre Dateien mühelos zu synchronisieren.
+
+## Server-URL eingeben
+
+- Öffnen Sie Ihren OpenCloud Desktop
+- Geben Sie die URL Ihrer OpenCloud-Instanz ein
+- Klicken Sie auf „Weiter“
+
+  <img src={require(".././img/set-up/set-up-enter-url.png").default} alt="URL eingeben" width="400"/>
+
+## Anmeldung über den Webbrowser
+
+- Klicken Sie auf „Webbrowser öffnen“, um sich automatisch anzumelden
+- Alternativ können Sie die angezeigte URL kopieren und manuell in Ihren Browser einfügen
+
+  <img src={require(".././img/set-up/set-up-login.png").default} alt="Browser öffnen zur Anmeldung" width="400"/>
+
+## Zugangsdaten eingeben
+
+- Geben Sie Ihren Benutzernamen und Ihr Passwort ein
+- Klicken Sie auf „Login“
+
+  <img src={require(".././img/set-up/set-up-user-password.png").default} alt="Zugangsdaten eingeben" width="400"/>
+
+## Zugriff gewähren
+
+- Bestätigen Sie die Zugriffsanfrage, um Ihr Konto mit dem OpenCloud Desktop zu verknüpfen.
+
+  <img src={require(".././img/set-up/set-up-accept-access.png").default} alt="Zugriff gewähren" width="400"/>
+
+## Einrichtung abschließen
+
+## Optionale erweiterte Konfiguration
+
+- Wählen Sie aus, ob alle vorhandenen Spaces synchronisiert werden sollen oder ob die Synchronisation manuell eingerichtet werden soll.
+- Ändern Sie den lokalen Download-Ordner, in dem Ihre Dateien gespeichert werden.
+
+  <img src={require(".././img/set-up/windows/set-up-advanced-configuration.png").default} alt="Erweiterte Konfiguration" width="400"/>
+
+Wenn alles bereit ist, klicken Sie auf „Fertig“, um die Einrichtung abzuschließen.
+
+<img src={require(".././img/set-up/windows/set-up-all-set.png").default} alt="Einrichtung abgeschlossen" width="400"/>
+
+Der OpenCloud Desktop wurde erfolgreich eingerichtet.  
+Sie können nun direkt damit beginnen, Ihre Dateien nahtlos zwischen Ihrem Gerät und dem OpenCloud-Server zu synchronisieren!
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/windows/settings.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/windows/settings.md
new file mode 100644
index 000000000..0b6cc6252
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/windows/settings.md
@@ -0,0 +1,52 @@
+---
+sidebar_position: 3
+id: settings
+title: Einstellungen in Windows
+description: Einstellungen in OpenCloud Desktop für Windows
+draft: false
+---
+
+# Einstellungen in OpenCloud Desktop ändern
+
+Sie können die Einstellungen des OpenCloud Desktop mit den folgenden Schritten anpassen:
+
+## Einstellungen öffnen
+
+- Klicken Sie auf "Einstellungen“ in der oberen rechten Ecke von OpenCloud Desktop
+
+<img src={require(".././img/settings/settings-overview.png").default} alt="settings overview" width="400"/>
+
+## Übersicht der Einstellungen
+
+### Allgemeine Einstellungen
+
+- Legen Sie Ihre bevorzugte Sprache fest
+
+  <img src={require(".././img/settings/windows/settings-general.png").default} alt="settings-general" width="400"/>
+
+### Erweiterte Einstellungen
+
+- Versteckte Dateien synchronisieren
+- Entscheiden Sie, ob gelöschte Dateien in den lokalen Papierkorb verschoben werden sollen
+- Bearbeiten Sie die Liste der ignorierten Dateien
+- Aktivieren Sie eine Debug-Protokolldatei für die Fehlersuche
+
+  <img src={require(".././img/settings/settings-advanced.png").default} alt="settings advanced" width="400"/>
+
+### Netzwerkeinstellungen
+
+- Wählen Sie aus, wie der Client mit Proxy-Einstellungen umgehen soll:
+  - Kein Proxy
+  - Systemproxy verwenden (Standard)
+  - Manuelles Eingeben eines Proxys
+
+  <img src={require(".././img/settings/settings-network.png").default} alt="settings network" width="400"/>
+
+  ### Download- und Upload-Bandbreite
+
+- Legen Sie Bandbreitenlimits fest:
+  - Kein Limit (Standard)
+  - Automatische Anpassung des Limits
+  - Ein bestimmtes Limit manuell einstellen
+
+  <img src={require(".././img/settings/settings-bandwidth.png").default} alt="settings bandwith" width="400"/>
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/windows/sync-settings.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/windows/sync-settings.md
new file mode 100644
index 000000000..4dff2e36e
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/desktop-client/windows/sync-settings.md
@@ -0,0 +1,65 @@
+---
+sidebar_position: 4
+id: sync-settings-win
+title: Synchronisationseinstellungen unter Windows
+description: Synchronisationseinstellungen unter Windows
+draft: false
+---
+
+# Windows: Synchronisationseinstellungen
+
+Der OpenCloud Desktop Client nutzt das Windows Virtual File System (VFS), um Ihre Cloud-Daten direkt in den Windows-Dateiexplorer zu integrieren.  
+Dateien und Ordner werden angezeigt, ohne dass sie vollständig heruntergeladen werden müssen – das spart lokalen Speicherplatz.
+
+## Status der Datei
+
+Dateien und Ordner können verschiedene Stati haben, je nachdem, ob sie lokal gespeichert oder nur online verfügbar sind.
+
+### Immer auf diesem Gerät verfügbar (full pinned)
+
+- Lokal gespeichert und jederzeit offline zugänglich.
+- Windows entfernt diese Datei nicht automatisch.
+
+<img src={require(".././img/vfs/full-pinned.png").default} alt="Symbol vollständig angeheftet" width="400"/>
+
+### Auf diesem Gerät verfügbar (full)
+
+- Heruntergeladen und offline verfügbar.
+- Kann von Windows entfernt werden, wenn Speicherplatz benötigt wird.
+- Neu erstellte oder hinzugefügte Dateien erhalten automatisch diesen Status.
+
+<img src={require(".././img/vfs/full.png").default} alt="Symbol vollständig" width="400"/>
+
+### Online verfügbar (placeholder)
+
+- Wird im Datei-Explorer angezeigt, befindet sich jedoch nur in der Cloud.
+- Wird beim Öffnen automatisch heruntergeladen; Internetverbindung erforderlich.
+
+<img src={require(".././img/vfs/placeholder.png").default} alt="Symbol Platzhalter" width="400"/>
+
+## Elemente offline verfügbar machen
+
+Um eine Datei, einen Ordner oder einen Space lokal zu speichern:
+
+1. Klicken Sie im Datei-Explorer mit der rechten Maustaste auf das Element.
+2. Wählen Sie „Immer auf diesem Gerät beibehalten“.
+
+<img src={require(".././img/vfs/always-keep-on-this-device.png").default} alt="Auswahl: Immer auf diesem Gerät behalten" width="400"/>
+
+## Speicherplatz freigeben
+
+Um lokale Kopien zu entfernen, während die Elemente weiterhin im Datei-Explorer sichtbar bleiben:
+
+1. Klicken Sie mit der rechten Maustaste auf das Element.
+2. Wählen Sie „Speicherplatz freigeben“.
+
+<img src={require(".././img/vfs/free-up-space.png").default} alt="Auswahl: Speicherplatz freigeben" width="400"/>
+
+## Zugriff auf Dateien
+
+- Online-only Dateien werden automatisch heruntergeladen, sobald Sie sie öffnen.
+- Änderungen werden zurück zu OpenCloud synchronisiert.
+
+:::note
+Für Dateien, die nur online verfügbar sind, ist eine Internetverbindung erforderlich.
+:::
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/_category_.json b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/_category_.json
new file mode 100644
index 000000000..5ff00c3b9
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/_category_.json
@@ -0,0 +1,8 @@
+{
+  "label": "Dateien und Ordner verwalten",
+  "position": 3,
+  "link": {
+    "type": "doc",
+    "id": "files-and-folders-overview"
+  }
+}
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/activity.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/activity.md
new file mode 100644
index 000000000..4adcd4fa0
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/activity.md
@@ -0,0 +1,31 @@
+---
+sidebar_position: 8
+id: activities
+title: Aktivitäten
+description: Aktivitäten einer Datei oder eines Ordners in OpenCloud anzeigen
+draft: false
+---
+
+# Aktivitäten einer Datei oder eines Ordners anzeigen
+
+Um herauszufinden, wer eine Datei oder einen Ordner bearbeitet hat und welche Aktionen ausgeführt wurden, gehen Sie wie folgt vor:
+
+## Aktivitäten anzeigen
+
+- Details öffnen
+  - Klicken Sie mit der rechten Maustaste auf die Datei oder den Ordner oder klicken Sie auf die drei Punkte in der entsprechenden Zeile.
+  - Wählen Sie im Kontextmenü "Details“ aus.
+
+    <img src={require("./img/activity/details-button.png").default} alt="Details auswählen im Kontextmenü" width="1920"/>
+
+- Wählen Sie Aktivitäten
+  - In der rechten Seitenleiste öffnet sich ein Fenster. Wählen Sie dort "Aktivitäten“ aus.
+    <img src={require("./img/activity/aktivitaeten-button.png").default} alt="Aktivitäten auswählen" width="400"/>
+
+- Aktivitäten anzeigen
+  - Alle Aktivitäten, die mit dieser Datei oder diesem Ordner durchgeführt wurden, werden jetzt angezeigt.
+    <img src={require("./img/activity/aktivitaeten.png").default} alt="Aktivitäten anzeigen" width="400"/>
+
+:::info
+So können Sie alle Änderungen und Aktionen nachverfolgen.
+:::
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/create-rename-move.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/create-rename-move.md
new file mode 100644
index 000000000..91fed2d24
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/create-rename-move.md
@@ -0,0 +1,68 @@
+---
+sidebar_position: 1
+id: create-rename-move
+title: Erstellen - Umbenennen - Verschieben
+description: Erstellen - Umbenennen - Verschieben
+draft: false
+---
+
+# Erstellen - Umbenennen - Verschieben
+
+In OpenCloud können Sie ganz einfach neue Text-, Tabellen- und Präsentationsdateien in der Weboberfläche erstellen. Sie können Dateien und Ordner außerdem umbenennen oder an einen anderen Speicherort verschieben.
+
+## Dateien und Ordner erstellen
+
+- Öffnen Sie das Menü „+ Neu“ in der linken Seitenleiste.
+  <img src={require("./img/create-rename-move/neu-button.png").default} alt="Neue Schaltfläche" width="1920"/>
+- Wählen Sie entweder „Ordner“ oder den gewünschten Dateityp aus.
+  <img src={require("./img/create-rename-move/neu-optionen.png").default} alt="Dateityp oder Ordner auswählen" width="400"/>
+- Geben Sie im angezeigten Fenster einen Namen für die Datei oder den Ordner ein.
+- Klicken Sie auf „Erstellen“.
+
+  <img src={require("./img/create-rename-move/erstellen-button.png").default} alt="Auf Erstellen klicken" width="400"/>
+
+Fertig. Die Datei oder der Ordner wurde erstellt. Wenn es sich um eine Datei handelt, wird sie automatisch im Bearbeitungsmodus geöffnet.
+
+## Dateien oder Ordner umbenennen
+
+- Öffnen Sie das Kontextmenü auf eine der folgenden Arten:
+  - Klicken Sie mit der rechten Maustaste auf die Datei oder den Ordner
+  - Oder klicken Sie auf die drei Punkte rechts in der entsprechenden Zeile
+- Wählen Sie die Option „Umbenennen“.
+
+  <img src={require("./img/create-rename-move/umbenennen-option.png").default} alt="Umbenennen auswählen" width="400"/>
+
+- Geben Sie den neuen Namen für die Datei oder den Ordner in das angezeigte Fenster ein.
+- Bestätigen Sie mit „Umbenennen“.
+
+  <img src={require("./img/create-rename-move/umbenennen-popup.png").default} alt="Neuen Namen eingeben" width="400"/>
+
+Fertig. Der neue Name wurde übernommen.
+
+## Dateien oder Ordner verschieben
+
+- Treffen Sie zuerst eine Auswahl:
+  - Wählen Sie die Datei(en) oder Ordner aus, die Sie verschieben möchten.
+
+    <img src={require("./img/create-rename-move/ordner-auswaehlen.png").default} alt="Dateien oder Ordner auswählen" width="1920"/>
+
+  - Öffnen Sie das Kontextmenü:
+    - Klicken Sie mit der rechten Maustaste auf die Datei oder den Ordner
+    - Oder klicken Sie auf die drei Punkte in der entsprechenden Zeile
+  - Wählen Sie die Option „Ausschneiden“ aus dem Menü.
+
+    <img src={require("./img/create-rename-move/rechts-klick-ausschneiden.png").default} alt="Ausschneiden per Rechtsklick" width="400"/>
+
+    Alternativ können Sie die Funktion „Ausschneiden“ in der Aktionsleiste oben verwenden.
+
+    <img src={require("./img/create-rename-move/actionbar-ausschneiden.png").default} alt="Ausschneiden in der Aktionsleiste" width="1920"/>
+
+- Wählen Sie das Ziel aus:
+  - Navigieren Sie zu dem Ordner oder Speicherort, an den die Datei oder der Ordner verschoben werden soll.
+  - Klicken Sie in der Aktionsleiste auf „Hier einfügen“.
+
+    <img src={require("./img/create-rename-move/hier-einfuegen-button.png").default} alt="Hier einfügen" width="1920"/>
+
+    <img src={require("./img/create-rename-move/eingefuegte-datei.png").default} alt="Eingefügte Datei" width="1920"/>
+
+Die Datei oder der Ordner befindet sich jetzt am neuen Speicherort und nicht mehr am ursprünglichen Speicherort.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/delete-restore.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/delete-restore.md
new file mode 100644
index 000000000..2d322348a
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/delete-restore.md
@@ -0,0 +1,51 @@
+---
+sidebar_position: 3
+id: delete-restore
+title: Löschen - Wiederherstellen
+description: Löschen - Wiederherstellen
+draft: false
+---
+
+# Löschen - Wiederherstellen
+
+## Dateien und Ordner löschen
+
+- Wählen Sie die Datei(en) oder Ordner aus, die Sie löschen möchten.
+
+  <img src={require("./img/delete-restore/markierter-ordner.png").default} alt="Dateien oder Ordner auswählen" width="1920"/>
+
+- Öffnen Sie das Kontextmenü und wählen Sie "Löschen“.
+
+  <img src={require("./img/delete-restore/loeschen-optionen.png").default} alt="Löschen auswählen" width="1920"/>
+
+:::info
+Alternativ können Sie auch auf "Löschen“ in der Aktionsleiste klicken.
+:::
+
+- Die Dateien oder Ordner werden in den Bereich "Gelöschte Dateien“ verschoben. Sie können bei Bedarf von dort wiederhergestellt werden.
+
+  <img src={require("./img/delete-restore/ordner-in-geloeschte-dateien.png").default} alt="Dateien und Ordner in den gelöschten Dateien" width="1920"/>
+
+## Dateien und Ordner wiederherstellen
+
+- Klicken Sie in der linken Seitenleiste auf „Gelöschte Dateien“.
+- Dateien aus Ihrem persönlichen Bereich finden Sie unter "Persönlich“.
+- Dateien aus anderen Spaces, zum Beispiel "Platform Team“, finden Sie in den jeweiligen Spaces.
+
+  <img src={require("./img/delete-restore/struktur-in-geloeschte-dateien.png").default} alt="Struktur in den gelöschten Dateien" width="1920"/>
+
+- Klicken Sie auf die Datei(en) oder Ordner, die Sie wiederherstellen möchten.
+
+  <img src={require("./img/delete-restore/markierter-ordner-in-geloeschte-dateien.png").default} alt="Dateien oder Ordner zum Wiederherstellen auswählen" width="1920"/>
+
+- Klicken Sie mit der rechten Maustaste auf die Auswahl oder klicken Sie auf die drei Punkte daneben und wählen sie "Wiederherstellen"
+
+  <img src={require("./img/delete-restore/drei-punkte-menue-in-geloeschte-dateien.png").default} alt="Drei-Punkte-Menü in den gelöschten Dateien" width="1920"/>
+
+:::info
+Alternativ können Sie auch auf "Wiederherstellen“ in der Aktionsleiste klicken.
+:::
+
+:::note
+Die Dateien oder Ordner werden an ihren ursprünglichen Speicherort wiederhergestellt.
+:::
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/favorites.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/favorites.md
new file mode 100644
index 000000000..0e772594b
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/favorites.md
@@ -0,0 +1,41 @@
+---
+sidebar_position: 7
+id: favorites
+title: Favoriten
+description: Häufig verwendete Dateien für den schnellen Zugriff markieren
+draft: false
+---
+
+# Favoriten
+
+Mit OpenCloud 6.0.0 können Sie häufig verwendete Dateien und Ordner als Favoriten markieren, damit Sie schneller darauf zugreifen können. Die Funktion ist im Web-Client verfügbar.
+
+Favoriten werden serverseitig gespeichert, auf einer eigenen Favoriten-Seite angezeigt und sind auch in Suchergebnissen und Dateilisten sichtbar. Die Funktion funktioniert in persönlichen und Projekt-Spaces, einschließlich Unterordnern.
+
+## Ein Element als Favorit markieren
+
+- Öffnen Sie das Kontextmenü für eine Datei oder einen Ordner.
+  <img src={require("./img/favorites/add-to-favorites-menu.png").default} alt="Kontextmenü mit Favoriten-Aktion" width="1920"/>
+
+- Wählen Sie im Kontextmenü oder in den Batch-Aktionen „Zu Favoriten hinzufügen“.
+
+- Das Element wird sofort zu Ihren Favoriten hinzugefügt.
+
+## Favoriten öffnen
+
+- Öffnen Sie „Favoriten“ in der linken Seitenleiste des Web-Clients.
+  <img src={require("./img/favorites/favorites-personal.png").default} alt="Favoriten-Seite mit mehreren persönlichen Dateien" width="1920"/>
+
+- Die Favoriten-Seite zeigt die Elemente aus dem persönlichen Bereich zusammen an.
+
+## Einen Favoriten entfernen
+
+- Öffnen Sie das Kontextmenü erneut.
+  <img src={require("./img/favorites/remove-from-favorites-menu.png").default} alt="Kontextmenü mit Entfernen-aus-Favoriten-Aktion" width="1920"/>
+
+- Wählen Sie im Kontextmenü oder in den Batch-Aktionen „Aus Favoriten entfernen“.
+- Das Element wird aus Ihren Favoriten entfernt.
+
+:::note
+Spaces selbst können derzeit noch nicht als Favoriten markiert werden.
+:::
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/activity/aktivitaeten-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/activity/aktivitaeten-button.png
new file mode 100644
index 000000000..963faec95
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/activity/aktivitaeten-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/activity/aktivitaeten.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/activity/aktivitaeten.png
new file mode 100644
index 000000000..d7f78d22f
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/activity/aktivitaeten.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/activity/details-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/activity/details-button.png
new file mode 100644
index 000000000..331c7876f
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/activity/details-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/activity/drei-punkte-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/activity/drei-punkte-menue.png
new file mode 100644
index 000000000..867104fe3
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/activity/drei-punkte-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/actionbar-ausschneiden.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/actionbar-ausschneiden.png
new file mode 100644
index 000000000..cf210a34b
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/actionbar-ausschneiden.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/eingefuegte-datei.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/eingefuegte-datei.png
new file mode 100644
index 000000000..8d21ac203
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/eingefuegte-datei.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/erstellen-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/erstellen-button.png
new file mode 100644
index 000000000..b525e3bd0
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/erstellen-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/hier-einfuegen-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/hier-einfuegen-button.png
new file mode 100644
index 000000000..5fdde93d2
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/hier-einfuegen-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/neu-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/neu-button.png
new file mode 100644
index 000000000..2e1fa7464
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/neu-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/neu-optionen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/neu-optionen.png
new file mode 100644
index 000000000..4702233ab
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/neu-optionen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/ordner-auswaehlen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/ordner-auswaehlen.png
new file mode 100644
index 000000000..1072342ab
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/ordner-auswaehlen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/rechts-klick-ausschneiden.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/rechts-klick-ausschneiden.png
new file mode 100644
index 000000000..a8cf05270
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/rechts-klick-ausschneiden.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/umbenennen-option.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/umbenennen-option.png
new file mode 100644
index 000000000..3bce327d9
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/umbenennen-option.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/umbenennen-popup.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/umbenennen-popup.png
new file mode 100644
index 000000000..6c529d4eb
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/create-rename-move/umbenennen-popup.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/drei-punkte-menue-in-geloeschte-dateien.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/drei-punkte-menue-in-geloeschte-dateien.png
new file mode 100644
index 000000000..b4ee5d8d4
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/drei-punkte-menue-in-geloeschte-dateien.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/drei-punkte-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/drei-punkte-menue.png
new file mode 100644
index 000000000..e790981fd
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/drei-punkte-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/geloeschte-dateien.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/geloeschte-dateien.png
new file mode 100644
index 000000000..d796c32b1
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/geloeschte-dateien.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/loeschen-optionen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/loeschen-optionen.png
new file mode 100644
index 000000000..c904c5a7c
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/loeschen-optionen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/markierter-ordner-in-geloeschte-dateien.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/markierter-ordner-in-geloeschte-dateien.png
new file mode 100644
index 000000000..893677f8b
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/markierter-ordner-in-geloeschte-dateien.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/markierter-ordner.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/markierter-ordner.png
new file mode 100644
index 000000000..5f024a625
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/markierter-ordner.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/ordner-in-geloeschte-dateien.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/ordner-in-geloeschte-dateien.png
new file mode 100644
index 000000000..9a3560467
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/ordner-in-geloeschte-dateien.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/struktur-in-geloeschte-dateien.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/struktur-in-geloeschte-dateien.png
new file mode 100644
index 000000000..26522a0e3
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/struktur-in-geloeschte-dateien.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/wiederherstellungs-optionen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/wiederherstellungs-optionen.png
new file mode 100644
index 000000000..3c4cc8a89
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/delete-restore/wiederherstellungs-optionen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/favorites/add-to-favorites-menu.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/favorites/add-to-favorites-menu.png
new file mode 100644
index 000000000..7fb473278
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/favorites/add-to-favorites-menu.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/favorites/favorites-personal.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/favorites/favorites-personal.png
new file mode 100644
index 000000000..8059aee30
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/favorites/favorites-personal.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/favorites/remove-from-favorites-menu.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/favorites/remove-from-favorites-menu.png
new file mode 100644
index 000000000..87bda93f9
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/favorites/remove-from-favorites-menu.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/link/create-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/link/create-button.png
new file mode 100644
index 000000000..4ef3b0b1e
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/link/create-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/link/pop-up-window.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/link/pop-up-window.png
new file mode 100644
index 000000000..319dbacd4
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/link/pop-up-window.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/link/shortcut-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/link/shortcut-button.png
new file mode 100644
index 000000000..fcfbadb0e
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/link/shortcut-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/link/shortcut-right-click.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/link/shortcut-right-click.png
new file mode 100644
index 000000000..b790ae44a
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/link/shortcut-right-click.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/link/shortcut.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/link/shortcut.png
new file mode 100644
index 000000000..773d20ffd
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/link/shortcut.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/link/url-and-title.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/link/url-and-title.png
new file mode 100644
index 000000000..a8209fe45
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/link/url-and-title.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/markdown-editor/editor-open.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/markdown-editor/editor-open.png
new file mode 100644
index 000000000..925736fb4
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/markdown-editor/editor-open.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/markdown-editor/slash-menu.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/markdown-editor/slash-menu.png
new file mode 100644
index 000000000..22b8a91e4
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/markdown-editor/slash-menu.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/photos-and-videos/photo-roll-screenshot.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/photos-and-videos/photo-roll-screenshot.png
new file mode 100644
index 000000000..c4e8e8695
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/photos-and-videos/photo-roll-screenshot.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/photos-and-videos/video-screenshot.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/photos-and-videos/video-screenshot.png
new file mode 100644
index 000000000..34b60afd2
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/photos-and-videos/video-screenshot.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/readme-files/readme-list-view.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/readme-files/readme-list-view.png
new file mode 100644
index 000000000..e4dd4ba21
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/readme-files/readme-list-view.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/readme-files/readme-removed.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/readme-files/readme-removed.png
new file mode 100644
index 000000000..a5f478de0
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/readme-files/readme-removed.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/search/drop-down-menu-searchbar.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/search/drop-down-menu-searchbar.png
new file mode 100644
index 000000000..06b37eb5e
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/search/drop-down-menu-searchbar.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/search/search-example.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/search/search-example.png
new file mode 100644
index 000000000..3ecf5e159
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/search/search-example.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/search/searchbar.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/search/searchbar.png
new file mode 100644
index 000000000..cda5394e3
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/search/searchbar.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/tags/delete-a-tag.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/tags/delete-a-tag.png
new file mode 100644
index 000000000..aabb50509
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/tags/delete-a-tag.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/tags/details-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/tags/details-button.png
new file mode 100644
index 000000000..823eb92ba
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/tags/details-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/tags/tags-line.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/tags/tags-line.png
new file mode 100644
index 000000000..6a3254e11
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/tags/tags-line.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/tags/type-or-choose-a-tag.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/tags/type-or-choose-a-tag.png
new file mode 100644
index 000000000..065ad5379
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/tags/type-or-choose-a-tag.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/upload-download-unzip/entpacken-optionen-fullpage.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/upload-download-unzip/entpacken-optionen-fullpage.png
new file mode 100644
index 000000000..975232bef
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/upload-download-unzip/entpacken-optionen-fullpage.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/upload-download-unzip/herunterladen-optionen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/upload-download-unzip/herunterladen-optionen.png
new file mode 100644
index 000000000..231df1206
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/upload-download-unzip/herunterladen-optionen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/upload-download-unzip/hochladen-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/upload-download-unzip/hochladen-button.png
new file mode 100644
index 000000000..4f057360f
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/upload-download-unzip/hochladen-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/upload-download-unzip/hochladen-fenster.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/upload-download-unzip/hochladen-fenster.png
new file mode 100644
index 000000000..c571c13f1
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/upload-download-unzip/hochladen-fenster.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/upload-download-unzip/hochladen-optionen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/upload-download-unzip/hochladen-optionen.png
new file mode 100644
index 000000000..d65c704f8
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/upload-download-unzip/hochladen-optionen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/upload-download-unzip/markierte-datei.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/upload-download-unzip/markierte-datei.png
new file mode 100644
index 000000000..ae056e31d
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/upload-download-unzip/markierte-datei.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/versions/details-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/versions/details-button.png
new file mode 100644
index 000000000..7df9105fc
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/versions/details-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/versions/versionen-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/versions/versionen-button.png
new file mode 100644
index 000000000..45bcf8db2
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/versions/versionen-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/versions/versionen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/versions/versionen.png
new file mode 100644
index 000000000..4b1fc1db4
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/img/versions/versionen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/index.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/index.md
new file mode 100644
index 000000000..13a3de5d5
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/index.md
@@ -0,0 +1,54 @@
+---
+sidebar_position: 0
+id: files-and-folders-overview
+title: Dateien und Ordner verwalten
+---
+
+# Dateien und Ordner verwalten
+
+Lernen Sie, wie Sie Dateien und Ordner in OpenCloud organisieren, verwalten und prüfen.  
+Dieser Abschnitt behandelt typische Aufgaben wie Inhalte erstellen und verschieben, Dateien hochladen, gelöschte Elemente wiederherstellen und den Dateiverlauf prüfen.
+
+## In diesem Abschnitt
+
+### Inhalte organisieren und verwalten
+
+- [Dateien und Ordner erstellen, umbenennen und verschieben](./create-rename-move.md)  
+  Erstellen Sie neue Inhalte, ordnen Sie bestehende Dateien und Ordner neu und verschieben Sie Elemente an einen anderen Ort.
+
+- [Inhalte hochladen, herunterladen und entpacken](./upload-download-unzip.md)  
+  Laden Sie Dateien in OpenCloud hoch, speichern Sie sie auf Ihrem Gerät oder entpacken Sie ZIP-Archive.
+
+- [Elemente löschen und aus dem Papierkorb wiederherstellen](./delete-restore.md)  
+  Entfernen Sie Dateien und Ordner und stellen Sie sie bei Bedarf später wieder her.
+
+- [Markdown-Dateien bearbeiten](./markdown-editor.md)  
+  Bearbeiten Sie `README.md` und andere Markdown-Dateien direkt in OpenCloud mit Formatierungshilfen.
+
+- [README-Dateien in Ordnern](./readme-files.md)  
+  Fügen Sie einem Ordner eine `README.md`-Datei hinzu, damit OpenCloud sie oberhalb der Dateiliste rendert.
+
+### Inhalte finden und klassifizieren
+
+- [Fotos und Videos](./photos-and-videos.md)  
+  Zeigen Sie Fotos in der Vorschau an, blättern Sie durch einen Photo-Roll und spielen Sie Videos direkt im Web an.
+
+- [Nach Dateien und Inhalten suchen](./search.md)  
+  Finden Sie Dateien anhand des Namens oder durchsuchen Sie Inhalte innerhalb von Dateien.
+
+- [Favoriten](./favorites.md)  
+  Markieren Sie häufig verwendete Dateien für den schnellen Zugriff und sammeln Sie sie auf einer eigenen Favoriten-Seite.
+
+- [Tags hinzufügen und entfernen](./tags.md)  
+  Verwenden Sie Tags, um Dateien und Ordner zu organisieren und leichter wiederzufinden.
+
+- [Verknüpfungen zu Dateien oder Weblinks erstellen](./shortcut.md)  
+  Fügen Sie Verknüpfungen zu häufig verwendeten Dateien oder externen Webseiten für einen schnelleren Zugriff hinzu.
+
+### Dateiverlauf und Aktivität prüfen
+
+- [Dateiversionen und Aktivitätshistorie ansehen](./versions.md)  
+  Prüfen Sie frühere Dateiversionen und verfolgen Sie, wie sich eine Datei im Laufe der Zeit verändert hat.
+
+- [Dateiaktivität prüfen](./activity.md)  
+  Sehen Sie, welche Aktionen an einer Datei oder einem Ordner durchgeführt wurden und von wem die Änderungen stammen.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/markdown-editor.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/markdown-editor.md
new file mode 100644
index 000000000..48b5df0fe
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/markdown-editor.md
@@ -0,0 +1,61 @@
+---
+id: markdown-editor
+sidebar_position: 3.6
+title: Markdown-Dateien bearbeiten
+description: Erfahren Sie, wie Sie Markdown-Dateien mit dem OpenCloud Tiptap-Editor bearbeiten.
+---
+
+# Markdown-Dateien bearbeiten
+
+OpenCloud verwendet einen Tiptap-basierten Markdown-Editor für Dateien wie `README.md` und andere `.md`-Dateien. Der Editor hilft Ihnen dabei, Inhalte zu schreiben und zu formatieren, auch wenn Sie die Markdown-Syntax nicht gut kennen.
+
+## So funktioniert der Editor
+
+Wenn Sie eine Markdown-Datei öffnen, zeigt OpenCloud sie im Editor an, sodass Sie die Datei direkt im Browser bearbeiten können.
+
+<img src={require("./img/markdown-editor/editor-open.png").default} alt="Markdown-Editor mit einer README-Datei geöffnet" width="1920"/>
+
+Sie können Überschriften, Listen, Links, Zitate, Code und andere häufige Formatierungen hinzufügen, ohne die Dateiansicht zu verlassen.
+
+Während Sie bearbeiten, zeigt OpenCloud den Markdown-Inhalt direkt gerendert an, sodass Sie sofort sehen können, wie die Datei aussehen wird.
+
+Der Editor unterstützt außerdem das Einfügen von Bildern und das Erstellen von Tabellen, sodass Sie reichhaltigere Markdown-Dateien direkt in OpenCloud einfacher erstellen können.
+
+## Slash-Kürzel verwenden
+
+Geben Sie `/` in einer neuen Zeile ein, um das Formatierungsmenü zu öffnen.
+
+Das Menü gibt Ihnen einen schnellen Überblick über die verfügbaren Formatierungsoptionen und erlaubt es Ihnen, diese zu nutzen, ohne sich jede Tastenkombination merken zu müssen.
+
+<img src={require("./img/markdown-editor/slash-menu.png").default} alt="Slash-Menü im Markdown-Editor" width="1920"/>
+
+Das ist besonders hilfreich, wenn Sie schnell formatieren möchten und dabei die Hände auf der Tastatur lassen wollen.
+
+## Formatierungsleiste verwenden
+
+Verwenden Sie die Formatierungsleiste oberhalb des Editors, um häufige Markdown-Elemente einzufügen.
+
+Klicken Sie auf die Schaltfläche `Heading`, um eine Überschriftenebene auszuwählen, oder verwenden Sie die anderen Schaltflächen für Fett, Kursiv, Listen, Code, Bilder und Tabellen.
+
+Das ist besonders hilfreich, wenn Sie Inhalte schnell formatieren möchten, ohne sich jede Markdown-Tastenkombination merken zu müssen.
+
+## Unterstützte Formatierung
+
+Der Markdown-Editor unterstützt gängige Formatierungsoptionen für alle Markdown-Dateien. Sie können die Formatierungsleiste oder das Slash-Menü verwenden, um Folgendes einzufügen:
+
+- Überschriften
+- Fett und kursiven Text
+- Aufzählungs- und nummerierte Listen
+- Zitate
+- Inline-Code und Codeblöcke
+- Links
+- Bilder
+- Tabellen
+
+## Gut zu wissen
+
+- Der Editor funktioniert für Markdown-Dateien wie `README.md`.
+- Sie können das Formatierungsmenü verwenden, um strukturierte Inhalte Schritt für Schritt zu erstellen.
+- Die Datei bleibt eine normale Markdown-Datei und kann daher auch außerhalb von OpenCloud verwendet werden.
+
+Wenn die Datei gespeichert wird, wird der Markdown-Inhalt in derselben `.md`-Datei gespeichert und kann überall dort gerendert werden, wo Markdown unterstützt wird.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/photos-and-videos.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/photos-and-videos.md
new file mode 100644
index 000000000..3024dff2f
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/photos-and-videos.md
@@ -0,0 +1,32 @@
+---
+sidebar_position: 3.6
+title: Fotos und Videos
+description: Erfahren Sie, wie OpenCloud Fotos in der Vorschau anzeigt und Videos direkt im Web abspielt.
+---
+
+# Fotos und Videos
+
+OpenCloud kann Fotos in der Vorschau anzeigen und Videos direkt in der Weboberfläche abspielen.
+Dadurch können Sie Medien einfacher prüfen, ohne die Dateien zuerst herunterladen zu müssen.
+
+## Fotovorschau
+
+Öffnen Sie ein Foto in der Vorschauansicht, um durch den Photo-Roll zu blättern.
+
+<img src={require("./img/photos-and-videos/photo-roll-screenshot.png").default} alt="Photo-Roll-Ansicht in OpenCloud" width="1920"/>
+
+Der Fotobetrachter unterstützt eine Navigation im Photo-Roll-Stil, sodass Sie durch eine Bilderserie blättern können, ohne die Vorschau zu verlassen.
+
+## Videowiedergabe
+
+Videos öffnen sich im gleichen Vorschaubereich und können direkt im Browser abgespielt werden.
+
+<img src={require("./img/photos-and-videos/video-screenshot.png").default} alt="Videovorschau in OpenCloud" width="1920"/>
+
+Die Videowiedergabe funktioniert direkt in OpenCloud, sodass Sie Clips prüfen können, ohne sie zuerst herunterzuladen.
+
+## Hinweise
+
+- Das Verhalten hängt vom Dateityp und von den Browserfunktionen ab.
+- Sehr große Mediendateien können trotzdem einen Moment zum Laden benötigen.
+- Diese Funktion ist für die schnelle Ansicht gedacht, nicht für eine erweiterte Medienbearbeitung.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/readme-files.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/readme-files.md
new file mode 100644
index 000000000..62c78fbeb
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/readme-files.md
@@ -0,0 +1,52 @@
+---
+sidebar_position: 3.5
+title: README-Dateien in Ordnern
+description: Erfahren Sie, wie README.md-Dateien in Ordnern in OpenCloud gerendert werden.
+---
+
+# README-Dateien in Ordnern
+
+Wenn ein Ordner eine Datei mit dem Namen `README.md` enthält, rendert OpenCloud deren Markdown-Inhalt oberhalb der Dateiliste.
+
+<img src={require("./img/readme-files/readme-list-view.png").default} alt="README in der Listenansicht gerendert, während die Datei noch sichtbar ist" width="1920"/>
+
+## README-Datei erstellen
+
+1. Öffnen Sie den Ordner, in dem Sie das README hinzufügen möchten.
+2. Erstellen oder laden Sie eine Datei mit dem Namen `README.md` hoch.
+3. Fügen Sie Ihren Markdown-Inhalt hinzu und speichern Sie die Datei.
+
+OpenCloud rendert den Inhalt, wenn der Ordner geöffnet oder aktualisiert wird.
+
+## Unterstützter Dateiname
+
+Der Dateiname muss genau so lauten:
+
+```text
+README.md
+```
+
+## Beispiel
+
+Eine `README.md`-Datei kann zum Beispiel folgenden Markdown-Inhalt enthalten:
+
+```markdown
+# Fotos
+
+Dieser Ordner enthält visuelle Beispiele für Vorschauen und Doku-Screenshots.
+
+Die Bilder werden verwendet, um das Verhalten der Listenansicht, der Kachelansicht und der Bildvorschau in OpenCloud zu zeigen.
+
+## Dateien
+
+- moon-surface-public-domain.jpg
+- rotated-chessboard-photo.jpg
+- vintage-computer-terminal.jpg
+- Space-Nebula.jpg
+```
+
+## README-Bereich entfernen
+
+Löschen oder benennen Sie `README.md` um, um den gerenderten Bereich zu entfernen.
+
+<img src={require("./img/readme-files/readme-removed.png").default} alt="Ordner ohne den gerenderten README-Bereich" width="1920"/>
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/search.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/search.md
new file mode 100644
index 000000000..473ead71f
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/search.md
@@ -0,0 +1,25 @@
+---
+sidebar_position: 4
+id: search
+title: Suche
+description: Nutzen der Suche in OpenCloud
+draft: false
+---
+
+# Die Suche in OpenCloud verwenden
+
+Sie können die Suchleiste in der oberen Leiste verwenden, um Dateien und Inhalte schnell zu finden.
+
+## So funktioniert die Suche
+
+- Die Suchleiste befindet sich oben in der Web-Oberfläche.
+  <img src={require("./img/search/searchbar.png").default} alt="Suchleiste" width="1920"/>
+- Kurzbefehle: Drücken Sie `/` oder geben Sie `s` ein, um die Suchleiste zu fokussieren.
+
+- Klicken Sie auf das Dropdown-Menü neben der Suchleiste.
+- Wählen Sie, ob Sie in allen Dateien oder nur im aktuellen Ordner suchen möchten.
+  <img src={require("./img/search/drop-down-menu-searchbar.png").default} alt="Auswahl, wo gesucht werden soll" width="500"/>
+- Die Suchfunktion sucht sowohl nach Dateinamen als auch nach dem Inhalt der Dateien, um relevante Ergebnisse anzuzeigen.
+  <img src={require("./img/search/search-example.png").default} alt="Suchbeispiel" width="500"/>
+
+Mit diesen Schritten finden Sie Ihre Dateien und Ordner schnell und effizient!
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/shortcut.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/shortcut.md
new file mode 100644
index 000000000..6bce8f24a
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/shortcut.md
@@ -0,0 +1,36 @@
+---
+sidebar_position: 5
+id: shortcut
+title: Verknüpfung
+description: Verknüpfung in OpenCloud erstellen
+draft: false
+---
+
+# Verknüpfung
+
+Mit OpenCloud können Sie Verknüpfungen zu Websites oder Dateien erstellen.
+
+## Verknüpfung erstellen
+
+- Öffnen Sie das Menü "+ Neu“ und wählen Sie "Verknüpfung“.
+
+  <img src={require("./img/link/shortcut-button.png").default} alt="Verknüpfung auswählen" width="1920"/>
+
+- Geben Sie eine URL oder einen Dateinamen ein.
+  - Sie können auch eine Datei aus der Liste auswählen, nachdem Sie ein paar Buchstaben eingegeben haben.
+
+  <img src={require("./img/link/pop-up-window.png").default} alt="Link oder Datei im Popup-Fenster eingeben" width="500"/>
+
+- Geben Sie einen Namen für die Verknüpfung ein.
+
+  <img src={require("./img/link/url-and-title.png").default} alt="Namen für die Verknüpfung eingeben" width="500"/>
+
+- Erstellen Sie die Verknüpfung, indem Sie auf "Erstellen“ klicken.
+
+  <img src={require("./img/link/create-button.png").default} alt="Auf Erstellen klicken" width="500"/>
+
+## Verknüpfung verwenden
+
+- Öffnen Sie das Kontextmenü, klicken Sie auf "Öffnen mit“ und wählen Sie "Verknüpfung öffnen“.
+
+  <img src={require("./img/link/shortcut-right-click.png").default} alt="Rechtsklick auf die Verknüpfung" width="1920"/>
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/tags.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/tags.md
new file mode 100644
index 000000000..5bcf96715
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/tags.md
@@ -0,0 +1,35 @@
+---
+sidebar_position: 6
+id: tags
+title: Tags
+description: Tags mit OpenCloud hinzufügen und verwalten
+draft: false
+---
+
+# Tags mit OpenCloud hinzufügen und verwalten
+
+Mit OpenCloud können Sie Dateien und Ordner mit Tags versehen, damit Sie diese leichter suchen oder gruppieren können.
+
+## Tag hinzufügen
+
+- Öffnen Sie das Kontextmenü für die Datei oder den Ordner.
+- Wählen Sie die Option „Details“.
+  <img src={require("./img/tags/details-button.png").default} alt="Details im Kontextmenü auswählen" width="1920"/>
+
+## Tag hinzufügen
+
+- Klicken Sie in das Eingabefeld neben „Tags“.
+  <img src={require("./img/tags/tags-line.png").default} alt="Eingabefeld neben Tags" width="400"/>
+- Wählen Sie einen vorhandenen Tag aus oder geben Sie einen neuen Begriff ein, um einen neuen Tag zu erstellen.
+  <img src={require("./img/tags/type-or-choose-a-tag.png").default} alt="Tag-Namen eingeben" width="400"/>
+
+  Der Tag wird hinzugefügt und ist jetzt mit der Datei oder dem Ordner verknüpft.
+
+## Tag entfernen
+
+- Öffnen Sie die „Details“ der Datei oder des Ordners erneut.
+- Suchen Sie den Tag, den Sie entfernen möchten.
+- Klicken Sie auf das „x“ neben dem Tag, um ihn zu löschen.
+  <img src={require("./img/tags/delete-a-tag.png").default} alt="Auf das x neben dem Tag klicken" width="400"/>
+
+  Die Datei oder der Ordner ist nun nicht mehr mit diesem Tag verknüpft.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/upload-download-unzip.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/upload-download-unzip.md
new file mode 100644
index 000000000..7d8009415
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/upload-download-unzip.md
@@ -0,0 +1,59 @@
+---
+sidebar_position: 2
+id: upload-download-unzip
+title: Hochladen - Herunterladen - Entpacken
+description: Hochladen - Herunterladen - Entpacken
+draft: false
+---
+
+# Hochladen - Herunterladen - Entpacken
+
+## Dateien oder Ordner hochladen
+
+- Öffnen Sie das Menü „+ Neu“ in der linken Seitenleiste.
+
+  <img src={require("./img/upload-download-unzip/hochladen-button.png").default} alt="Hochladen-Schaltfläche" width="1920"/>
+
+- Wählen Sie aus, ob Sie Dateien oder Ordner hochladen möchten.
+
+  <img src={require("./img/upload-download-unzip/hochladen-optionen.png").default} alt="Datei oder Ordner auswählen" width="400" style={{ display: "block", marginTop: "1rem", marginBottom: "1rem" }}/>
+
+- Dateien oder Ordner auswählen:
+  - Wählen Sie im sich öffnenden Fenster die gewünschten Dateien oder Ordner aus.
+  - Mehrere Dateien oder Ordner können gleichzeitig ausgewählt werden.
+- Upload bestätigen:
+  - Klicken Sie auf „Öffnen“, um den Upload zu starten.
+
+    <img src={require("./img/upload-download-unzip/hochladen-fenster.png").default} alt="Upload bestätigen" width="500"/>
+
+  - Nach Abschluss des Uploads erscheint eine Meldung in der unteren rechten Ecke.
+
+- Alternativ:
+  - Ziehen Sie die Dateien oder Ordner direkt aus Ihrem Explorer-Fenster in den Browser, um sie hochzuladen.
+
+## Dateien oder Ordner herunterladen
+
+- Wählen Sie die Datei(en) aus, die Sie herunterladen möchten.
+
+  <img src={require("./img/upload-download-unzip/markierte-datei.png").default} alt="Dateien für den Download auswählen" width="1920"/>
+
+- Öffnen Sie das Kontextmenü, indem Sie mit der rechten Maustaste klicken oder auf die drei Punkte neben der Datei klicken.
+
+  <img src={require("./img/upload-download-unzip/herunterladen-optionen.png").default} alt="Download-Optionen" width="1920"/>
+
+- Wählen Sie „Herunterladen“ aus dem Menü oder in der oberen Leiste.
+
+- Wenn Sie mehrere Dateien oder Ordner herunterladen, werden diese als ZIP-Datei gespeichert.
+- Entpacken Sie die ZIP-Datei nach dem Herunterladen auf Ihrem Gerät.
+
+## Entpacken
+
+Wenn die Funktion aktiviert ist, können Sie gepackte Dateien in der Cloud entpacken.
+
+- Wählen Sie die ZIP-Datei in der Dateiliste aus und öffnen Sie das Kontextmenü mit einem Rechtsklick auf die Datei oder über die drei Punkte daneben.
+- Wählen Sie „Entpacken“.
+
+  <img src={require("./img/upload-download-unzip/entpacken-optionen-fullpage.png").default} alt="Entpacken-Optionen im Vollbild" width="1920"/>
+
+- Die Inhalte werden direkt in der Cloud entpackt und erscheinen im aktuellen Ordner.
+- Sobald der Vorgang abgeschlossen ist, erscheint eine Benachrichtigung.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/versions.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/versions.md
new file mode 100644
index 000000000..25cdd94b6
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/files-and-folders/versions.md
@@ -0,0 +1,29 @@
+---
+sidebar_position: 7
+id: versions
+title: Versionen
+description: Verwalten der Versionen von Dateien OpenCloud
+draft: false
+---
+
+# Verwalten von Dateiversionen in OpenCloud
+
+OpenCloud speichert verschiedene Versionen von Dateien. So können Sie frühere Versionen wiederherstellen oder herunterladen:
+
+## Versionen anzeigen und wiederherstellen
+
+- Details öffnen
+  - Klicken Sie mit der rechten Maustaste auf die Datei oder klicken Sie auf die drei Punkte in der entsprechenden Dateizeile.
+  - Wählen Sie „Details“ aus dem Kontextmenü aus.
+    <img src={require("./img/versions/details-button.png").default} alt="Details auswählen" width="1920"/>
+
+- Versionen auswählen
+  - Wählen Sie in der rechten Seitenleiste den Punkt „Versionen“ aus.
+    <img src={require("./img/versions/versionen-button.png").default} alt="Versionen auswählen" width="400" style={{ display: "block", marginTop: "1rem", marginBottom: "1rem" }}/>
+
+- Versionen anzeigen
+  - Alle Versionen der Datei werden angezeigt.
+  - Sie können nun die gewünschte Version wiederherstellen oder herunterladen.
+    <img src={require("./img/versions/versionen.png").default} alt="Alle Versionen anzeigen" width="400" style={{ display: "block", marginTop: "1rem", marginBottom: "1rem" }}/>
+
+Mit diesen Schritten können Sie jederzeit auf ältere Versionen Ihrer Dateien zugreifen.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/_category_.json b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/_category_.json
new file mode 100644
index 000000000..ee32c9a10
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Benutzeroberfläche und Navigation",
+  "position": 2
+}
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/account-settings.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/account-settings.md
new file mode 100644
index 000000000..ca6131805
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/account-settings.md
@@ -0,0 +1,83 @@
+---
+sidebar_position: 2
+id: settings
+title: Kontoeinstellungen
+description: Einstellungen für das Benutzerkonto in OpenCloud
+draft: false
+---
+
+# Einstellungen für Ihr Benutzerkonto in OpenCloud
+
+In OpenCloud haben Sie die Möglichkeit, verschiedene Einstellungen für Ihr Benutzerkonto vorzunehmen und es an Ihre Bedürfnisse anzupassen.
+
+## Auf die Einstellungen zugreifen
+
+- Klicken Sie oben rechts auf Ihren Avatar.
+- Wählen Sie den Punkt „Einstellungen“.
+  <img src={require("./img/account-settings/access.png").default} alt="Einstellungen öffnen" width="400" style={{ display: "block", marginTop: "1rem", marginBottom: "1rem" }}/>
+
+## Kontoinformationen
+
+In den Einstellungen können Sie zwischen verschiedenen Abschnitten wählen:
+
+### Profil
+
+- Profilbild
+- Benutzername / Login-Name
+- Vor- und Nachname
+- E-Mail-Adresse
+- Persönlicher Speicherplatz
+- Gruppenmitgliedschaften
+
+<img src={require("./img/account-settings/account-information.png").default} alt="Kontoinformationen" width="1920"/>
+
+### Avatar
+
+Im Bereich Profilbild können Sie Ihr Avatar-Bild ändern:
+
+- Klicken Sie auf „Hochladen“ unter Ihrem Avatar-Symbol.
+  <img src={require("./img/account-settings/avatar-menu.png").default} alt="Avatar-Menü" width="400" style={{ display: "block", marginTop: "1rem", marginBottom: "1rem" }}/>
+- Wählen Sie Ihr Avatar-Bild aus und klicken Sie auf „Hochladen“.
+  <img src={require("./img/account-settings/avatar-upload.png").default} alt="Avatar hochladen" width="500"/>
+- Es öffnet sich nun ein Fenster, in dem Sie Ihr Bild anpassen können. Klicken Sie anschließend auf „Set“.
+  <img src={require("./img/account-settings/avatar-settings.png").default} alt="Avatar-Einstellungen" width="400" style={{ display: "block", marginTop: "1rem", marginBottom: "1rem" }}/>
+- Danach wird Ihr Avatar in Ihrem Konto angezeigt.
+  <img src={require("./img/account-settings/visible-avatar.png").default} alt="Sichtbarer Avatar" width="1920"/>
+
+## Einstellungen
+
+Je nach Grundkonfiguration können Sie die folgenden Optionen ändern:
+
+- Sprache:  
+  Wählen Sie die gewünschte Sprache für Ihre Benutzeroberfläche.
+- Passwort:  
+  Ändern Sie Ihr Passwort für den Zugriff auf Ihr Benutzerkonto.
+- Design (Theme):  
+  Passen Sie das Erscheinungsbild der Benutzeroberfläche nach Ihren Vorlieben an.
+- E-Mail-Benachrichtigungen:  
+  Legen Sie fest, welche E-Mail-Benachrichtigungen Sie von OpenCloud erhalten möchten.
+- Anzeigeoptionen:  
+  Mit den WebDAV-Einstellungen legen Sie fest, ob auf Dateien und Ordner extern zugegriffen werden kann.
+  <img src={require("./img/account-settings/preferences.png").default} alt="Einstellungen" width="1920"/>
+
+## Erweiterungen
+
+Unter „Erweiterungen“ können Sie installierte Erweiterungen konfigurieren, wie z. B. die Fortschrittsanzeige, sofern verfügbar.
+<img src={require("./img/account-settings/extensions.png").default} alt="Erweiterungen" width="1920"/>
+
+## Kalender
+
+Unter „Kalender“ können Sie auf Ihren persönlichen Kalender zugreifen und ihn, sofern konfiguriert, mit Drittanbieter-Apps wie Thunderbird, Apple Kalender und anderen integrieren.
+
+<img src={require("./img/account-settings/calendar.png").default} alt="Kalender" width="1920"/>
+
+## DSGVO
+
+Unter „DSGVO“ können Sie bei Bedarf einen Export Ihrer personenbezogenen Daten anfordern.
+<img src={require("./img/account-settings/gdpr.png").default} alt="DSGVO" width="1920"/>
+
+## App-Tokens
+
+Mit „App-Tokens“ können Sie externe Apps und Dienste (wie WebDAV-Clients) sicher verbinden, ohne Ihr Hauptpasswort zu verwenden.
+
+<img src={require("./img/account-settings/app-tokens.png").default} alt="App-Tokens" width="1920"/>
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/file-list-adjustments.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/file-list-adjustments.md
new file mode 100644
index 000000000..dc09c5fc8
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/file-list-adjustments.md
@@ -0,0 +1,31 @@
+---
+sidebar_position: 3
+id: customization-file-list
+title: Anpassungen der Datei-Liste
+description: Anpassungen der Datei-Liste in OpenCloud
+draft: false
+---
+
+# Anpassungen der Datei-Liste in OpenCloud
+
+Wenn Sie auf das Einstellungssymbol auf der rechten Seite der Benutzeroberfläche klicken, gelangen Sie zu den Optionen für die Anpassung der Ansicht. Hier können Sie die Anzeige anpassen
+
+## Verfügbare Optionen
+
+<img src={require("./img/files-list-adjustment/einstellungs-button.png").default} alt="Settings icon" width="400"/>
+
+- Versteckte Dateien anzeigen
+  - Aktivieren oder deaktivieren Sie die Anzeige von versteckten Dateien.
+  - Bei versteckten Dateien handelt es sich oft um System- oder Konfigurationsdateien.
+
+- Dateierweiterungen anzeigen
+  - Legen Sie fest, ob die Dateierweiterungen (z. B. `.docx`, `.jpg`) hinter den Dateinamen angezeigt werden sollen. Dies erleichtert die Identifizierung von Dateitypen.
+
+- Dateien pro Seite
+  - Geben Sie an, wie viele Dateien pro Seite in einem Ordner angezeigt werden sollen.
+  - Nützlich für das Navigieren in Ordnern mit vielen Dateien.
+
+- Kachelgröße
+  - Passen Sie die Größe der Symbole und Schaltflächen an:
+  - Kleine Kacheln für eine kompaktere Ansicht.
+  - Große Kacheln für eine übersichtlichere Ansicht.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/access.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/access.png
new file mode 100644
index 000000000..29a09b03a
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/access.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/account-information.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/account-information.png
new file mode 100644
index 000000000..711cb7013
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/account-information.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/app-tokens.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/app-tokens.png
new file mode 100644
index 000000000..7a7b1f65c
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/app-tokens.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/avatar-menu.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/avatar-menu.png
new file mode 100644
index 000000000..1035f544d
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/avatar-menu.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/avatar-settings.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/avatar-settings.png
new file mode 100644
index 000000000..901d273de
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/avatar-settings.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/avatar-upload.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/avatar-upload.png
new file mode 100644
index 000000000..7504ac258
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/avatar-upload.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/calendar.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/calendar.png
new file mode 100644
index 000000000..94523b529
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/calendar.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/extensions.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/extensions.png
new file mode 100644
index 000000000..025c8589b
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/extensions.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/gdpr.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/gdpr.png
new file mode 100644
index 000000000..8867ce89e
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/gdpr.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/preferences.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/preferences.png
new file mode 100644
index 000000000..0b0c7064b
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/preferences.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/visible-avatar.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/visible-avatar.png
new file mode 100644
index 000000000..bd12c1503
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/account-settings/visible-avatar.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/files-list-adjustment/einstellungs-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/files-list-adjustment/einstellungs-button.png
new file mode 100644
index 000000000..db448b93c
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/files-list-adjustment/einstellungs-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/files-list-adjustment/settings-icon.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/files-list-adjustment/settings-icon.png
new file mode 100644
index 000000000..ba901dd78
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/files-list-adjustment/settings-icon.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/overview/marker.svg b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/overview/marker.svg
new file mode 100644
index 000000000..c0d261367
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/overview/marker.svg
@@ -0,0 +1,60 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1180 900" width="1180" height="900" role="img" aria-label="OpenCloud overview markers">
+<defs><filter id="markerShadow" x="-20%" y="-20%" width="140%" height="140%"><feDropShadow dx="0" dy="1" stdDeviation="1.2" flood-opacity="0.18"/></filter></defs>
+<g fill="#f5401d" filter="url(#markerShadow)">
+<polygon points="69,353 111,360 69,367"/>
+<circle cx="48" cy="360" r="23"/>
+<polygon points="1096,79 1103,37 1110,79"/>
+<circle cx="1103" cy="100" r="23"/>
+<polygon points="226,23 268,30 226,37"/>
+<circle cx="205" cy="30" r="23"/>
+<polygon points="681,21 723,28 681,35"/>
+<circle cx="660" cy="28" r="23"/>
+<polygon points="328,619 335,577 342,619"/>
+<circle cx="335" cy="640" r="23"/>
+<polygon points="324,67 282,74 324,81"/>
+<circle cx="345" cy="74" r="23"/>
+<polygon points="448,146 455,176 462,146"/>
+<circle cx="455" cy="125" r="23"/>
+<polygon points="696,81 738,88 696,95"/>
+<circle cx="675" cy="88" r="23"/>
+<polygon points="807,81 765,88 807,95"/>
+<circle cx="828" cy="88" r="23"/>
+<polygon points="1135,79 1142,37 1149,79"/>
+<circle cx="1142" cy="100" r="23"/>
+<polygon points="1104,338 1146,345 1104,352"/>
+<circle cx="1083" cy="345" r="23"/>
+<polygon points="809,153 767,160 809,167"/>
+<circle cx="830" cy="160" r="23"/>
+<polygon points="824,507 782,514 824,521"/>
+<circle cx="845" cy="514" r="23"/>
+<polygon points="1101,570 1143,577 1101,584"/>
+<circle cx="1080" cy="577" r="23"/>
+<polygon points="1101,618 1143,625 1101,632"/>
+<circle cx="1080" cy="625" r="23"/>
+<polygon points="1101,666 1143,673 1101,680"/>
+<circle cx="1080" cy="673" r="23"/>
+<polygon points="1101,713 1143,720 1101,727"/>
+<circle cx="1080" cy="720" r="23"/>
+<polygon points="553,719 560,677 567,719"/>
+<circle cx="560" cy="740" r="23"/>
+</g>
+<g fill="#ffffff" font-family="Arial, Helvetica, sans-serif" font-weight="700" font-size="21" text-anchor="middle" dominant-baseline="central">
+<text x="48" y="360">1</text>
+<text x="1103" y="100">2</text>
+<text x="205" y="30">3</text>
+<text x="660" y="28">4</text>
+<text x="335" y="640">5</text>
+<text x="345" y="74">6</text>
+<text x="455" y="125">7</text>
+<text x="675" y="88">8</text>
+<text x="828" y="88">9</text>
+<text x="1142" y="100">10</text>
+<text x="1083" y="345">11</text>
+<text x="830" y="160">12</text>
+<text x="845" y="514">13</text>
+<text x="1080" y="577">14</text>
+<text x="1080" y="625">15</text>
+<text x="1080" y="673">16</text>
+<text x="1080" y="720">17</text>
+<text x="560" y="740">18</text>
+</g></svg>
\ No newline at end of file
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/overview/ueberblick.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/overview/ueberblick.png
new file mode 100644
index 000000000..9f191daeb
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/overview/ueberblick.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/view-modes/kachel.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/view-modes/kachel.png
new file mode 100644
index 000000000..bdee75c17
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/view-modes/kachel.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/view-modes/klassisch.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/view-modes/klassisch.png
new file mode 100644
index 000000000..3cbbf8d8c
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/view-modes/klassisch.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/view-modes/verdichtet.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/view-modes/verdichtet.png
new file mode 100644
index 000000000..01f5a355b
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/img/view-modes/verdichtet.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/index.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/index.md
new file mode 100644
index 000000000..6aea7de46
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/index.md
@@ -0,0 +1,27 @@
+---
+title: Web Benutzeroberfläche und Navigation
+---
+
+# Web Benutzeroberfläche und Navigation
+
+Der Web Client ist die zentrale Oberfläche von OpenCloud und bietet vollen Zugriff im Browser, ohne dass zusätzliche
+Software installiert werden muss.
+
+Dieser Abschnitt erklärt die wichtigsten Bereiche der Oberfläche und zeigt, wie Sie den Web Client nutzen, die
+Dateiliste anpassen und Ihre Kontoeinstellungen personalisieren.
+
+## In diesem Abschnitt
+
+- [Überblick](./overview.md)  
+  Machen Sie sich mit den wichtigsten Bereichen des Web Clients vertraut, darunter Seitenleiste, obere Leiste,
+  Dateiliste und Aktionsbereiche.
+
+- [Kontoeinstellungen](./account-settings.md)  
+  Verwalten Sie Ihr Profil, Ihre Einstellungen, Ihr Avatarbild, den Kalenderzugriff, den DSGVO-Export und App-Tokens.
+
+- [Dateiliste anpassen](./file-list-adjustments.md)  
+  Passen Sie an, wie Dateien angezeigt werden, einschließlich versteckter Dateien, Dateiendungen, Seitennummerierung und
+  Kachelgröße.
+
+- [Ansichtsmodi](./view-modes.md)  
+  Wechseln Sie zwischen Tabellen-, Kompakt- und Kachelansicht, um die Dateiliste anders darzustellen.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/overview.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/overview.md
new file mode 100644
index 000000000..9c49dc704
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/overview.md
@@ -0,0 +1,109 @@
+---
+sidebar_position: 1
+id: overview
+title: Übersicht
+description: Überblick über die Web-Benutzeroberfläche
+draft: false
+---
+
+import OverviewMarker from "./img/overview/marker.svg";
+
+# Überblick der Web-Benutzeroberfläche
+
+Die OpenCloud Web-Benutzeroberfläche besteht aus mehreren Bereichen, die Ihnen helfen, effizient mit Dateien und Einstellungen zu arbeiten.
+
+<div style={{ position: "relative", display: "inline-block", width: "100%", maxWidth: "1920px" }}>
+  <img
+    src={require("./img/overview/ueberblick.png").default}
+    alt="Übersicht"
+    width="1920"
+    style={{ display: 'block', width: '100%', height: 'auto' }}
+  />
+  <OverviewMarker
+    aria-hidden="true"
+    style={{
+      position: 'absolute',
+      inset: 0,
+      width: '100%',
+      height: '100%',
+      pointerEvents: 'none',
+      zIndex: 1,
+    }}
+  />
+</div>
+
+## 1. Linke Seitenleiste
+
+Die Seitenleiste enthält Navigationselemente wie Spaces, Dateien, Freigaben und Einstellungen.
+
+## 2. App-Switcher
+
+Das Menü in der rechten oberen Ecke ermöglicht es Ihnen, zwischen verschiedenen Apps und Modulen zu wechseln.
+
+## 3. Obere Leiste
+
+Die obere Leiste enthält wichtige Funktionen wie die Suchleiste, Benutzeraktionen und globale Einstellungen.
+
+## 4. Suchleiste
+
+Ermöglicht Ihnen das schnelle Auffinden von Dateien, Ordnern oder Spaces.
+
+## 5. Dateiliste
+
+Zeigt alle Dateien und Ordner in der ausgewählten Ansicht an.
+
+## 6. Breadcrumbs-Menü
+
+Zeigt den aktuellen Pfad Ihrer Navigation an und ermöglicht es Ihnen, schnell zu vorherigen Verzeichnissen zurückzuspringen.
+
+## 7. Batch-Aktionen
+
+Ermöglicht Ihnen das Bearbeiten, Verschieben oder Löschen mehrerer ausgewählter Dateien zur gleichen Zeit.
+
+## 8. Ansichtsmodi
+
+Bietet verschiedene Anzeigeoptionen für die Dateiliste:
+
+- Listenansicht
+- Kachelansicht
+- Komprimierte Ansicht
+
+## 9. Ansichtseinstellungen
+
+Hier können Sie zusätzliche Anzeigeoptionen wie Sortierung oder Spaltenauswahl anpassen.
+
+## 10. Benutzermenü
+
+Klicken Sie auf Ihr Profilbild in der oberen rechten Ecke, um auf Einstellungen, Abmeldung und Kontooptionen zuzugreifen.
+
+## 11. Rechte Seitenleiste
+
+Zeigt zusätzliche Informationen und Bereiche für Freigaben, Aktivitäten oder Dateidetails.
+
+## 12. Aktionen
+
+Hier finden Sie Aktionen wie Herunterladen, Teilen, Löschen oder Bearbeiten für ausgewählte Dateien.
+
+## 13. Drei-Punkte-Menü
+
+Bietet weitere Optionen für Dateien, Ordner oder Spaces.
+
+## 14. Aktionen-Panel
+
+Zeigt mögliche Aktionen für die ausgewählte Datei, z. B. Umbenennen oder Verschieben.
+
+## 15. Freigabe-Panel
+
+Hier können Sie Dateien und Ordner intern oder extern freigeben und Berechtigungen verwalten.
+
+## 16. Versionen
+
+Zeigt eine Übersicht der Versionen einer ausgewählten Datei oder eines ausgewählten Ordners.
+
+## 17. Aktivitätsleiste
+
+Zeigt eine Übersicht über Änderungen und Aktivitäten innerhalb eines Spaces oder einer Datei.
+
+## 18. Kontextmenü
+
+Ein Rechtsklick auf eine Datei oder einen Ordner öffnet das Kontextmenü mit spezifischen Optionen.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/view-modes.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/view-modes.md
new file mode 100644
index 000000000..fd1d46d50
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/general/view-modes.md
@@ -0,0 +1,31 @@
+---
+sidebar_position: 4
+id: view-modes
+title: Ansichtsmodi
+description: Ansichtsmodi für die Dateiliste in OpenCloud
+draft: false
+---
+
+# Ansichtsmodi der Dateiliste in OpenCloud
+
+In OpenCloud können Sie zwischen verschiedenen Ansichtsmodi für Dateien und Ordner wählen, um die Anzeige nach Ihren Wünschen anzupassen.
+
+## Verfügbare Ansichtsmodi
+
+### Kachelansicht
+
+Dies ist die Standardansicht. Dateien und Ordner werden als Kacheln angezeigt und eignen sich gut für die visuelle Navigation.
+
+<img src={require("./img/view-modes/kachel.png").default} alt="Kachelansicht der Dateiliste" width="1920"/>
+
+### Verdichtete Tabellenansicht
+
+Eine kompaktere Tabellenansicht, in der Informationen dichter zusammengefasst werden, um Platz zu sparen.
+
+<img src={require("./img/view-modes/verdichtet.png").default} alt="Verdichtete Tabellenansicht der Dateiliste" width="1920"/>
+
+### Standard-Tabellenansicht
+
+Die klassische Listenansicht, in der Dateien und Ordner in einer detaillierten Tabelle angezeigt werden.
+
+<img src={require("./img/view-modes/klassisch.png").default} alt="Standard-Tabellenansicht der Dateiliste" width="1920"/>
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/img/common-issues/desktop-excluded.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/img/common-issues/desktop-excluded.png
new file mode 100644
index 000000000..fc0b13394
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/img/common-issues/desktop-excluded.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/index.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/index.md
new file mode 100644
index 000000000..3e28abfdb
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/index.md
@@ -0,0 +1,94 @@
+---
+sidebar_position: 1
+title: Willkommen
+description: Willkommen
+---
+
+<!-- markdownlint-disable MD041 -->
+
+import OcLogoPetrol from '/static/img/oc-logo-petrol.svg';
+import OcLogoLilac from '/static/img/oc-logo-lilac.svg';
+
+<!-- markdownlint-enable MD041 -->
+
+# Willkommen
+
+<OcLogoPetrol width="250" height="55" className="light-mode-image"/>
+<OcLogoLilac width="250" height="55" className="dark-mode-image"/>
+
+## Willkommen zur OpenCloud-Wissensdatenbank
+
+Diese Dokumentation hilft Ihnen beim Einstieg in OpenCloud, beim Verständnis der wichtigsten Funktionen und bei der Suche nach Hilfen für den Alltag, die Administration und die Fehlersuche.
+
+## Was ist OpenCloud?
+
+OpenCloud ist eine File-Sharing- und Kollaborationsplattform der [Heinlein Group](https://www.heinlein.group/). Sie hilft Teams dabei, Dateien geräteübergreifend zu speichern, zu organisieren, zu teilen und gemeinsam zu bearbeiten.
+
+Je nach Arbeitsweise können Sie OpenCloud auf unterschiedliche Weise nutzen:
+
+- Der [Web Client](./general/) bietet direkten Zugriff auf alle OpenCloud-Funktionen im Browser, einschließlich Dateiverwaltung, Kollaborationsfunktionen und Verwaltungsoptionen, soweit Ihre Berechtigungen dies zulassen.
+- Der [Desktop Client](./desktop-client/) synchronisiert Dateien zwischen OpenCloud und Ihrem lokalen Computer für die Offline-Arbeit und automatische Aktualisierungen.
+- Die [iOS App](./ios-app/) bietet bequemen Zugriff auf Dateien und wichtige Aktionen unterwegs.
+- Die [Android App](./android-app/) bietet bequemen Zugriff auf Dateien und wichtige Aktionen unterwegs.
+- Die [Collabora Online-Integration](./collabora) ermöglicht das Bearbeiten von Office-Dokumenten direkt im Browser und die Zusammenarbeit in Echtzeit.
+
+Jeder Client und jede Integration ist für einen bestimmten Anwendungsfall ausgelegt: der Web Client für den umfangreichen Zugriff im Browser, der Desktop Client für die lokale Synchronisierung, die mobilen Apps für den Zugriff unterwegs und Collabora für die Dokumentbearbeitung im Browser.
+
+## Administration und Bereitstellung
+
+Wenn Sie Ihre eigene OpenCloud-Umgebung installieren, einrichten oder verwalten möchten, finden Sie Hilfe in der [Admin-Dokumentation](../admin/) und im Abschnitt [Erste Schritte](../admin/getting-started/).
+
+## Dokumentationsversionen
+
+Diese Dokumentation ist versioniert, damit Sie die Informationen passend zu Ihrer OpenCloud-Version finden.
+
+- **Rolling-Version**  
+  Entspricht dem aktuellen Entwicklungsstand. Änderungen werden fortlaufend eingepflegt, einzelne Funktionen sind möglicherweise noch nicht vollständig dokumentiert.
+
+- **Stable-Release-Versionen**  
+  Dokumentation zu offiziell veröffentlichten Versionen. Diese Versionen werden geprüft und bleiben nach der Veröffentlichung unverändert.
+
+Über das Versionsmenü oben rechts können Sie zwischen der Rolling-Version und bestimmten Release-Versionen wechseln.
+
+## Dokumentation entdecken
+
+### Apps
+
+- [OpenCloud Desktop Client](./desktop-client/)  
+  Hier erfahren Sie, wie Sie den Desktop Client installieren, einrichten und verwenden.
+
+- [OpenCloud iOS App](./ios-app/)  
+  Hier finden Sie Hinweise zur Nutzung von OpenCloud auf iPhone und iPad.
+
+- [OpenCloud Android App](./android-app/)  
+  Hier finden Sie Hinweise zur Nutzung von OpenCloud auf Android-Geräten.
+
+### Web und Bearbeitung
+
+- [Benutzeroberfläche und Navigation](./general/)  
+  Hier lernen Sie den Web Client kennen, passen Kontoeinstellungen an und verändern die Darstellung.
+
+- [Collabora Online](./collabora)  
+  Hier erfahren Sie, wie Sie Dokumente direkt im Browser bearbeiten.
+
+- [Dateien und Ordner verwalten](./files-and-folders/)  
+  Hier finden Sie Hinweise zum Erstellen, Organisieren, Verschieben, Löschen und Wiederherstellen von Dateien und Ordnern.
+
+- [Dateien und Ordner teilen](./sharing/)  
+  Hier erfahren Sie, wie Sie Inhalte intern teilen, öffentliche Links erstellen und File Drop verwenden.
+
+- [Im Team mit Spaces arbeiten](./spaces/)  
+  Hier erfahren Sie, wie Sie Spaces für die Zusammenarbeit in Teams nutzen.
+
+### Administration
+
+- [Rollen](./roles/)  
+  Hier erfahren Sie mehr über Benutzerrollen, Space-Rollen und Freigaberechte in OpenCloud.
+
+- [Administration von OpenCloud](./admin/)  
+  Hier finden Sie Informationen zu Einstellungen, App-Tokens und WebDAV-Zugriff.
+
+### Hilfe
+
+- [Häufige Probleme und Hilfe](./common-issues)  
+  Hier finden Sie Lösungen für häufige Probleme und Antworten auf häufig gestellte Fragen.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/_category_.json b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/_category_.json
new file mode 100644
index 000000000..39441f177
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/_category_.json
@@ -0,0 +1,8 @@
+{
+  "label": "OpenCloud iOS App",
+  "position": 7,
+  "link": {
+    "type": "doc",
+    "id": "ios-app-overview"
+  }
+}
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/files-and-folders/create-rename-move.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/files-and-folders/create-rename-move.md
new file mode 100644
index 000000000..e3830f370
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/files-and-folders/create-rename-move.md
@@ -0,0 +1,119 @@
+---
+sidebar_position: 1
+id: create-rename-move
+title: Erstellen - Umbenennen - Verschieben
+description: Erstellen - Umbenennen - Verschieben
+draft: false
+---
+
+# Erstellen, Umbenennen und Verschieben von Dateien und Ordnern
+
+Mit der OpenCloud iOS-App verwalten Sie Ihre Inhalte ganz einfach. Erstellen Sie neue Ordner und Dateien, benennen Sie Elemente um und verschieben Sie sie an andere Speicherorte – alles direkt von Ihrem iPhone oder iPad aus.
+
+## Erstellen von Dateien und Ordnern
+
+- Tippen Sie oben rechts auf die Schaltfläche "+".
+
+<img src={require("../img/files-and-folders/create-rename-move/create-new.png").default} alt="Neu erstellen" height="400"/>
+
+Wählen Sie aus dem Menü aus, was Sie erstellen möchten:
+
+### Erstellen Sie einen Ordner
+
+– Tippen Sie auf "Ordner erstellen"
+– Geben Sie einen Namen für Ihren Ordner ein
+– Tippen Sie auf "Done"
+
+<img src={require("../img/files-and-folders/create-rename-move/create-folder.png").default} alt="Ordner erstellen" height="400"/>
+
+### Erstellen Sie ein Dokument (erfordert Collabora)
+
+Wenn Collabora Online in Ihrer OpenCloud-Instanz aktiviert ist:
+
+– Tippen Sie auf "Neues Dokument"
+– Wählen Sie den Dokumenttyp (Text, Tabelle, Präsentation)
+– Geben Sie einen Dateinamen ein und bestätigen Sie.
+
+<img src={require("../img/files-and-folders/create-rename-move/choose-file-type.png").default} alt="Wählen Sie den Dateityp" height="400"/>
+
+Das Dokument wird zur Bearbeitung in einer integrierten Webansicht mit Collabora geöffnet.
+
+<img src={require("../img/files-and-folders/create-rename-move/open-collabora.png").default} alt="In Collabora öffnen" height="400"/>
+<img src={require("../img/files-and-folders/create-rename-move/edit-collabora.png").default} alt="In Collabora bearbeiten" height="400"/>
+
+### Machen Sie ein Foto oder Video
+
+- Wählen Sie "Foto oder Video aufnehmen" aus dem Menü
+
+<img src={require("../img/files-and-folders/create-rename-move/select-take-photo.png").default} alt="wählen Sie Foto oder Video aufnehmen aus" height="400"/>
+
+– Die Kamera Ihres Geräts wird geöffnet.
+– Nehmen Sie ein Foto oder Video auf.
+
+<img src={require("../img/files-and-folders/create-rename-move/take-photo.png").default} alt="Machen Sie ein Foto" height="400"/>
+
+- Die Medien werden direkt in Ihrem OpenCloud-Konto gespeichert
+
+<img src={require("../img/files-and-folders/create-rename-move/photo-saved.png").default} alt="Foto gespeichert" height="400"/>
+
+### Dokument scannen
+
+Scannen Sie Papierdokumente mit Ihrem iOS-Gerät:
+
+- Wählen Sie "Dokument scannen"
+- Richten Sie die Kamera auf Ihr Dokument.
+- OpenCloud erkennt die Ränder automatisch und scannt das Dokument.
+
+Sie können dann:
+
+– Den Scan zuschneiden oder drehen
+– Den Farbmodus wechseln (Farbe, Graustufen, Schwarzweiß)
+– Ein Dateiformat wählen (PDF, JPEG, PNG)
+– Als einseitige oder mehrseitige Datei speichern
+
+Das gescannte Dokument wird in Ihrem OpenCloud-Konto gespeichert.
+
+## Dateien oder Ordner umbenennen
+
+So benennen Sie eine Datei oder einen Ordner in der OpenCloud iOS-App um:
+
+- Tippen Sie auf die drei Punkte (⋯) neben dem Element, das Sie umbenennen möchten.
+
+<img src={require("../img/files-and-folders/create-rename-move/three-dots.png").default} alt="Klicken Sie auf das Drei-Punkte-Menü" height="400"/>
+
+- Wählen Sie "Umbenennen" aus dem Menü
+
+<img src={require("../img/files-and-folders/create-rename-move/select-rename.png").default} alt="Wählen Sie umbenennen" height="400"/>
+
+- Geben Sie den neuen Namen für die Datei oder den Ordner ein
+
+<img src={require("../img/files-and-folders/create-rename-move/enter-rename.png").default} alt="Geben Sie den neuen Namen ein" height="400"/>
+
+- Tippen Sie auf "Done", um die Änderungen zu übernehmen
+
+<img src={require("../img/files-and-folders/create-rename-move/tap-done.png").default} alt="Tippen Sie auf fertig" height="400"/>
+<img src={require("../img/files-and-folders/create-rename-move/new-name-applied.png").default} alt="Neuer angewendeter Name" height="400"/>
+
+Der neue Name wird sofort gespeichert.
+
+## Dateien oder Ordner verschieben
+
+So verschieben Sie eine Datei oder einen Ordner in der OpenCloud iOS-App:
+
+- Tippen Sie auf die drei Punkte (⋯) neben der Datei oder dem Ordner, die/den Sie verschieben möchten.
+
+<img src={require("../img/files-and-folders/create-rename-move/three-dots-move.png").default} alt="Wählen Sie das Drei-Punkte-Menü" height="400"/>
+
+- Wählen Sie "Ausschneiden" oder "Kopieren" aus dem Menü
+
+<img src={require("../img/files-and-folders/create-rename-move/select-cut-or-copy.png").default} alt="Wählen Sie Ausschneiden oder Kopieren" height="400"/>
+
+- Navigieren Sie zum Zielordner.
+- Tippen Sie auf die drei Punkte (⋯) im Zielordner und wählen Sie Einfügen.
+
+<img src={require("../img/files-and-folders/create-rename-move/select-paste.png").default} alt="Wählen Sie einfügen" height="400"/>
+<img src={require("../img/files-and-folders/create-rename-move/file-moved.png").default} alt="Datei ist verschoben" height="400"/>
+
+Die Datei oder der Ordner wird jetzt am neuen Speicherort angezeigt.
+
+---
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/files-and-folders/upload-make-available-offline.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/files-and-folders/upload-make-available-offline.md
new file mode 100644
index 000000000..29a930fce
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/files-and-folders/upload-make-available-offline.md
@@ -0,0 +1,59 @@
+---
+sidebar_position: 2
+id: upload-make-available-offline
+title: Hochladen - Offline verfügbar machen
+description: Hochladen - Offline verfügbar machen
+draft: false
+---
+
+# Dateien hochladen
+
+Mit der OpenCloud iOS-App können Sie ganz einfach Dateien hochladen und offline verfügbar machen.
+
+## Gewünschten Ordner öffnen
+
+Navigieren Sie zu dem Ordner, in den Sie eine Datei hochladen möchten.
+
+## Tippen Sie oben rechts auf das "+"-Symbol
+
+<img src={require("../img/files-and-folders/upoload-make-available-offline/upload-plus-button.png").default} alt="Plus Symbol" height="400"/>
+
+## Upload-Option auswählen
+
+Im Menü können Sie Folgendes auswählen:
+
+– "Datei hochladen" – Laden Sie eine Datei aus der Dateien-App Ihres Geräts hoch.
+– "Aus Ihrer Fotobibliothek hochladen" – Laden Sie ein vorhandenes Foto oder Video aus Ihrer Medienbibliothek hoch.
+
+<img src={require("../img/files-and-folders/upoload-make-available-offline/upload-options.png").default} alt="Upload-Optionen" height="400"/>
+
+## Auswahl bestätigen
+
+Wählen Sie die hochzuladende Datei oder das Medium aus. Der Upload startet automatisch.
+
+## Dateien offline verfügbar machen
+
+Sie können Dateien auch offline verfügbar machen, sodass sie auch ohne Internetverbindung zugänglich sind.
+
+- Tippen Sie auf die drei Punkte (⋯) neben der Datei
+
+<img src={require("../img/files-and-folders/upoload-make-available-offline/three-dots.png").default} alt="Offline verfügbar machen" height="400"/>
+
+- Wählen Sie "Offline verfügbar machen" aus
+
+Die Datei wird heruntergeladen und lokal auf Ihrem Gerät gespeichert.
+
+<img src={require("../img/files-and-folders/upoload-make-available-offline/make-available-offline.png").default} alt="Offline verfügbar machen" height="400"/>
+
+- Offlinedateien sind mit einem Wolkensymbol mit Häkchen gekennzeichnet.
+
+<img src={require("../img/files-and-folders/upoload-make-available-offline/marked-offline.png").default} alt="Offline verfügbar machen" height="400"/>
+
+## Offline-Verfügbarkeit entfernen
+
+So geben Sie Speicherplatz frei:
+
+- Tippen Sie erneut auf die drei Punkte (⋯) einer Offline-Datei.
+- Wählen Sie "Offline-Zugriff entfernen".
+
+Mit diesen Funktionen sind Sie immer vorbereitet – auch wenn Sie offline sind!
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/general/installation.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/general/installation.md
new file mode 100644
index 000000000..eaca3ce50
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/general/installation.md
@@ -0,0 +1,35 @@
+---
+sidebar_position: 1
+id: installation
+title: Installieren der iOS App
+description: Installieren der iOS App
+draft: false
+---
+
+# 📱 Installieren der iOS-App
+
+## App Store
+
+Öffnen Sie den App Store auf Ihrem iPhone oder iPad
+
+## OpenCloud
+
+Suchen Sie nach "OpenCloud" oder klicken Sie direkt auf den folgenden Link:
+
+[OpenCloud im App Store](https://apps.apple.com/de/app/opencloud-your-data-anywhere/id6743121005)
+
+<img src={require(".././img/installation/ios-installation.jpg").default} alt="iOS Installation" height="400"/>
+
+## Installieren
+
+Tippen Sie auf "Laden", um die App zu installieren
+
+## App Icon
+
+Nach der Installation finden Sie die OpenCloud App auf Ihrem Home-Bildschirm
+
+<img src={require(".././img/installation/icon-on-screen.png").default} alt="icon" height="400"/>
+
+## Einrichten
+
+Öffnen Sie die App und folgen Sie den Anweisungen zur Einrichtung
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/general/overview/account-fileslist.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/general/overview/account-fileslist.md
new file mode 100644
index 000000000..a30ed2e0b
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/general/overview/account-fileslist.md
@@ -0,0 +1,53 @@
+---
+sidebar_position: 2
+id: account-fileslist
+title: Dateilisten-Menü
+description: Dateilisten-Menü
+draft: false
+---
+
+# Überblick über die Benutzeroberfläche
+
+In diesem Abschnitt werden die zentralen Elemente der Benutzeroberfläche der OpenCloud iOS-App und deren Funktionen erklärt.
+
+<img src={require("../../img/overview/fileslist.png").default} alt="Dateiliste-Übersicht" style={{ width: '400px', marginRight: '60px' }} />
+
+## 1. Konto-Menü
+
+Bietet Zugriff auf die Kontoeinstellungen.
+
+## 2. Navigationsverlauf
+
+Ermöglicht das Zurück- und Vorwärtsnavigieren durch zuvor besuchte Ansichten oder Ordner.
+
+## 3. Suche
+
+Ermöglicht die Suche nach Dateien, Ordnern oder geteilten Inhalten innerhalb der App.
+
+## 4. Hinzufügen-Schaltfläche
+
+Öffnet Optionen zum Hochladen von Dateien, Erstellen von Ordnern oder Hinzufügen neuer Inhalte.
+
+## 5. Drei-Punkte-Menü
+
+Zeigt zusätzliche Aktionen oder Einstellungen zur aktuellen Ansicht oder zum aktuellen Element an.
+
+## 6. Sortierung
+
+Ermöglicht das Sortieren von Dateien nach Name, Datum, Größe oder anderen Kriterien.
+
+## 7. Ansichtsmodus
+
+Ermöglicht das Umschalten zwischen verschiedenen Ansichtsmodi.
+
+## 8. Auswahlmodus
+
+Aktiviert den Mehrfachauswahlmodus, um mehrere Dateien oder Ordner gleichzeitig auszuwählen.
+
+## 9. Dateiliste
+
+Zeigt den Inhalt des aktuellen Ordners als Liste von Dateien und Ordnern an.
+
+## 10. Breadcrumb-Menü
+
+Zeigt den aktuellen Ordnerpfad an und ermöglicht die schnelle Navigation zu übergeordneten Ordnern.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/general/overview/account-overview.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/general/overview/account-overview.md
new file mode 100644
index 000000000..9745f2443
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/general/overview/account-overview.md
@@ -0,0 +1,56 @@
+---
+sidebar_position: 1
+id: account-overview
+title: Account-Menü
+draft: false
+---
+
+# Kontomenü
+
+In der iOS-App bietet das Kontomenü Zugriff auf verschiedene persönliche und freigabebezogene Funktionen.
+
+<img src={require("../../img/overview/account.png").default} alt="Dateiübersicht" style={{ width: '400px', marginRight: '60px' }} />
+
+## 1. Kontomenüeintrag
+
+Öffnet die Hauptoptionen und Einstellungen des Kontos.
+
+## 2. Aktives Konto
+
+Zeigt an, welches Benutzerkonto derzeit aktiv ist.
+
+## 3. Persönlicher Bereich
+
+Bietet Zugriff auf die persönlichen Dateien und Ordner der nutzenden Person.
+
+## 4. Freigaben
+
+Zeigt Dateien und Ordner, die mit anderen geteilt wurden oder empfangen wurden.
+
+## 5. Spaces
+
+Öffnet eine Liste kollaborativer Bereiche oder Teamordner.
+
+## 6. Suche
+
+Ermöglicht die Suche nach Dateien, Ordnern und Inhalten.
+
+## 7. Zuletzt verwendet
+
+Zeigt eine Liste der zuletzt geöffneten oder bearbeiteten Dateien.
+
+## 8. Offline verfügbar
+
+Zeigt Dateien an, die für den Offline-Zugriff markiert wurden.
+
+## 9. Status
+
+Zeigt den aktuellen Synchronisations- oder Verbindungsstatus an.
+
+## 10. Konto hinzufügen
+
+Ermöglicht das Hinzufügen eines neuen Kontos zur App.
+
+## 11. Einstellungen
+
+Öffnet die allgemeinen Einstellungen und Konfigurationsoptionen.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/general/set-up.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/general/set-up.md
new file mode 100644
index 000000000..ed0655a9e
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/general/set-up.md
@@ -0,0 +1,50 @@
+---
+sidebar_position: 2
+id: set-up
+title: Einrichten der OpenCloud iOS App
+description: Einrichten deines OpenCloud Accounts
+draft: false
+---
+
+# 🔐 Einrichten deines OpenCloud Accounts
+
+Nachdem du die App installiert hast, kannst du deinen OpenCloud Account einrichten.
+
+## S tarte die Einrichtung
+
+- Tippe auf „Start setup“, um zu beginnen.
+- Wenn du bereits einen Account eingerichtet hast und einen weiteren hinzufügen möchtest, tippe auf das „+“-Symbol unten links auf dem Bildschirm.
+
+<img src={require(".././img/set-up/start-setup.png").default} alt="Einrichtung starten" height="400"/>
+<img src={require(".././img/set-up/add-additional-account.png").default} alt="Zusätzlichen Account hinzufügen" height="400"/>
+
+## Server-URL eingeben
+
+- Gib die URL deines OpenCloud Servers ein (z. B. `https://cloud.beispiel.de`)
+- Tippe auf „Proceed“, um fortzufahren.
+
+<img src={require(".././img/set-up/enter-server-url.png").default} alt="Server-URL eingeben" height="400"/>
+
+## Login Seite öffnen
+
+- Tippe auf „Open login page“
+- Tippe anschließend auf „Fortfahren“, um die Anmeldeseite im Browser zu starten
+
+<img src={require(".././img/set-up/open-login-page.png").default} alt="Login-Seite öffnen" height="400"/>
+<img src={require(".././img/set-up/continue-sign-in.png").default} alt="Anmeldung fortsetzen" height="400"/>
+
+## Anmelden und Zugriff erlauben
+
+- Melde dich mit deinen OpenCloud Zugangsdaten an
+- Erlaube der App den Zugriff auf deine Benutzerinformationen und die kontinuierliche Anmeldung
+
+<img src={require(".././img/set-up/enter-credentials.png").default} alt="Zugangsdaten eingeben" height="400"/>
+<img src={require(".././img/set-up/grant-access.png").default} alt="Zugriff gewähren" height="400"/>
+
+## Einrichtung abschließen
+
+- Nach erfolgreicher Anmeldung wird dein Account in der App hinzugefügt
+- Optional kannst du deinem Account einen benutzerdefinierten Anzeigenamen geben  
+  (Standardmäßig erscheint er als `BENUTZERNAME@DEINE.DOMAIN`)
+
+<img src={require(".././img/set-up/custom-name.png").default} alt="Benutzerdefinierter Name" height="400"/>
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/general/settings.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/general/settings.md
new file mode 100644
index 000000000..76d9d0465
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/general/settings.md
@@ -0,0 +1,103 @@
+---
+sidebar_position: 4
+id: settings
+title: Einstellungen
+description: Einstellungen der iOS App
+draft: false
+---
+
+# Einstellungen
+
+In den iOS-App Einstellungen können Änderungen vorgenommen werden wie z.B
+
+    - Benutzeroberfläche
+    - Datennutzung
+    - erweiterte Einstellungen
+    - Mediadateien
+    und mehr
+
+<img src={require(".././img/settings/einstellungen.png").default} alt="Einstellungen" width="1920"/>
+
+## Userinterface
+
+### 1. Theme
+
+Hier kann ausgewählt werden, ob man die App im "Light-" oder "Darkmode" betreiben möchte.
+
+### 2. Sucheinstellungen
+
+Hier kann man einstellen, wo die Suchfunktion agieren soll:
+
+- Ordner
+- Baum
+- Space
+- Account
+- Server
+
+### 3. Logging
+
+Hier kann die Loggingfunktion aktiviert und deaktiviert werden, sowie der Speicherort des Logfiles angegeben werden.
+
+## Data Usage
+
+### 4. Mobile Datennutzung
+
+Hier kann eingestellt werden, ob die App mit mobilen Daten genutzt werden kann oder nicht.
+
+### 5. Löschen von nicht verwendeten lokalen Kopien
+
+Hier kann eingestellt werden, wann nicht genutzte lokale Kopien gelöscht werden sollen.
+
+## Advanced Settings
+
+### 6. Anzeigen von versteckten Dateien und Ordnern
+
+Hier kann das Anzeigen von verstecken Dateien und Ordnern aktiviert und deaktiviert werden.
+
+### 7. Zeige Ordner oben
+
+Hier kann man einstellen, ob die Ordner in der Listenansicht vor den Dateien angezeigt werden sollen.
+
+### 8. Gesten deaktivieren
+
+Hier kann die Gestensteuerung deaktiviert werden, um Mehfachauswahl und das Ziehen von Dateien und Ordnern zu verhindern.
+
+### 9. Diagnose aktivieren
+
+Hier kann ausgewählt werden, ob die App im Hintergrund Diagnosen ausführen darf.
+
+## Media Files
+
+### 10. Herunterladen anstelle von streamen
+
+Hier kann eingestellt werden, ob eine Datei direkt heruntergeladen oder gestreamt werden soll.
+
+### 11. Medien hochladen
+
+Hier kann man einstellen, ob z.B. bestimmte Dateien beim hochladen konvertiert werden sollen, wie HEIC zu JPEG.
+
+## More
+
+### 12. Hilfe und Kontakt
+
+Hier findet man Links zu unserer Dokumentaionsseite und Hilfelinks.
+
+### 13. Einem Freund empfehlen
+
+Hier kann man einen Link zum Download der iOS-App weiterleiten.
+
+### 14. Datenschutzrichtlinie
+
+Hier findet man einen vollständigen Eintrag zu unseren Datenschutzrichtlinien.
+
+### 15. Nutzungsbedingungen
+
+Hier findet man einen vollständigen Eintrag zu unseren Nutzungsbedingen.
+
+### 16. Anerkennungen
+
+Teile der App können urheberrechtlich geschütztes Material verwenden, dessen Verwendung hier anerkannt wird.
+
+### 17. App Version
+
+Hier kann ausgelesen werden, welche App Version verwendet wird.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/choose-file-type.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/choose-file-type.png
new file mode 100644
index 000000000..0e014e283
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/choose-file-type.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/create-folder.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/create-folder.png
new file mode 100644
index 000000000..ba69d2a97
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/create-folder.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/create-new.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/create-new.png
new file mode 100644
index 000000000..c925a437a
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/create-new.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/edit-collabora.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/edit-collabora.png
new file mode 100644
index 000000000..79a870c1d
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/edit-collabora.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/enter-rename.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/enter-rename.png
new file mode 100644
index 000000000..6023a359d
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/enter-rename.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/file-moved.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/file-moved.png
new file mode 100644
index 000000000..df5c8fe32
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/file-moved.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/new-name-applied.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/new-name-applied.png
new file mode 100644
index 000000000..3c9a42233
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/new-name-applied.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/open-collabora.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/open-collabora.png
new file mode 100644
index 000000000..890e17a71
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/open-collabora.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/photo-saved.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/photo-saved.png
new file mode 100644
index 000000000..651c303f0
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/photo-saved.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-cut-or-copy.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-cut-or-copy.png
new file mode 100644
index 000000000..36e6376b6
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-cut-or-copy.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-paste.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-paste.png
new file mode 100644
index 000000000..55ea34e2d
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-paste.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-rename.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-rename.png
new file mode 100644
index 000000000..3555bd608
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-rename.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-take-photo.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-take-photo.png
new file mode 100644
index 000000000..776241fc7
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-take-photo.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/take-photo.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/take-photo.png
new file mode 100644
index 000000000..9c82a0645
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/take-photo.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/tap-done.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/tap-done.png
new file mode 100644
index 000000000..cc09b6957
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/tap-done.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/three-dots-move.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/three-dots-move.png
new file mode 100644
index 000000000..5005f980f
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/three-dots-move.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/three-dots.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/three-dots.png
new file mode 100644
index 000000000..f26842895
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/three-dots.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/make-available-offline.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/make-available-offline.png
new file mode 100644
index 000000000..c7f66a588
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/make-available-offline.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/marked-offline.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/marked-offline.png
new file mode 100644
index 000000000..6a414eaae
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/marked-offline.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/three-dots.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/three-dots.png
new file mode 100644
index 000000000..200f2d4f1
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/three-dots.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/upload-options.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/upload-options.png
new file mode 100644
index 000000000..ee3c63a76
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/upload-options.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/upload-plus-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/upload-plus-button.png
new file mode 100644
index 000000000..f2a7ceeff
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/upload-plus-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/installation/icon-on-screen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/installation/icon-on-screen.png
new file mode 100644
index 000000000..a86cb5c3f
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/installation/icon-on-screen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/installation/ios-installation.jpg b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/installation/ios-installation.jpg
new file mode 100644
index 000000000..70eaa1864
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/installation/ios-installation.jpg differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/overview/account.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/overview/account.png
new file mode 100644
index 000000000..ffd976234
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/overview/account.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/overview/fileslist.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/overview/fileslist.png
new file mode 100644
index 000000000..cf8773d83
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/overview/fileslist.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/date.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/date.png
new file mode 100644
index 000000000..c4a31e2bc
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/date.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/save-search.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/save-search.png
new file mode 100644
index 000000000..63f439b26
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/save-search.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/search-location.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/search-location.png
new file mode 100644
index 000000000..b2084313e
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/search-location.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/search-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/search-menue.png
new file mode 100644
index 000000000..ec300254b
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/search-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/search-result.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/search-result.png
new file mode 100644
index 000000000..551f4f7b2
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/search-result.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/search-symbol.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/search-symbol.png
new file mode 100644
index 000000000..3ecbd4991
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/search-symbol.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/searchbar.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/searchbar.png
new file mode 100644
index 000000000..755fa9050
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/searchbar.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/size.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/size.png
new file mode 100644
index 000000000..708f96903
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/size.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/type.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/type.png
new file mode 100644
index 000000000..72d249a63
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/search/type.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/add-additional-account.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/add-additional-account.png
new file mode 100644
index 000000000..e3ecc6c06
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/add-additional-account.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/continue-sign-in.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/continue-sign-in.png
new file mode 100644
index 000000000..ebe6f25a4
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/continue-sign-in.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/custom-name.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/custom-name.png
new file mode 100644
index 000000000..056a6225f
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/custom-name.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/enter-credentials.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/enter-credentials.png
new file mode 100644
index 000000000..bb31e743b
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/enter-credentials.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/enter-server-url.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/enter-server-url.png
new file mode 100644
index 000000000..90af12a67
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/enter-server-url.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/grant-access.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/grant-access.png
new file mode 100644
index 000000000..1f36079e8
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/grant-access.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/open-login-page.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/open-login-page.png
new file mode 100644
index 000000000..195e33502
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/open-login-page.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/start-setup.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/start-setup.png
new file mode 100644
index 000000000..69ab090f6
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/set-up/start-setup.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/settings/einstellungen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/settings/einstellungen.png
new file mode 100644
index 000000000..93fc10aba
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/settings/einstellungen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/choose-invites.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/choose-invites.png
new file mode 100644
index 000000000..0a632fc7d
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/choose-invites.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/invite-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/invite-button.png
new file mode 100644
index 000000000..a4ae9d18f
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/invite-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/invite-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/invite-menue.png
new file mode 100644
index 000000000..13c5854a7
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/invite-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/invite-option.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/invite-option.png
new file mode 100644
index 000000000..d5f398baf
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/invite-option.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/permissions.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/permissions.png
new file mode 100644
index 000000000..3848f49ae
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/permissions.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/searchbar.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/searchbar.png
new file mode 100644
index 000000000..f7aa1ecf0
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/searchbar.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/shared-with.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/shared-with.png
new file mode 100644
index 000000000..80566d860
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/shared-with.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/sharing-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/sharing-button.png
new file mode 100644
index 000000000..cb96657d0
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/sharing-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/three-dot-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/three-dot-menue.png
new file mode 100644
index 000000000..fb1ec63ec
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/invite/three-dot-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/create-link-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/create-link-button.png
new file mode 100644
index 000000000..9b38d54ae
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/create-link-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/create-link-options.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/create-link-options.png
new file mode 100644
index 000000000..e126b5de6
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/create-link-options.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/created-link.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/created-link.png
new file mode 100644
index 000000000..233aa0124
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/created-link.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/expiration-date.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/expiration-date.png
new file mode 100644
index 000000000..33eda696c
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/expiration-date.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/link-name.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/link-name.png
new file mode 100644
index 000000000..3f70f6c0b
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/link-name.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/password.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/password.png
new file mode 100644
index 000000000..b6814c107
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/password.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/share-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/share-button.png
new file mode 100644
index 000000000..ac909edf7
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/share-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/sharing-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/sharing-button.png
new file mode 100644
index 000000000..cb96657d0
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/sharing-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/sharing-options.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/sharing-options.png
new file mode 100644
index 000000000..05f86cd45
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/sharing-options.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/three-dot-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/three-dot-menue.png
new file mode 100644
index 000000000..fb1ec63ec
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shares/links/three-dot-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/choose-file-or-folder.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/choose-file-or-folder.png
new file mode 100644
index 000000000..ff7c3266a
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/choose-file-or-folder.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/create-shortcut-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/create-shortcut-button.png
new file mode 100644
index 000000000..de479b955
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/create-shortcut-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/create-shortcut.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/create-shortcut.png
new file mode 100644
index 000000000..a55ff6ed3
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/create-shortcut.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/created-shortcut.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/created-shortcut.png
new file mode 100644
index 000000000..ccf7a2b88
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/created-shortcut.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/pick-file-or-folder.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/pick-file-or-folder.png
new file mode 100644
index 000000000..3f2a0899f
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/pick-file-or-folder.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/plus-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/plus-button.png
new file mode 100644
index 000000000..d66a0b336
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/plus-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/plus-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/plus-menue.png
new file mode 100644
index 000000000..9247ed80c
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/plus-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/select-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/select-button.png
new file mode 100644
index 000000000..18ab749bf
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/select-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/shortcut-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/shortcut-menue.png
new file mode 100644
index 000000000..f65abb1d0
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/shortcut-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/shortcut-name.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/shortcut-name.png
new file mode 100644
index 000000000..7673f7fa5
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/shortcut-name.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/url.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/url.png
new file mode 100644
index 000000000..2e455795e
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/shortcuts/url.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/spaces/plus-symbol.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/spaces/plus-symbol.png
new file mode 100644
index 000000000..a8bb6ed5f
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/spaces/plus-symbol.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/spaces/search-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/spaces/search-button.png
new file mode 100644
index 000000000..5893e8bae
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/spaces/search-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/spaces/search-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/spaces/search-menue.png
new file mode 100644
index 000000000..3aff88663
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/spaces/search-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/spaces/spaces-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/spaces/spaces-button.png
new file mode 100644
index 000000000..8f44b7e19
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/spaces/spaces-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/spaces/spaces-functions.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/spaces/spaces-functions.png
new file mode 100644
index 000000000..60db08662
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/spaces/spaces-functions.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/spaces/spaces-overview.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/spaces/spaces-overview.png
new file mode 100644
index 000000000..0973862ff
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/spaces/spaces-overview.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/spaces/three-point-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/spaces/three-point-menue.png
new file mode 100644
index 000000000..e6e214bdc
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/img/spaces/three-point-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/index.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/index.md
new file mode 100644
index 000000000..35d331407
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/index.md
@@ -0,0 +1,31 @@
+---
+sidebar_position: 0
+id: ios-app-overview
+title: OpenCloud iOS App
+---
+
+# OpenCloud iOS App
+
+Die OpenCloud iOS App bietet mobilen Zugriff auf Ihre Dateien, Spaces und Freigaben auf iPhone und iPad. Sie ist für
+alltägliche Aufgaben wie Einrichtung, Suche, Teilen und das Offline-Verfügbar-Machen von Dateien ausgelegt.
+
+## In diesem Abschnitt
+
+- [Allgemeines](./general/)  
+  Installieren Sie die App, führen Sie die Ersteinrichtung durch und lernen Sie die wichtigsten Bereiche und
+  Einstellungen kennen.
+
+- [Dateien und Ordner](./files-and-folders/)  
+  Erstellen und bearbeiten Sie Inhalte, laden Sie Dateien hoch und machen Sie Elemente offline verfügbar.
+
+- [Spaces](./spaces.md)  
+  Arbeiten Sie mit Spaces und den verfügbaren Aktionen in der iOS App.
+
+- [Suche](./search.md)  
+  Finden Sie Dateien und Ordner direkt in der iOS App.
+
+- [Verknüpfungen](./shortcuts.md)  
+  Erstellen Sie Verknüpfungen zu Dateien oder Weblinks.
+
+- [Freigaben](./shares/)  
+  Laden Sie Personen ein und erstellen Sie Freigabelinks direkt in der iOS App.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/search.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/search.md
new file mode 100644
index 000000000..ec6a6f201
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/search.md
@@ -0,0 +1,72 @@
+---
+sidebar_position: 4
+id: search
+title: Suche
+description: Suche
+draft: false
+---
+
+# Suchfunktion
+
+Hier erklären wir, wie du die Suchfunktion in der OpenCloud iOS-App verwendest.
+
+## Suchsymbol
+
+- Klicke auf das Suchsymbol, um die Suchfunktion zu öffnen
+
+  <img src={require("./img/search/search-symbol.png").default} alt="Magnifying glass icon" height="400"/>
+
+## Suchfunktion
+
+- Die Suchfunktion bietet verschiedene Optionen, mit denen du deine Suche eingrenzen kannst
+
+## Suchleiste
+
+- In der Suchleiste kannst du nach Datei- oder Ordnernamen suchen.
+
+  <img src={require("./img/search/searchbar.png").default} alt="Search bar" height="400"/>
+
+## Suchort
+
+Durch Klicken auf die Option links neben der Suchleiste kannst du festlegen, wo gesucht werden soll.
+
+- Ordner:  
+  Sucht nur im aktuellen Ordner.
+- Baum:  
+  Sucht im aktuellen Ordner und allen darin enthaltenen Unterordnern.
+- Space:  
+  Sucht im aktuellen Space, einschließlich aller darin enthaltenen Ordner und Unterordner.
+- Konto:  
+  Sucht im gesamten angemeldeten Konto, einschließlich aller Spaces, Ordner und Unterordner.
+- Server:  
+  Sucht auf dem gesamten Server.
+
+  <img src={require("./img/search/search-location.png").default} alt="Search location" height="400"/>
+
+## Typ
+
+- Durch Klicken auf die Option „Typ“ kannst du festlegen, nach welchem Dateityp gesucht werden soll
+
+  <img src={require("./img/search/type.png").default} alt="File type" height="400"/>
+
+## Datum
+
+- Durch Klicken auf die Option „Datum“ kannst du den Zeitraum festlegen, in dem gesucht werden soll
+
+  <img src={require("./img/search/date.png").default} alt="Date" height="400"/>
+
+## Größe
+
+- Durch Klicken auf die Option „Größe“ kannst du die gesuchte Dateigröße eingrenzen
+
+## Suche speichern
+
+- Durch Klicken auf das „Kreissymbol“ mit den drei Punkten kannst du die aktuelle Suche speichern
+
+  <img src={require("./img/search/save-search.png").default} alt="Save search" height="400"/>
+
+## Suchergebnis
+
+- In diesem Bereich werden die Suchergebnisse angezeigt
+
+  <img src={require("./img/search/search-result.png").default} alt="Search results" height="400"/>
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/shares/invite.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/shares/invite.md
new file mode 100644
index 000000000..14cf488c3
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/shares/invite.md
@@ -0,0 +1,62 @@
+---
+sidebar_position: 1
+id: invite
+title: Einladen zum Teilen
+description: Einladen zum Teilen
+draft: false
+---
+
+# Dateien und Ordner mit Personen und Gruppen per Einladung teilen
+
+Hier erklären wir, wie man in der OpenCloud iOS-App, Dateien und Ordner per Einladung mit anderen Personen und Gruppen innerhalb der eigenen OpenCloud teilt
+
+## Drei-Punkte-Menü
+
+- Klicken Sie auf das "Drei-Punkte-Menü" neben der Datei oder Ordner
+
+<img src={require("../img/shares/invite/three-dot-menue.png").default} alt="Drei-Punkte-Menü" height="400"/>
+
+## Teilen
+
+- Wählen Sie nun den Menüpunkt "Sharing" aus
+
+<img src={require("../img/shares/invite/sharing-button.png").default} alt="Teilen" height="400"/>
+
+## Teilen mit
+
+- In der folgenden Auswahl klicken Sie auf "invite"
+
+<img src={require("../img/shares/invite/invite-option.png").default} alt="Teilen mit" height="400"/>
+
+## Teilen Menü
+
+- Es öffnet sich das Teilen Menü, in dem Sie über die Suchleiste nach Personen oder Gruppen suchen können, die Sie einladen möchten
+
+<img src={require("../img/shares/invite/invite-menue.png").default} alt="Teilen mit Menü" height="400"/>
+<img src={require("../img/shares/invite/searchbar.png").default} alt="Suchleiste" height="400"/>
+<img src={require("../img/shares/invite/choose-invites.png").default} alt="Auswahl Personen und/oder Gruppen" height="400"/>
+
+## Berechtigungen
+
+- Hier können Sie auswählen welche Berechtiigungen Personen und Gruppen haben sollen:
+
+<img src={require("../img/shares/invite/permissions.png").default} alt="Berechtigungen" height="400"/>
+
+    - Viever:
+    Personen können die Inhalte nur anzeigen und herunterladen, jedoch nicht bearbeiten, erstellen oder hochladen.
+    - Editor:
+    Personen können die Inhalte anzeigen, herunterladen, Dateien hochladen, bearbeiten und erstellen.
+    - Custom:
+    Hier können die Berechtigungen individuell gewählt werden.
+
+## Einladen
+
+- Um den Link nun zu erstellen müssen Sie auf "Invite" klicken
+
+<img src={require("../img/shares/invite/invite-button.png").default} alt="Einladen" height="400"/>
+
+## Link erstellt
+
+- Wenn die Einladung erstellt ist, sehen Sie diese in der Datei- oder Ordnerübersicht
+
+<img src={require("../img/shares/invite/shared-with.png").default} alt="geteilt mit" height="400"/>
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/shares/links.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/shares/links.md
new file mode 100644
index 000000000..8b90ab8bf
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/shares/links.md
@@ -0,0 +1,81 @@
+---
+sidebar_position: 2
+id: links
+title: Per Link teilen
+description: Per Link teilen
+draft: false
+---
+
+# Dateien und Ordner per Link teilen
+
+Hier erklären wir, wie man in der OpenCloud iOS-App Dateien und Ordner per Link mit anderen teilen kann.
+
+## Drei-Punkte-Menü
+
+- Tippe auf das Drei-Punkte-Menü neben der Datei oder dem Ordner
+
+  <img src={require("../img/shares/links/three-dot-menue.png").default} alt="Drei-Punkte-Menü" height="400"/>
+
+## Teilen
+
+- Wähle nun den Menüpunkt „Share“ aus
+
+  <img src={require("../img/shares/links/sharing-button.png").default} alt="Teilen" height="400"/>
+
+## Link erstellen
+
+- Klicke in der folgenden Auswahl auf „Create Link“
+
+  <img src={require("../img/shares/links/create-link-button.png").default} alt="Link erstellen" height="400"/>
+
+## Optionen
+
+- Hier kannst du mehrere Optionen für den zu erstellenden Link auswählen und festlegen
+
+  <img src={require("../img/shares/links/create-link-options.png").default} alt="Übersicht Link-Menü" height="400"/>
+
+## Linkname
+
+- Gib hier einen Namen für deinen Link ein
+
+  <img src={require("../img/shares/links/link-name.png").default} alt="Linkname" height="400"/>
+
+## Linkfunktionen
+
+- Hier kannst du auswählen, welche Funktion dein Link haben soll:
+
+  <img src={require("../img/shares/links/sharing-options.png").default} alt="Freigabeoptionen" height="400"/>
+  - Personen einladen:  
+    Nur eingeladene Personen haben Zugriff auf den Link und dessen Inhalt.
+  - Kann anzeigen:  
+    Personen können den Inhalt des Links nur ansehen und herunterladen, aber nicht bearbeiten, erstellen oder hochladen.
+  - Kann hochladen:  
+    Personen können den Inhalt des Links ansehen und Dateien hochladen, aber nicht bearbeiten oder erstellen.
+  - Kann verwalten:  
+    Personen können Dateien ansehen, herunterladen und hochladen, aber nicht bearbeiten oder erstellen.
+  - Kann bearbeiten:  
+    Personen können den Inhalt des Links ansehen, herunterladen, hochladen, bearbeiten und erstellen.
+
+## Passwort
+
+- Hier musst du ein Passwort eingeben. Du kannst eines selbst wählen oder automatisch generieren lassen
+
+  <img src={require("../img/shares/links/password.png").default} alt="Passwort" height="400"/>
+
+## Verfügbarkeitszeitraum
+
+- Hier kannst du einen Zeitraum festlegen, für den der Link verfügbar sein soll
+
+  <img src={require("../img/shares/links/expiration-date.png").default} alt="Ablaufdatum des Links" height="400"/>
+
+## Erstellen
+
+- Um den Link zu erstellen, musst du nun auf „Share“ klicken
+
+  <img src={require("../img/shares/links/share-button.png").default} alt="Teilen" height="400"/>
+
+## Erstellt Link
+
+- Sobald der Link erstellt wurde, wird er mit dem vergebenen Namen in der Datei- oder Ordnerübersicht angezeigt
+
+  <img src={require("../img/shares/links/created-link.png").default} alt="Erstellter Link" height="400"/>
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/shortcuts.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/shortcuts.md
new file mode 100644
index 000000000..410a17b53
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/shortcuts.md
@@ -0,0 +1,67 @@
+---
+sidebar_position: 5
+id: shortcuts
+title: Verlinkungen in der OpenCloud iOS App
+description: Verlinkungen in der OpenCloud iOS App
+draft: false
+---
+
+# Shortcut in der OpenCloud iOS-App
+
+Hier zeigen wir dir, wie du Shortcuts in der iOS-App erstellst.
+
+## „+“-Symbol
+
+- Tippe auf das „+“-Symbol
+
+  <img src={require("./img/shortcuts/plus-button.png").default} alt="Plus symbol" height="400"/>
+
+## Drop-down-Menü
+
+- Es öffnet sich ein Drop-down-Menü
+
+  <img src={require("./img/shortcuts/plus-menue.png").default} alt="Drop-down menu" height="400"/>
+
+## Shortcut erstellen
+
+- Wähle „Shortcut erstellen“ aus
+
+  <img src={require("./img/shortcuts/create-shortcut.png").default} alt="Select create shortcut" height="400"/>
+
+## Shortcut-Optionen
+
+- Es öffnet sich ein Menü mit Optionen für Shortcuts
+
+  <img src={require("./img/shortcuts/shortcut-menue.png").default} alt="Shortcut menu" height="400"/>
+
+## URL
+
+- Um einen Shortcut zu einer Website zu erstellen, gib unter „URL“ die Adresse der Website ein
+
+  <img src={require("./img/shortcuts/url.png").default} alt="URL" height="400"/>
+
+## Dateien und Ordner auswählen
+
+- Um einen Shortcut zu einer Datei oder einem Ordner in OpenCloud zu erstellen, tippe auf die Option „Datei oder Ordner auswählen“
+
+  <img src={require("./img/shortcuts/pick-file-or-folder.png").default} alt="Select file or folder option" height="400"/>
+  <img src={require("./img/shortcuts/choose-file-or-folder.png").default} alt="Select file or folder" height="400"/>
+  <img src={require("./img/shortcuts/select-button.png").default} alt="Select" height="400"/>
+
+## Shortcut-Name
+
+- Gib hier einen Namen für den Shortcut ein, unter dem er angezeigt werden soll
+
+  <img src={require("./img/shortcuts/shortcut-name.png").default} alt="Name of the shortcut" height="400"/>
+
+## Erstellen-Button
+
+- Tippe auf „Shortcut erstellen“, um den Shortcut zu erstellen
+
+  <img src={require("./img/shortcuts/create-shortcut-button.png").default} alt="Create shortcut" height="400"/>
+
+## Erstellter Shortcut
+
+- Dein erstellter Shortcut wird nun angezeigt und kann verwendet werden
+
+  <img src={require("./img/shortcuts/created-shortcut.png").default} alt="Shortcut" height="400"/>
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/spaces.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/spaces.md
new file mode 100644
index 000000000..ca5aa5960
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/ios-app/spaces.md
@@ -0,0 +1,75 @@
+---
+sidebar_position: 6
+id: spaces
+title: Spaces
+description: Spaces in OpenCloud iOS app
+draft: false
+---
+
+# Der Bereich „Spaces“ in der OpenCloud iOS-App
+
+Der Bereich „Spaces“ bietet einen zentralen Ort für die Zusammenarbeit in Gruppen oder Teams. In einem Space können mehrere Personen gemeinsam auf Dateien und Ordner zugreifen, Inhalte organisieren und Änderungen nachverfolgen.
+
+## Spaces-Übersicht
+
+Um die Spaces-Übersicht zu öffnen, tippe im Kontomenü auf die Schaltfläche „Spaces“.
+
+<img src={require("./img/spaces/spaces-button.png").default} alt="Spaces Button" style={{ width: '300px', marginRight: '60px' }} />
+
+Anschließend erscheint die Spaces-Übersicht, in der alle Spaces aufgelistet sind, in denen du Mitglied bist oder die du selbst erstellt hast.
+
+<img src={require("./img/spaces/spaces-overview.png").default} alt="Spaces Overview" style={{ width: '300px', marginRight: '60px' }} />
+
+## Suchfunktion
+
+Durch Tippen auf das Suchsymbol öffnet sich das Suchmenü für Spaces.
+
+<img src={require("./img/spaces/search-button.png").default} alt="Search Function" style={{ width: '300px', marginRight: '60px' }} />
+
+<img src={require("./img/spaces/search-menue.png").default} alt="Search Menu" style={{ width: '300px', marginRight: '60px' }} />
+
+## Funktionen innerhalb eines Spaces
+
+Durch Tippen auf das Plus-Symbol erscheinen die verfügbaren Funktionen innerhalb eines Spaces.
+
+<img src={require("./img/spaces/plus-symbol.png").default} alt="Plus Icon" style={{ width: '300px', marginRight: '60px' }} />
+
+<img src={require("./img/spaces/spaces-functions.png").default} alt="Functions in Spaces" style={{ width: '400px', marginRight: '60px' }} />
+
+## Hinzufügen-Menü
+
+Das Hinzufügen-Menü in der iOS-App ermöglicht es Nutzer\*innen, Inhalte direkt in einem Space zu erstellen oder hochzuladen.
+
+### 1. Ordner erstellen
+
+Neue Ordner erstellen, um Inhalte übersichtlich zu strukturieren.
+
+### 2. Neues Dokument
+
+Ein neues Dokument direkt im Space erstellen, ohne eine separate App zu nutzen.
+
+### 3. Dateien hochladen
+
+Dateien vom eigenen Gerät auswählen und in den Space hochladen.
+
+### 4. Aus Mediathek hochladen
+
+Auf die iOS-Fotomediathek zugreifen und Bilder oder Videos direkt in den Space laden.
+
+### 5. Foto oder Video aufnehmen
+
+Die iOS-Kamera nutzen, um Fotos oder Videos aufzunehmen und direkt in den Space hochzuladen.
+
+### 6. Shortcut erstellen
+
+Einen Shortcut zu einer Datei oder einem Ordner im Space erstellen, um schneller darauf zugreifen zu können.
+
+### 7. Dokument scannen
+
+Die Gerätekamera verwenden, um physische Dokumente zu scannen und sie direkt als PDF im Space zu speichern.
+
+## Drei-Punkte-Menü
+
+Durch Tippen auf das Drei-Punkte-Menü öffnet sich ein Pop-up-Menü, in dem du den Space offline verfügbar machen kannst.
+
+<img src={require("./img/spaces/three-point-menue.png").default} alt="Three-Dot Menu" style={{ width: '300px', marginRight: '60px' }} />
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/roles/_category_.json b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/roles/_category_.json
new file mode 100644
index 000000000..6f27be626
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/roles/_category_.json
@@ -0,0 +1,8 @@
+{
+  "label": "Rollen",
+  "position": 9,
+  "link": {
+    "type": "doc",
+    "id": "roles-overview"
+  }
+}
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/roles/index.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/roles/index.md
new file mode 100644
index 000000000..e735f65fd
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/roles/index.md
@@ -0,0 +1,21 @@
+---
+sidebar_position: 0
+id: roles-overview
+title: Rollen
+---
+
+# Rollen
+
+Dieser Abschnitt erklärt die Rollenmodelle in OpenCloud. Er behandelt allgemeine Benutzerrollen, die Berechtigungen
+innerhalb von Spaces und die Zugriffsebenen, die beim Teilen von Dateien und Ordnern vergeben werden können.
+
+## In diesem Abschnitt
+
+- [Benutzerrollen](./user-roles.md)  
+  Erfahren Sie mehr über die verfügbaren Benutzerrollen in OpenCloud, darunter Admin, Space Admin, User und User Light.
+
+- [Space-Rollen](./space-roles.md)  
+  Verstehen Sie die Berechtigungen innerhalb eines Space, darunter Kann ansehen, Kann bearbeiten und Kann verwalten.
+
+- [Freigaberollen](./share-roles.md)  
+  Prüfen Sie die Zugriffsebenen, die beim Teilen von Dateien und Ordnern verfügbar sind.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/roles/share-roles.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/roles/share-roles.md
new file mode 100644
index 000000000..3307c6f6b
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/roles/share-roles.md
@@ -0,0 +1,42 @@
+---
+sidebar_position: 3
+id: share-roles
+title: Rollen beim Teilen
+description: Rollen beim Teilen in OpenCloud
+draft: false
+---
+
+# Rollen beim teilen in OpenCloud
+
+| Rolle                  | anzeigen | herunterladen | hochladen | bearbeiten | erstellen | löschen | nur doc, img, pdf mit Wasserzeichen anzeigen |
+| :--------------------- | :------: | :-----------: | :-------: | :--------: | :-------: | :-----: | :------------------------------------------: |
+| kann anzeigen (geheim) |    -     |       -       |     -     |     -      |     -     |    -    |                      x                       |
+| kann anzeigen          |    x     |       x       |     -     |     -      |     -     |    -    |                      -                       |
+| kann hochladen         |    x     |       x       |     x     |     -      |     -     |    -    |                      -                       |
+| kann bearbeiten        |    x     |       x       |     x     |     x      |     x     |    x    |                      -                       |
+
+## Space-Mitglieder-Rollen und -Rechte
+
+In einem Space können Mitglieder verschiedene Rollen haben, die bestimmen, was sie mit gemeinsamen Dateien und Ordnern tun können.
+
+### Kann ansehen (sicher)
+
+- Sie können nur Dokumente, Bilder und PDFs anzeigen.
+- Die Dateien werden mit einem Wasserzeichen versehen.
+- Das Herunterladen ist nicht erlaubt.
+
+### Kann anzeigen
+
+- Sie können Dateien und Ordner anzeigen und herunterladen.
+- Keine Einschränkungen beim Herunterladen.
+
+### Kann hochladen
+
+- Sie können Dateien und Ordner anzeigen, herunterladen und hochladen.
+
+### Kann bearbeiten
+
+- Sie können Dateien und Ordner bearbeiten, hinzufügen und löschen.
+- Voller Zugriff auf die Änderung gemeinsamer Inhalte.
+
+Jede Rolle gibt eine andere Zugriffsstufe, so dass jeder Benutzer die richtigen Berechtigungen erhält!
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/roles/space-roles.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/roles/space-roles.md
new file mode 100644
index 000000000..443e494d3
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/roles/space-roles.md
@@ -0,0 +1,42 @@
+---
+sidebar_position: 2
+id: space-roles
+title: Rollen für Spaces
+---
+
+# Rollen für Spaces in OpenCloud
+
+| Role            | anzeigen | herunterladen | hochladen | bearbeiten | erstellen | löschen | Mitglieder verwalten | deaktivieren / aktivieren Space | Quota bearbeiten | Space löschen |
+| :-------------- | :------: | :-----------: | :-------: | :--------: | :-------: | :-----: | :------------------: | :-----------------------------: | :--------------: | :-----------: |
+| Kann anzeigen   |    x     |       x       |     -     |     -      |     -     |    -    |          -           |                -                |        -         |       -       |
+| Kann bearbeiten |    x     |       x       |     x     |     x      |     x     |    x    |          -           |                -                |        -         |       -       |
+| Kann verwalten  |    x     |       x       |     x     |     x      |     x     |    x    |          x           |                x                |        x         |       x       |
+
+## Space Rollen und Berechtigungen
+
+In einem Space können Mitglieder verschiedene Rollen haben, die ihnen unterschiedliche Zugriffsebenen geben.
+
+### Kann anzeigen
+
+Mit dieser Rolle kann das Mitglied Dateien im Space ansehen und herunterladen, aber keine Änderungen vornehmen, keine Dateien und Ordner hochladen oder neue erstellen.
+
+### Kann bearbeiten
+
+Mit dieser Rolle kann das Mitglied alles tun, was ein „Can View“-Mitglied tun kann, plus:
+
+- Dateien in den Space hochladen
+- Hinzufügen von neuen Dateien und Ordnern
+- Löschen von Dateien und Ordnern, einschließlich ihrer Historie
+- Gelöschte Dateien wiederherstellen
+
+### Kann verwalten
+
+Diese Rolle verleiht dem Mitglied alle Fähigkeiten von „Kann bearbeiten“, plus:
+
+- Hinzufügen oder Entfernen von Mitgliedern aus dem Space
+- Ändern der Rollen anderer Mitglieder im Space
+- Aktivieren und Deaktivieren des Spaces
+- Bearbeiten der Quote des Spaces
+- Löschen des Spaces
+
+Jede Rolle bestimmt, was ein Mitglied innerhalb des Spaces tun kann!
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/roles/user-roles.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/roles/user-roles.md
new file mode 100644
index 000000000..11289190b
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/roles/user-roles.md
@@ -0,0 +1,73 @@
+---
+sidebar_position: 1
+id: user-roles
+title: Rollen für Nutzer
+---
+
+# Nutzerrollen in OpenCloud
+
+| Rolle             | Persönlicher Space | Spaces erstellen | Spaces verwalten | Nutzer und Gruppen verwalten |
+| :---------------- | :----------------: | :--------------: | :--------------: | :--------------------------: |
+| Administrator     |         x          |        x         |        x         |              x               |
+| Space Manager/-in |         x          |        x         |        x         |              -               |
+| Person            |         x          |        -         |        x         |              -               |
+| User Light        |         -          |        -         |        x         |              -               |
+
+## Administrator
+
+Die Administrator-Rolle in OpenCloud hat die gleichen Fähigkeiten wie ein Space-Administrator, verfügt aber zusätzlich über spezielle Berechtigungen zur Verwaltung von Benutzern, Gruppen und Systemeinstellungen.
+Allerdings haben Administratoren keinen direkten Zugriff auf Space-Daten oder die Möglichkeit, Benutzer zu Spaces hinzuzufügen, für die sie nicht die Rolle „kann verwalten“ haben. Nachfolgend sind die wichtigsten Aktionen aufgeführt, die ein Administrator durchführen kann:
+
+- Lokale Benutzer und Gruppen erstellen und löschen
+
+  Administratoren können neue lokale Benutzer hinzufügen und bestehende lokale Benutzer aus dem System entfernen.
+  Sie können auch lokale Gruppen erstellen und löschen, um Benutzer effizient zu organisieren.
+
+- Benutzer und Gruppen bearbeiten
+
+  Benutzerdetails wie Namen, E-Mail-Adressen und Rollen können geändert werden.
+  Gruppen können durch Hinzufügen oder Entfernen von Mitgliedern nach Bedarf aktualisiert werden.
+
+- Anmeldung verhindern
+
+  Falls erforderlich, können Administratoren Benutzerkonten deaktivieren und so verhindern, dass sie sich anmelden können.
+  Dies ist nützlich aus Sicherheitsgründen oder wenn ein Konto nicht mehr benötigt wird.
+
+- Spaces verwalten (ohne Zugriff auf Space-Daten)
+
+  Administratoren können Spaces verwalten, z. B. aktivieren, deaktivieren oder löschen, umbenennen oder die Quote anpassen, auch wenn sie nicht die Rolle „kann verwalten“ haben.
+  Sie können jedoch nicht auf die Dateien innerhalb eines Spaces zugreifen oder ihm Mitglieder hinzufügen.
+
+- Das Logo ändern
+
+  Das Systemlogo kann aktualisiert werden, um das Firmenbranding widerzuspiegeln.
+  Dies kann in den Admin-Einstellungen unter dem Abschnitt „Allgemein“ vorgenommen werden.
+
+## Space Manager/-in
+
+Ein Space-Administrator hat die höchste Ebene der Kontrolle über Spaces. Er kann:
+
+- Spaces erstellen und verwalten
+- in Spaces, die er nicht erstellt hat, die Rolle „Kann bearbeiten“ zugewiesen bekommen
+- Einen persönlichen Space haben, in dem er Dateien und Ordner erstellen und Daten hochladen kann
+
+## Person
+
+Ein normaler Benutzer hat Zugang zu seinem eigenen Space und kann Teil anderer Spaces sein. Er kann:
+
+- Dateien und Ordner in seinem persönlichen Space erstellen
+- Eigene Daten hochladen und verwalten
+- Als Mitglied zu einem Space hinzugefügt werden
+- Kann die Rolle „Kann bearbeiten“ in einem Space haben
+
+## User Light
+
+Ein User Light hat einen eingeschränkten Zugang und verfügt nicht über einen eigenen Space. Er kann:
+
+- Als Mitglied zu einem Space hinzugefügt werden
+- Kann die Rolle „Kann bearbeiten“ in einem Space haben
+- Er kann keine Dateien und Ordner erstellen oder Daten in einen persönlichen Space hochladen.
+
+:::note
+Wenn ein Nutzer zuvor die Rolle Person oder höher hatte und später wieder auf User Light gesetzt wird, behält er seinen persönlichen Space.
+:::
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/_category_.json b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/_category_.json
new file mode 100644
index 000000000..1773e73a2
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/_category_.json
@@ -0,0 +1,8 @@
+{
+  "label": "Dateien und Ordner teilen",
+  "position": 4,
+  "link": {
+    "type": "doc",
+    "id": "sharing-overview"
+  }
+}
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/external.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/external.md
new file mode 100644
index 000000000..3c7d4e365
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/external.md
@@ -0,0 +1,51 @@
+---
+sidebar_position: 2
+id: external
+title: Extern
+description: Externes Teilen von Dateien und Ordnern in OpenCloud
+draft: false
+---
+
+# Öffentliche Links - Externes Teilen von Dateien und Ordnern in OpenCloud
+
+Öffentliche Links ermöglichen es Ihnen, Dateien und Ordner mit Personen außerhalb Ihrer Organisation zu teilen.
+
+## Schritte zum Erstellen eines öffentlichen Links
+
+- Klicken Sie mit der rechten Maustaste auf die Datei oder den Ordner oder klicken Sie auf das Drei-Punkte-Menü neben dem Namen, um das Kontextmenü zu öffnen.
+- Wählen Sie im Kontextmenü die Option „Teilen“ aus.
+
+  <img src={require("./img/extern/teilen-menue.png").default} alt="Teilen auswählen" width="1920"/>
+
+- Auf der rechten Seite des Bildschirms wird eine Seitenleiste geöffnet.
+  <img src={require("./img/extern/sidebar-fenster.png").default} alt="Seitenleistenfenster" width="400"/>
+
+- Klicken Sie auf „Link hinzufügen“, um das Fenster zur Link-Konfiguration zu öffnen.
+
+  <img src={require("./img/extern/oeffentliche-links-popup.png").default} alt="Popup-Fenster" width="1920"/>
+
+- Klicken Sie auf „Optionen“, um den Link zu konfigurieren.
+- Wählen Sie die gewünschten Zugriffsrechte für die Empfänger aus:
+  - „Kann anzeigen“:
+    Empfänger können die Datei ansehen und herunterladen, aber nicht bearbeiten oder Dateien hochladen.
+  - „Kann bearbeiten“:
+    Empfänger können die Datei ansehen, herunterladen, bearbeiten und löschen sowie Dateien in den Ordner hochladen.
+  - „Datei ablegen (geheim)“:
+    Empfänger können nur Dateien hochladen. Sie können den Inhalt weder anzeigen noch bearbeiten.
+
+    <img src={require("./img/extern/rechte.png").default} alt="Zugriffsrechte" width="1920"/>
+
+- Geben Sie ein Passwort in das Feld unter „Passwort“ ein. Ein Passwort ist erforderlich, sofern ein Administrator die Einstellung nicht geändert hat.
+- Optional können Sie ein Ablaufdatum festlegen.
+- Nachdem Sie die Link-Optionen konfiguriert haben, klicken Sie auf „Link kopieren“, um den öffentlichen Link zu erstellen und zu kopieren.
+  Um das Passwort mit einzuschließen, öffnen Sie das Menü neben „Link kopieren“ und wählen Sie „Link und Passwort kopieren“.
+  <img src={require("./img/extern/passwort-auswahl.png").default} alt="Passwortbereich" width="1920"/>
+
+- Der Link ist jetzt erstellt und kann mit den Empfängern geteilt werden.
+  <img src={require("./img/extern/link-kopieren-button.png").default} alt="Link kopieren" width="1920"/>
+
+- Sie können den Link später bearbeiten, indem Sie auf das Drei-Punkte-Menü rechts neben dem Link klicken.
+  Dort können Sie den Link umbenennen, das Ablaufdatum ändern, das Passwort aktualisieren, das Passwort entfernen oder den Link löschen.
+  <img src={require("./img/extern/drei-punkte-menue.png").default} alt="Link-Aktionen-Menü" width="1920"/>
+
+Jetzt wissen Sie, wie Sie Dateien und Ordner sicher mit externen Nutzern teilen können.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/file-drop.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/file-drop.md
new file mode 100644
index 000000000..1cde54e0d
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/file-drop.md
@@ -0,0 +1,46 @@
+---
+sidebar_position: 3
+id: file-drop
+title: File Drop
+description: File Drop (geheim)
+draft: false
+---
+
+# File Drop (geheim) - So funktioniert es
+
+File Drop ermöglicht es Personen, die einen bestimmten Link erhalten, Dateien in einen freigegebenen Ordner hochzuladen.
+Die Linkempfänger können die Dateien, die sich bereits im Ordner befinden, nicht sehen.
+
+## Einen File Drop erstellen
+
+- Klicken Sie mit der rechten Maustaste auf die Datei oder den Ordner oder klicken Sie auf das Drei-Punkte-Menü neben dem Namen, um das Kontextmenü zu öffnen.
+- Wählen Sie im Kontextmenü „Teilen“ aus.
+  <img src={require("./img/file-drop/teilen-menue.png").default} alt="Dropdown-Menü" width="1920" />
+- Auf der rechten Seite des Bildschirms wird eine Seitenleiste geöffnet.
+  <img src={require("./img/file-drop/sidebar-fenster.png").default} alt="Seitenleiste" width="400" />
+- Suchen Sie in der Seitenleiste den Bereich „Öffentliche Links“ und klicken Sie auf „Link hinzufügen“.
+  <img src={require("./img/file-drop/link-hinzufuegen.png").default} alt="Link hinzufügen" width="400" />
+- Klicken Sie auf „Optionen“, um die Linkeinstellungen zu öffnen.
+- Öffnen Sie das Dropdown-Menü für die Zugriffsrechte und wählen Sie „File Drop (geheim)“.
+  <img src={require("./img/file-drop/oeffentliche-links-button.png").default} alt="File Drop auswählen" width="1920" />
+
+- Geben Sie ein Passwort ein und klicken Sie auf „Link kopieren“, um zu bestätigen.
+- Sie können auch ein „Ablaufdatum“ festlegen, wenn der Link ablaufen soll.
+  <img src={require("./img/file-drop/passwort-und-link-kopieren.png").default} alt="Passwort eingeben und Link kopieren" width="1920" />
+- Teilen Sie den Link und das Passwort mit dem Empfänger.
+
+## Was der Empfänger macht
+
+- Der Empfänger öffnet den erhaltenen Link in einem Browser und gibt das Passwort ein. Anschließend klickt er auf „Weiter“.
+  <img src={require("./img/file-drop/passwort-popup.png").default} alt="Passwort eingeben und weiter" width="1920" />
+- Dateien hochladen:
+  - Der File-Drop-Ordner wird geöffnet. Der Empfänger kann Dateien hochladen, ohne den vorhandenen Inhalt des Ordners zu sehen.
+    <img src={require("./img/file-drop/file-drop-bildschirm.png").default} alt="File-Drop-Bereich" width="1920" />
+  - Unten rechts erscheint ein Pop-up-Fenster, das bestätigt, dass der Upload erfolgreich war.
+    <img src={require("./img/file-drop/hochladen-bestaedigung.png").default} alt="Upload-Bestätigung" width="1920" />
+
+:::important
+Empfänger haben keinen Zugriff auf vorhandene Dateien. Sie können nur neue Dateien hinzufügen.
+:::
+
+Jetzt wissen Sie, wie Sie einen File-Drop-Link freigeben.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/extern/drei-punkte-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/extern/drei-punkte-menue.png
new file mode 100644
index 000000000..2e9a0b240
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/extern/drei-punkte-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/extern/link-kopieren-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/extern/link-kopieren-button.png
new file mode 100644
index 000000000..f21c219e6
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/extern/link-kopieren-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/extern/oeffentliche-links-popup.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/extern/oeffentliche-links-popup.png
new file mode 100644
index 000000000..7db8c011b
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/extern/oeffentliche-links-popup.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/extern/passwort-auswahl.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/extern/passwort-auswahl.png
new file mode 100644
index 000000000..a8f4d358b
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/extern/passwort-auswahl.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/extern/rechte.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/extern/rechte.png
new file mode 100644
index 000000000..f40e52367
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/extern/rechte.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/extern/sidebar-fenster.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/extern/sidebar-fenster.png
new file mode 100644
index 000000000..58aa4cda9
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/extern/sidebar-fenster.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/extern/teilen-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/extern/teilen-menue.png
new file mode 100644
index 000000000..7ec536bf0
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/extern/teilen-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/drei-punkte-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/drei-punkte-menue.png
new file mode 100644
index 000000000..ee3d5d38f
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/drei-punkte-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/file-drop-bildschirm.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/file-drop-bildschirm.png
new file mode 100644
index 000000000..d1aa6661f
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/file-drop-bildschirm.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/file-drop-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/file-drop-button.png
new file mode 100644
index 000000000..54a64ff4b
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/file-drop-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/file-drop-website.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/file-drop-website.png
new file mode 100644
index 000000000..3be8f0f28
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/file-drop-website.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/hochladen-bestaedigung.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/hochladen-bestaedigung.png
new file mode 100644
index 000000000..3011035c3
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/hochladen-bestaedigung.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/link-hinzufuegen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/link-hinzufuegen.png
new file mode 100644
index 000000000..d3655c719
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/link-hinzufuegen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/oeffentliche-links-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/oeffentliche-links-button.png
new file mode 100644
index 000000000..69a412201
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/oeffentliche-links-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/passwort-popup.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/passwort-popup.png
new file mode 100644
index 000000000..ad732d48a
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/passwort-popup.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/passwort-und-link-kopieren.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/passwort-und-link-kopieren.png
new file mode 100644
index 000000000..40c747340
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/passwort-und-link-kopieren.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/sidebar-fenster.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/sidebar-fenster.png
new file mode 100644
index 000000000..d3655c719
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/sidebar-fenster.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/teilen-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/teilen-menue.png
new file mode 100644
index 000000000..0534bd1f9
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/file-drop/teilen-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/intern/freigabe-entfernen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/intern/freigabe-entfernen.png
new file mode 100644
index 000000000..c5be9c1fa
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/intern/freigabe-entfernen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/intern/mit-personen-teilen-auswahl.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/intern/mit-personen-teilen-auswahl.png
new file mode 100644
index 000000000..847abbeee
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/intern/mit-personen-teilen-auswahl.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/intern/rechte-optionen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/intern/rechte-optionen.png
new file mode 100644
index 000000000..bac87f27b
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/intern/rechte-optionen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/intern/shared-with-alan.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/intern/shared-with-alan.png
new file mode 100644
index 000000000..35c2d5dc9
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/intern/shared-with-alan.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/intern/sidebar-fenster.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/intern/sidebar-fenster.png
new file mode 100644
index 000000000..86934f065
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/intern/sidebar-fenster.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/intern/suchleiste.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/intern/suchleiste.png
new file mode 100644
index 000000000..a2f50b7a2
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/intern/suchleiste.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/intern/teilen-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/intern/teilen-menue.png
new file mode 100644
index 000000000..28ac95130
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/img/intern/teilen-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/index.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/index.md
new file mode 100644
index 000000000..03b9f0798
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/index.md
@@ -0,0 +1,21 @@
+---
+sidebar_position: 0
+id: sharing-overview
+title: Dateien und Ordner teilen
+---
+
+# Dateien und Ordner teilen
+
+Dieser Abschnitt erklärt, wie das Teilen in OpenCloud funktioniert. Er behandelt internes Teilen mit Mitgliedern und
+Gruppen, öffentliche Links für externen Zugriff und File Drop zum Empfangen von Uploads.
+
+## In diesem Abschnitt
+
+- [Internes Teilen](./internal.md)  
+  Teilen Sie Dateien und Ordner mit Mitgliedern oder Gruppen innerhalb Ihrer Organisation.
+
+- [Externes Teilen](./external.md)  
+  Erstellen Sie öffentliche Links und verwalten Sie Optionen wie Berechtigungen, Passwörter und Ablaufdaten.
+
+- [File Drop](./file-drop.md)  
+  Erlauben Sie externen Benutzern das Hochladen von Dateien, ohne ihnen Zugriff auf bestehende Inhalte zu geben.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/internal.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/internal.md
new file mode 100644
index 000000000..59d666be6
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/sharing/internal.md
@@ -0,0 +1,63 @@
+---
+sidebar_position: 1
+id: internal
+title: Intern
+description: Organisationsinterne Freigabe von Dateien und Ordnern in OpenCloud
+draft: false
+---
+
+# Organisationsinterne Freigabe von Dateien und Ordnern in OpenCloud
+
+Dateien und Ordner können innerhalb der Organisation mit einzelnen Mitgliedern oder Gruppen geteilt werden. Dabei können unterschiedliche Zugriffsrechte vergeben werden.
+
+## Interne Freigabe erstellen
+
+- Öffnen Sie das Drei-Punkte-Menü neben der Datei oder dem Ordner, den Sie freigeben möchten.
+
+- Wählen Sie im Kontextmenü die Option „Teilen“ aus.
+
+  <img src={require("./img/intern/teilen-menue.png").default} alt="Teilen auswählen" width="1920"/>
+
+- Die Seitenleiste wird auf der rechten Seite des Bildschirms geöffnet.
+
+  <img src={require("./img/intern/sidebar-fenster.png").default} alt="Seitenleiste anzeigen" width="1920"/>
+
+- Wählen Sie in der Seitenleiste den Bereich „Interne Freigabe“ aus.
+
+  <img src={require("./img/intern/mit-personen-teilen-auswahl.png").default} alt="Interne Freigabe auswählen" width="400"/>
+
+- Geben Sie mindestens drei Zeichen in das Suchfeld ein, um nach Mitgliedern oder Gruppen zu suchen.
+
+  <img src={require("./img/intern/suchleiste.png").default} alt="Nach Personen oder Gruppen suchen" width="400"/>
+
+- Wählen Sie die gewünschte Person oder Gruppe aus der Vorschlagsliste aus.
+
+- Legen Sie die Zugriffsrechte fest:
+  - „Kann anzeigen“:
+    Mitglieder können die Datei oder den Ordner anzeigen und herunterladen. Sie können keine Inhalte bearbeiten oder in freigegebene Ordner hochladen.
+
+  - „Kann hochladen“:
+    Mitglieder können Inhalte anzeigen und herunterladen. Bei Ordnern können sie zusätzlich eigene Dateien hochladen.
+
+  - „Kann bearbeiten“:
+    Mitglieder können Inhalte anzeigen, herunterladen, hochladen, erstellen, bearbeiten und löschen.
+
+  <img src={require("./img/intern/rechte-optionen.png").default} alt="Rechte auswählen" width="400"/>
+
+- Klicken Sie auf „Teilen“, um die interne Freigabe zu erstellen.
+
+Die freigegebenen Mitglieder oder Gruppen werden anschließend im Bereich „Freigegeben mit“ angezeigt.
+
+<img src={require("./img/intern/shared-with-alan.png").default} alt="Freigegebene Mitglieder anzeigen" width="400"/>
+
+## Interne Freigabe entfernen
+
+Eine bestehende interne Freigabe kann jederzeit entfernt werden.
+
+- Öffnen Sie im Bereich „Freigegeben mit“ das Drei-Punkte-Menü neben der Person oder Gruppe.
+
+- Wählen Sie die Option „Freigabe entfernen“ aus.
+
+<img src={require("./img/intern/freigabe-entfernen.png").default} alt="Freigabe entfernen" width="400"/>
+
+Der Zugriff wird sofort entfernt. Die betroffene Person oder Gruppe kann danach nicht mehr über diese Freigabe auf die Datei oder den Ordner zugreifen.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/_category_.json b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/_category_.json
new file mode 100644
index 000000000..eac5ba4c7
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/_category_.json
@@ -0,0 +1,8 @@
+{
+  "label": "Im Team mit Spaces arbeiten",
+  "position": 5,
+  "link": {
+    "type": "doc",
+    "id": "spaces-overview"
+  }
+}
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/add-user.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/add-user.md
new file mode 100644
index 000000000..1a7b43997
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/add-user.md
@@ -0,0 +1,46 @@
+---
+sidebar_position: 3
+id: add-members
+title: Mitglieder hinzufügen
+description: Neue Mitglieder zu Ihrem Space in OpenCloud hinzufügen
+draft: false
+---
+
+# Neues Mitglied zu Ihrem Space in OpenCloud hinzufügen
+
+Sie können ganz einfach neue Mitglieder einladen, um in Ihrem Space zusammenzuarbeiten, indem Sie die folgenden Schritte ausführen.
+
+- Gehen Sie zu Ihrem Space und öffnen Sie das Mitglieder-Menü.
+  <img src={require("./img/add-user/mitglieder-menue.png").default} alt="Mitglieder-Menü" width="1920"/>
+
+- Im Mitglieder-Menü können Sie nach dem Benutzer aus Ihrer Organisation suchen, den Sie hinzufügen möchten.
+
+  <img src={require("./img/add-user/mitglieder-suche.png").default} alt="Benutzer suchen" width="1920"/>
+
+- Wählen Sie die gewünschten Rechte für das Mitglied aus, z. B. ob die Person nur lesen oder auch bearbeiten darf.
+
+  <img src={require("./img/add-user/rechte.png").default} alt="Rechte auswählen" width="1920"/>
+
+- Klicken Sie auf „Hinzufügen“, um das Mitglied in den Space einzuladen.
+
+  <img src={require("./img/add-user/mitglieder-hinzufuegen.png").default} alt="Mitglied hinzugefügt" width="1920"/>
+
+- Um die Rechte eines Mitglieds zu ändern, öffnen Sie das Mitglieder-Menü, klicken Sie auf den entsprechenden Benutzer und wählen Sie die gewünschten neuen Rechte aus.
+
+  <img src={require("./img/add-user/rechte-aendern.png").default} alt="Rechte ändern" width="1920"/>
+
+- Öffnen Sie das Mitglieder-Menü, klicken Sie auf das Drei-Punkte-Menü neben dem Mitglied und verwenden Sie nach Bedarf „Zugriffsdetails“, „Ablaufdatum festlegen“ oder „Mitglied entfernen“.
+
+  <img src={require("./img/add-user/mitglied-entfernen.png").default} alt="Mitglied entfernen" width="1920"/>
+
+:::note
+Das entfernte Mitglied verliert sofort den Zugriff auf den Space.
+:::
+
+:::important
+
+- Das hinzugefügte Mitglied hat sofortigen Zugriff auf den Space.
+- Achtung: Jeder Benutzer mit dem Recht „Kann verwalten“ hat die Berechtigung, den Space zu deaktivieren und zu löschen.
+- Ein gelöschter Space kann nicht wiederhergestellt werden, also seien Sie vorsichtig, wem Sie diese Rechte gewähren.
+
+:::
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/create.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/create.md
new file mode 100644
index 000000000..9aa160ea9
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/create.md
@@ -0,0 +1,39 @@
+---
+sidebar_position: 2
+id: create
+title: Space erstellen
+description: Spaces erstellen und Daten in OpenCloud teilen
+draft: false
+---
+
+# Spaces erstellen und Daten in OpenCloud teilen
+
+Mit Spaces können Sie Daten mit bestimmten Personen innerhalb Ihrer Organisation teilen. Alle Mitglieder eines Spaces haben den festgelegten Zugriff auf die Daten, und Sie können die Bearbeitungsrechte für jedes Mitglied individuell anpassen.
+
+## Einen neuen Space erstellen
+
+- Gehen Sie auf den Menüpunkt „Spaces“ in der linken Seitenleiste.
+
+  <img src={require("./img/create/linke-seitenleiste.png").default} alt="Space in linker Seitenleiste" width="1920"/>
+
+- Klicken Sie auf „+ Neuer Space“.
+
+  <img src={require("./img/create/space-erstellen.png").default} alt="Neuer Space" width="1920"/>
+
+- Geben Sie den gewünschten Namen für den Space ein.
+
+  <img src={require("./img/create/benennen.png").default} alt="Space-Namen eingeben" width="1920"/>
+
+- Klicken Sie auf „Erstellen“.
+
+## Ihr neuer Space
+
+Ihr neuer Space erscheint nun unter „Spaces“ und ist bereit zur Nutzung.
+
+<img src={require("./img/create/neuer-space.png").default} alt="Erstellter Space" width="1920"/>
+
+Jetzt wissen Sie, wie Sie schnell und einfach einen Space erstellen und mit dem Teilen von Daten beginnen können.
+
+:::important
+Spaces können nur dauerhaft innerhalb Ihrer eigenen Organisation geteilt werden.
+:::
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/customize.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/customize.md
new file mode 100644
index 000000000..9e43109de
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/customize.md
@@ -0,0 +1,45 @@
+---
+sidebar_position: 8
+id: customize
+title: Spaces anpassen
+description: Einen Space in OpenCloud anpassen
+draft: false
+---
+
+# Spaces anpassen in OpenCloud
+
+Sie können einen Space entweder in der Space-Übersicht oder direkt im Space selbst anpassen.
+
+## Beschreibung bearbeiten
+
+Klicken Sie auf „Beschreibung bearbeiten“. Geben Sie Ihre Beschreibung in den sich öffnenden Texteditor ein, speichern Sie sie und schließen Sie ihn anschließend.
+
+<img src={require("./img/customize/beschreibung-erstellen.png").default} alt="Beschreibung erstellen" width="1920"/>
+<img src={require("./img/customize/beschreibung-editor.png").default} alt="Beschreibung Editor" width="1920"/>
+
+Die Beschreibung kann auch direkt im Space bearbeitet werden, indem Sie auf den Stift daneben klicken.
+
+## Untertitel bearbeiten
+
+Klicken Sie auf „Untertitel bearbeiten“. Geben Sie den gewünschten Untertitel in den Texteditor ein und speichern Sie ihn.
+
+<img src={require("./img/customize/untertitel-aendern.png").default} alt="Untertitel ändern" width="1920"/>
+<img src={require("./img/customize/untertitel-bearbeiten.png").default} alt="Untertitel bearbeiten und speichern" width="1920"/>
+
+## Bild festlegen
+
+Klicken Sie auf „Bild bearbeiten“ und dann auf „Bild festlegen“. Wählen Sie im sich öffnenden Fenster das gewünschte Bild für Ihren Space aus und bestätigen Sie. Wählen Sie dann den gewünschten Ausschnitt aus und bestätigen Sie.
+
+<img src={require("./img/customize/spacebild-bearbeiten.png").default} alt="Spacebild bearbeiten" width="1920"/>
+<img src={require("./img/customize/spacebild-zuschneiden.png").default} alt="Spacebild zuschneiden" width="1920"/>
+<img src={require("./img/customize/spacebild.png").default} alt="Spacebild" width="1920"/>
+
+## Symbol festlegen
+
+Klicken Sie auf „Bild bearbeiten“ und dann auf „Symbol festlegen“. Wählen Sie im sich öffnenden Fenster das gewünschte Symbol für Ihren Space aus.
+
+<img src={require("./img/customize/symbol-als-spacebild-option.png").default} alt="Symbol als Spacebild Option" width="1920"/>
+<img src={require("./img/customize/symbol-auswahl.png").default} alt="Symbol Auswahl" width="500"/>
+<img src={require("./img/customize/symbol-als-spacebild.png").default} alt="Symbol als Spacebild" width="1920"/>
+
+Jetzt wissen Sie, wie Sie einen Space anpassen können.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/delete.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/delete.md
new file mode 100644
index 000000000..4448e3a48
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/delete.md
@@ -0,0 +1,35 @@
+---
+sidebar_position: 6
+id: delete
+title: Einen Space löschen
+description: Einen Space in OpenCloud löschen
+draft: false
+---
+
+# Einen Space in OpenCloud löschen
+
+Bevor Sie einen Space löschen, muss er zuerst deaktiviert werden.
+
+## Space deaktivieren
+
+- Folgen Sie der Anleitung unter [Einen Space deaktivieren](./enable-disable.md), um den Space vor dem Löschen zu deaktivieren.
+
+- Wenn der Space nach der Deaktivierung nicht mehr sichtbar ist, stellen Sie sicher, dass der Filter für deaktivierte Spaces aktiviert ist, damit der Space wieder angezeigt wird.
+
+  <img src={require("./img/delete/einblenden.png").default} alt="Deaktivierte Spaces anzeigen" width="1920"/>
+
+## Space löschen
+
+- Wählen Sie den Space aus, den Sie löschen möchten, oder öffnen Sie das Kontextmenü und klicken Sie auf „Löschen“.
+
+  <img src={require("./img/delete/loeschen-top-bar.png").default} alt="Space löschen in der oberen Leiste und im Kontextmenü" width="1920"/>
+
+- Bestätigen Sie, dass Sie den Space löschen möchten.
+
+  <img src={require("./img/delete/loeschen-bestaetigen.png").default} alt="Bestätigen" width="500"/>
+
+:::caution  
+Ein gelöschter Space kann nicht wiederhergestellt werden. Stellen Sie sicher, dass vor dem Löschen keine wichtigen Daten verloren gehen.
+:::
+
+Jetzt wissen Sie, wie Sie einen Space löschen können.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/enable-disable.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/enable-disable.md
new file mode 100644
index 000000000..92d8bcfb5
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/enable-disable.md
@@ -0,0 +1,56 @@
+---
+sidebar_position: 5
+id: disable-enable
+title: Deaktivieren und Aktivieren eines Spaces
+description: Einen Space in OpenCloud deaktivieren und aktivieren
+draft: false
+---
+
+# Einen Space in OpenCloud deaktivieren und aktivieren
+
+Sie können einen Space auf verschiedene Arten deaktivieren und später wieder aktivieren. Nur ein Space-Admin oder ein Administrator kann dies tun.
+
+## Space deaktivieren
+
+- Wählen Sie den gewünschten Space aus.
+- Klicken Sie in der oberen Aktionsleiste auf „Deaktivieren“ oder öffnen Sie das Kontextmenü.
+
+  <img src={require("./img/enable-disable/deaktivieren-spaceuebersicht.png").default} alt="Space in der Übersicht deaktivieren" width="1920"/>
+
+- Bestätigen Sie die Deaktivierung.
+
+  <img src={require("./img/enable-disable/deaktivieren-bestaetigen.png").default} alt="Deaktivierung bestätigen" width="1920"/>
+
+- Der Space ist jetzt deaktiviert.
+
+  <img src={require("./img/enable-disable/space-nicht-sichtbar.png").default} alt="Deaktivierter Space" width="1920"/>
+  :::note
+  Es werden keine Daten gelöscht. Nur der Space-Admin oder der Administrator kann den Space wieder aktivieren.
+  :::
+
+## Space aktivieren
+
+- Nachdem der Space deaktiviert wurde, ersetzt die Option „Aktivieren“ nun „Deaktivieren“.
+
+  <img src={require("./img/enable-disable/aktivieren-button.png").default} alt="Admin general" width="1920"/>
+
+- Klicken Sie darauf, um den Space wieder zu aktivieren.
+
+- Wenn der Space nicht sichtbar ist, kann der Filter „Deaktivierte Spaces anzeigen“ aktiviert sein.
+
+  <img src={require("./img/enable-disable/deaktivierte-spaces-einblenden.png").default} alt="Deaktivierte Spaces anzeigen" width="1920"/>
+
+- Aktivieren Sie den Filter, damit der Space angezeigt wird und wieder aktiviert werden kann.
+
+  <img src={require("./img/enable-disable/wieder-verfuegbar.png").default} alt="Space wieder verfügbar" width="1920"/>
+
+## Aktivieren durch den Administrator
+
+Ein Administrator kann einen Space auch über [Admin-Einstellungen](../admin/settings.md#spaces) aktivieren oder deaktivieren.
+
+- Öffnen Sie in den Admin-Einstellungen den Bereich „Spaces“.
+- Suchen Sie den Space, der aktiviert oder deaktiviert werden soll.
+- Öffnen Sie das Drei-Punkte-Menü und wählen Sie „Aktivieren“ oder „Deaktivieren“.
+- Bestätigen Sie die Aktion.
+
+Der Space wird dann in der Space-Übersicht im entsprechenden Zustand angezeigt.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/add-user/mitglied-entfernen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/add-user/mitglied-entfernen.png
new file mode 100644
index 000000000..869ccc10d
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/add-user/mitglied-entfernen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/add-user/mitglieder-hinzufuegen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/add-user/mitglieder-hinzufuegen.png
new file mode 100644
index 000000000..408c87241
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/add-user/mitglieder-hinzufuegen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/add-user/mitglieder-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/add-user/mitglieder-menue.png
new file mode 100644
index 000000000..b432745df
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/add-user/mitglieder-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/add-user/mitglieder-suche.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/add-user/mitglieder-suche.png
new file mode 100644
index 000000000..408c87241
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/add-user/mitglieder-suche.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/add-user/rechte-aendern.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/add-user/rechte-aendern.png
new file mode 100644
index 000000000..74f6565fe
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/add-user/rechte-aendern.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/add-user/rechte.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/add-user/rechte.png
new file mode 100644
index 000000000..408c87241
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/add-user/rechte.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/create/benennen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/create/benennen.png
new file mode 100644
index 000000000..18c1deeed
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/create/benennen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/create/linke-seitenleiste.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/create/linke-seitenleiste.png
new file mode 100644
index 000000000..85d4e10d0
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/create/linke-seitenleiste.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/create/neuer-space.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/create/neuer-space.png
new file mode 100644
index 000000000..b86af4acb
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/create/neuer-space.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/create/space-erstellen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/create/space-erstellen.png
new file mode 100644
index 000000000..3d3d83cf6
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/create/space-erstellen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/beschreibung-editor.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/beschreibung-editor.png
new file mode 100644
index 000000000..93ea80876
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/beschreibung-editor.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/beschreibung-erstellen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/beschreibung-erstellen.png
new file mode 100644
index 000000000..7c9428617
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/beschreibung-erstellen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/spacebild-bearbeiten.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/spacebild-bearbeiten.png
new file mode 100644
index 000000000..f4255b9c2
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/spacebild-bearbeiten.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/spacebild-zuschneiden.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/spacebild-zuschneiden.png
new file mode 100644
index 000000000..10f9b2ba9
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/spacebild-zuschneiden.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/spacebild.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/spacebild.png
new file mode 100644
index 000000000..eedfc7b12
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/spacebild.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/symbol-als-spacebild-option.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/symbol-als-spacebild-option.png
new file mode 100644
index 000000000..e10a2697c
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/symbol-als-spacebild-option.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/symbol-als-spacebild.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/symbol-als-spacebild.png
new file mode 100644
index 000000000..4beac082e
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/symbol-als-spacebild.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/symbol-auswahl.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/symbol-auswahl.png
new file mode 100644
index 000000000..cc18e010e
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/symbol-auswahl.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/untertitel-aendern.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/untertitel-aendern.png
new file mode 100644
index 000000000..40029133d
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/untertitel-aendern.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/untertitel-bearbeiten.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/untertitel-bearbeiten.png
new file mode 100644
index 000000000..275e2e089
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/customize/untertitel-bearbeiten.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/confirm.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/confirm.png
new file mode 100644
index 000000000..57e702482
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/confirm.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/deactivate-filter.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/deactivate-filter.png
new file mode 100644
index 000000000..64e7de42b
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/deactivate-filter.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/deaktivieren-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/deaktivieren-button.png
new file mode 100644
index 000000000..bd6bd181a
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/deaktivieren-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/delete-top-bar.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/delete-top-bar.png
new file mode 100644
index 000000000..de6186c3e
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/delete-top-bar.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/einblenden.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/einblenden.png
new file mode 100644
index 000000000..cb796647e
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/einblenden.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/loeschen-bestaetigen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/loeschen-bestaetigen.png
new file mode 100644
index 000000000..0f7a062bf
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/loeschen-bestaetigen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/loeschen-kontext-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/loeschen-kontext-menue.png
new file mode 100644
index 000000000..104e7ad9a
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/loeschen-kontext-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/loeschen-top-bar.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/loeschen-top-bar.png
new file mode 100644
index 000000000..3ca278ad6
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/delete/loeschen-top-bar.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/enable-disable/aktivieren-bestaetigen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/enable-disable/aktivieren-bestaetigen.png
new file mode 100644
index 000000000..445799510
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/enable-disable/aktivieren-bestaetigen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/enable-disable/aktivieren-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/enable-disable/aktivieren-button.png
new file mode 100644
index 000000000..147fdc40c
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/enable-disable/aktivieren-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/enable-disable/deaktivieren-bestaetigen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/enable-disable/deaktivieren-bestaetigen.png
new file mode 100644
index 000000000..de17fe0fa
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/enable-disable/deaktivieren-bestaetigen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/enable-disable/deaktivieren-spaceuebersicht.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/enable-disable/deaktivieren-spaceuebersicht.png
new file mode 100644
index 000000000..9bd8dff4b
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/enable-disable/deaktivieren-spaceuebersicht.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/enable-disable/deaktivierte-spaces-einblenden.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/enable-disable/deaktivierte-spaces-einblenden.png
new file mode 100644
index 000000000..356745cd3
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/enable-disable/deaktivierte-spaces-einblenden.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/enable-disable/space-nicht-sichtbar.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/enable-disable/space-nicht-sichtbar.png
new file mode 100644
index 000000000..f0932c86b
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/enable-disable/space-nicht-sichtbar.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/enable-disable/wieder-verfuegbar.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/enable-disable/wieder-verfuegbar.png
new file mode 100644
index 000000000..4e05122e4
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/enable-disable/wieder-verfuegbar.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/invite-user/hinzufuegen-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/invite-user/hinzufuegen-button.png
new file mode 100644
index 000000000..8adbf3496
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/invite-user/hinzufuegen-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/invite-user/mitglieder-rechte.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/invite-user/mitglieder-rechte.png
new file mode 100644
index 000000000..fe488db81
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/invite-user/mitglieder-rechte.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/invite-user/mitglieder-suchleiste.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/invite-user/mitglieder-suchleiste.png
new file mode 100644
index 000000000..a5f26e72f
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/invite-user/mitglieder-suchleiste.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/invite-user/space-mitglieder-menue.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/invite-user/space-mitglieder-menue.png
new file mode 100644
index 000000000..59ab8fdfa
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/invite-user/space-mitglieder-menue.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/quota/bestaetigen-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/quota/bestaetigen-button.png
new file mode 100644
index 000000000..a02de7362
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/quota/bestaetigen-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/quota/individuelle-quota.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/quota/individuelle-quota.png
new file mode 100644
index 000000000..1cc6e8ba6
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/quota/individuelle-quota.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/quota/quota-aendern-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/quota/quota-aendern-button.png
new file mode 100644
index 000000000..6e6948584
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/quota/quota-aendern-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/quota/standard-quota.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/quota/standard-quota.png
new file mode 100644
index 000000000..963f509f6
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/quota/standard-quota.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/rename/space-mit-neuem-namen.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/rename/space-mit-neuem-namen.png
new file mode 100644
index 000000000..6a844c2e3
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/rename/space-mit-neuem-namen.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/rename/umbenennen-button.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/rename/umbenennen-button.png
new file mode 100644
index 000000000..3cb4ad739
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/rename/umbenennen-button.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/rename/umbenennen-popup.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/rename/umbenennen-popup.png
new file mode 100644
index 000000000..3a701d216
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/rename/umbenennen-popup.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/why-spaces/alan-left.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/why-spaces/alan-left.png
new file mode 100644
index 000000000..01e2c4179
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/why-spaces/alan-left.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/why-spaces/spaces.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/why-spaces/spaces.png
new file mode 100644
index 000000000..95ee417f8
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/why-spaces/spaces.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/why-spaces/spaghetti-alan-left.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/why-spaces/spaghetti-alan-left.png
new file mode 100644
index 000000000..a1ebee16c
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/why-spaces/spaghetti-alan-left.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/why-spaces/spaghetti.png b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/why-spaces/spaghetti.png
new file mode 100644
index 000000000..7ba9019cc
Binary files /dev/null and b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/img/why-spaces/spaghetti.png differ
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/index.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/index.md
new file mode 100644
index 000000000..39c6be1f0
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/index.md
@@ -0,0 +1,39 @@
+---
+sidebar_position: 0
+id: spaces-overview
+title: Im Team mit Spaces arbeiten
+---
+
+# Im Team mit Spaces arbeiten
+
+Spaces sind gemeinsam genutzte Arbeitsbereiche in OpenCloud. Sie helfen Teams dabei, Inhalte zu organisieren, den
+Zugriff zu verwalten und Projekt- oder Teamdateien von persönlichen Daten zu trennen.
+
+## In diesem Abschnitt
+
+- [Warum Spaces?](./why-spaces.md)  
+  Erfahren Sie, warum Spaces sich besser für Teamarbeit eignen als klassische Freigaben.
+
+- [Space erstellen](./create.md)  
+  Legen Sie einen neuen Space für ein Team, ein Projekt oder eine Abteilung an.
+
+- [Mitglieder hinzufügen](./add-user.md)  
+  Laden Sie Personen in einen Space ein und vergeben Sie die passenden Berechtigungen.
+
+- [Space-Quota bearbeiten](./quota.md)  
+  Passen Sie die für einen Space verfügbare Speicherkapazität an.
+
+- [Space deaktivieren und aktivieren](./enable-disable.md)  
+  Deaktivieren Sie einen Space vorübergehend und aktivieren Sie ihn später wieder.
+
+- [Space löschen](./delete.md)  
+  Entfernen Sie einen Space endgültig, wenn er nicht mehr benötigt wird.
+
+- [Space umbenennen](./rename.md)  
+  Ändern Sie den Namen eines vorhandenen Space.
+
+- [Spaces anpassen](./customize.md)  
+  Aktualisieren Sie Beschreibungen, Untertitel, Bilder und Symbole für einen Space.
+
+- [Best Practice](./spaces-best-practices.md)  
+  Beachten Sie empfohlene Strukturen und Namenskonventionen für Spaces.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/quota.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/quota.md
new file mode 100644
index 000000000..9d8b0d3b4
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/quota.md
@@ -0,0 +1,30 @@
+---
+sidebar_position: 4
+id: space-quota
+title: Space Quota
+description: Quota eines Spaces bearbeiten
+draft: false
+---
+
+# Quota eines Spaces bearbeiten
+
+Als Space-Administrator können Sie die Speicherkapazität (Quota) eines Spaces anpassen, um den verfügbaren Speicherplatz nach Bedarf zu erhöhen oder zu verringern.
+
+## Schritte zum Bearbeiten der Space-Quota
+
+- Wählen Sie die Option „Quota ändern“ in der Top-Bar oder im Kontextmenü.
+
+  <img src={require("./img/quota/quota-aendern-button.png").default} alt="Kontextmenü" width="1920"/>
+
+- Im sich öffnenden Fenster stehen zwei Optionen zur Verfügung:
+- Wählen Sie eine Standardgröße (z. B. 5 GB) aus dem Dropdown-Menü.
+
+  <img src={require("./img/quota/standard-quota.png").default} alt="Quota auswählen" width="1920"/>
+
+- Geben Sie eine individuelle Speichergröße ein.
+
+  <img src={require("./img/quota/individuelle-quota.png").default} alt="Quota eingeben" width="1920"/>
+
+- Klicken Sie auf „Bestätigen“, um die Änderung zu übernehmen.
+
+Die Quota des Spaces wird entsprechend der neuen Einstellungen aktualisiert.
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/rename.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/rename.md
new file mode 100644
index 000000000..aa8570f01
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/rename.md
@@ -0,0 +1,22 @@
+---
+sidebar_position: 7
+id: rename
+title: Space umbenennen
+description: Einen Space in OpenCloud umbenennen
+draft: false
+---
+
+# Einen Space in OpenCloud umbenennen
+
+Sie können einen bestehenden Space jederzeit umbenennen, damit er besser zu seinem Zweck oder Inhalt passt.
+
+- Klicken Sie im Space-Überblick auf das Drei-Punkte-Menü oder machen Sie einen Rechtsklick auf den Space und wählen Sie „Umbenennen“.
+
+  <img src={require("./img/rename/umbenennen-button.png").default} alt="Umbenennen" width="1920"/>
+
+- Geben Sie den neuen Namen für den Space ein und bestätigen Sie.
+
+  <img src={require("./img/rename/umbenennen-popup.png").default} alt="Bestätigen" width="1920"/>
+
+- Jetzt wurde Ihr Space umbenannt.
+  <img src={require("./img/rename/space-mit-neuem-namen.png").default} alt="Umbenannter Space" width="1920"/>
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/spaces-best-practices.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/spaces-best-practices.md
new file mode 100644
index 000000000..175733238
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/spaces-best-practices.md
@@ -0,0 +1,135 @@
+---
+sidebar_position: 9
+id: best-practice
+title: Best practice
+description: Best Practices zur Organisation von Spaces in OpenCloud
+---
+
+# Best Practices zur Organisation von Spaces in OpenCloud
+
+Spaces sind kollaborative Bereiche, die von mehreren Nutzern verwendet
+werden. Anders als persönlicher Speicher müssen sie so aufgebaut sein,
+dass sie Klarheit, Zusammenarbeit und Skalierbarkeit unterstützen.
+Dieser Leitfaden hilft dir dabei, Spaces gut organisiert und langfristig
+nutzbar einzurichten und zu pflegen.
+
+## Allgemeine Grundsätze
+
+- Erst planen -- Behandle Spaces nicht wie spontanen Ablagespeicher.
+  Denke voraus.
+- In Rollen und Teams denken -- Strukturiere anhand der Zusammenarbeit
+  von Personen.
+- Skalierbarkeit beachten -- Wähle eine Struktur, die jetzt _und_
+  später mit mehr Nutzern funktioniert.
+- Konsistenz anwenden -- Benennung, Zugriffsrechte und Aufbau sollten
+  gemeinsamen Regeln folgen.
+
+## Ordnerstruktur: Empfohlene Muster
+
+### Beispiel: Familie
+
+```plaintext
+📁 Familien-Space
+ ├── 📂 Dokumente
+ │    ├── 🧾 Versicherungen
+ │    └── 📑 Verträge
+ ├── 📂 Fotos
+ │    ├── 📸 2024
+ │    └── 📸 2023
+ └── 📂 Gemeinsame Notizen
+```
+
+### Schule / Kindergarten
+
+```plaintext
+📁 2024
+ ├── 📂 Klasse 3B
+ │    ├── 📂 Unterrichtsmaterial
+ │    ├── 📂 Elternkommunikation
+ │    ├── 📂 Hausaufgaben
+ │    └── 📂 Veranstaltungen & Fotos
+ ├── 📂 Klasse 4C
+ │    ├── 📂 Unterrichtsmaterial
+ │    ├── 📂 Elternkommunikation
+ │    ├── 📂 Hausaufgaben
+ │    └── 📂 Veranstaltungen & Fotos
+```
+
+### Unternehmen / Team
+
+```plaintext
+📁 Marketing-Team
+ ├── 📂 Kampagnen
+ │    ├── 📂 Q1-2025
+ │    └── 📂 Q2-2025
+ ├── 📂 Vorlagen
+ ├── 📂 Berichte
+ └── 📂 Meeting-Notizen
+```
+
+## Namenskonventionen
+
+- Klare, beschreibende Namen verwenden -- vermeide „Neuer Ordner" oder
+  kryptische Titel
+- Bevorzuge lowercase-mit-bindestrichen oder Title Case
+- Relevante Daten hinzufügen: `bericht-2025-Q2.pdf` oder
+  `Budget 2024.xlsx`
+- Sonderzeichen vermeiden: `& % $ § !` können Integrationen stören
+
+## Richtlinien für Eigentümerschaft & Zugriffe
+
+- Space Owner festlegen: verantwortlich für Struktur und
+  Berechtigungen
+- Wenn möglich Gruppen für Zugriffskontrolle nutzen (z. B. `staff`,
+  `students`, `parents`)
+- Sensible Inhalte in separate Ordner mit eingeschränktem Zugriff
+  auslagern
+- Bearbeitungs- und Leserechte klar definieren
+
+## Archivierung & Aufräumen
+
+- Einen Archiv-Ordner für alte oder ungenutzte Dateien einrichten
+- Den Space jährlich überprüfen und veraltete Inhalte entfernen
+- Bei Unsicherheit Versionierung nutzen oder vor dem Löschen
+  exportieren
+
+## Häufige Stolperfallen
+
+| ❌ Nicht tun                               | ✅ Besser so                               |
+| ------------------------------------------ | ------------------------------------------ |
+| Alle Dateien im Root-Ordner ablegen        | Klare Unterordner verwenden                |
+| Persönliche und gemeinsame Inhalte mischen | Persönliche Daten in „Persönlich" belassen |
+| Allen Nutzern Vollzugriff geben            | Least-Privilege-Prinzip anwenden           |
+| Uneinheitliche Benennungen nutzen          | Konventionen definieren & einhalten        |
+
+## Schnellstart-Vorlage zum Teilen
+
+Du kannst diese Vorlage für neue Spaces verwenden:
+
+```plaintext
+📁 [Team-/Projektname]
+ ├── 📂 Dokumente
+ ├── 📂 Planung
+ ├── 📂 Ressourcen
+ ├── 📂 Archiv
+ └── README.md (Zweck, Struktur, Regeln des Spaces)
+```
+
+## Zusammenfassung
+
+---
+
+Ziel Vorgehen
+
+---
+
+Spaces leicht navigierbar Klare Ordnernamen & Hierarchie nutzen
+machen
+
+Berechtigungschaos vermeiden Eigentümer und Rollen definieren
+
+Ordnung behalten Regelmäßig prüfen und archivieren
+
+Zusammenarbeit fördern Gruppenrechte & standardisierte Benennung
+
+---
diff --git a/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/why-spaces.md b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/why-spaces.md
new file mode 100644
index 000000000..105faaead
--- /dev/null
+++ b/i18n/de/docusaurus-plugin-content-docs/version-7.x/user/spaces/why-spaces.md
@@ -0,0 +1,42 @@
+---
+sidebar_position: 1
+id: why-spaces
+title: Warum Spaces?
+description: Warum man Spaces nutzen sollte
+draft: false
+---
+
+# Warum du Spaces verwenden solltest – und wie sie sich vom klassischen Teilen unterscheiden
+
+## Das Problem mit klassischem Teilen
+
+### Ein einfaches Beispiel
+
+- Alan erstellt einen Ordner mit dem Namen „Projekt“ und teilt ihn mit mehreren Personen.  
+  <img src={require("./img/why-spaces/spaghetti.png").default} alt="Mitglieder-Menü" width="500"/>
+- Später verlässt Alan die Organisation.
+- Da Alans Account gelöscht wird, verschwinden auch einige geteilte Ordner.
+- Benutzer verlieren den Zugriff auf bestimmte Ordner und deren Inhalte.
+
+  <img src={require("./img/why-spaces/alan-left.png").default} alt="Mitglieder-Menü" width="500"/>
+
+### Dieses Szenario zeigt mehrere Risiken auf
+
+- Potenzieller Datenverlust, wenn der ursprüngliche Eigentümer das Unternehmen verlässt
+- Projektdaten werden auf das persönliche Speicherkontingent angerechnet – ungünstig für Teamarbeit
+- Administrativer Aufwand beim Übertragen der Eigentümerschaft
+- Chaos durch „Spaghetti“-Sharing – Benutzer verlieren den Überblick in „Mit mir geteilt“ oder „Von mir geteilt“
+
+## Die Vorteile von Spaces
+
+Spaces wurden entwickelt, um diese Einschränkungen zu überwinden und eine stabilere, teamfreundlichere Lösung zu bieten:
+
+- **Organisationsgebunden:** Spaces gehören der Organisation, nicht einzelnen Personen.
+- **Gemeinsame Verwaltung:** Mehrere Benutzer können einen Space gemeinsam verwalten.
+- **Eigenes Speicherkontingent:** Jeder Space hat ein eigenes Speicherkontingent, unabhängig vom persönlichen Speicherplatz.
+
+  <img src={require("./img/why-spaces/spaces.png").default} alt="Mitglieder-Menü" width="500"/>
+
+:::note
+Spaces machen Zusammenarbeit einfacher, sicherer und skalierbarer – besonders in professionellen Umgebungen.
+:::
diff --git a/versioned_docs/version-7.x/_static/env-vars/activitylog.yaml b/versioned_docs/version-7.x/_static/env-vars/activitylog.yaml
new file mode 100644
index 000000000..62c1ba3c1
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/activitylog.yaml
@@ -0,0 +1,60 @@
+# Autogenerated
+# Filename: activitylog.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9197
+  token: ""
+  pprof: false
+  zpages: false
+events:
+  endpoint: 127.0.0.1:9233
+  cluster: opencloud-cluster
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+  enable_tls: false
+  username: ""
+  password: ""
+store:
+  store: nats-js-kv
+  nodes:
+  - 127.0.0.1:9233
+  database: activitylog
+  ttl: 0s
+  username: ""
+  password: ""
+  enable_tls: false
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+reva_gateway: eu.opencloud.api.gateway
+grpc_client_tls: null
+http:
+  addr: 127.0.0.1:9195
+  root: /
+  cors:
+    allow_origins:
+    - '*'
+    allow_methods:
+    - GET
+    allow_headers:
+    - Authorization
+    - Origin
+    - Content-Type
+    - Accept
+    - X-Requested-With
+    - X-Request-Id
+    - Ocs-Apirequest
+    allow_credentials: true
+  tls:
+    enabled: false
+    cert: ""
+    key: ""
+token_manager:
+  jwt_secret: ""
+translation_path: ""
+default_language: en
+service_account:
+  service_account_id: ""
+  service_account_secret: ""
+write_buffer_duration: 10s
+max_activities: 6000
diff --git a/versioned_docs/version-7.x/_static/env-vars/activitylog_configvars.md b/versioned_docs/version-7.x/_static/env-vars/activitylog_configvars.md
new file mode 100644
index 000000000..22d45b0b7
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/activitylog_configvars.md
@@ -0,0 +1,42 @@
+## Environment variables for the **activitylog** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`ACTIVITYLOG_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`ACTIVITYLOG_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9197`|
+|`ACTIVITYLOG_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`ACTIVITYLOG_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`ACTIVITYLOG_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`OC_EVENTS_ENDPOINT`| 1.0.0 |string|`The address of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture.`|`127.0.0.1:9233`|
+|`OC_EVENTS_CLUSTER`| 1.0.0 |string|`The clusterID of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture. Mandatory when using NATS as event system.`|`opencloud-cluster`|
+|`OC_INSECURE`<br/>`OC_EVENTS_TLS_INSECURE`| 1.0.0 |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_EVENTS_TLS_ROOT_CA_CERTIFICATE`| 1.0.0 |string|`The root CA certificate used to validate the server's TLS certificate. If provided NOTIFICATIONS_EVENTS_TLS_INSECURE will be seen as false.`|``|
+|`OC_EVENTS_ENABLE_TLS`| 1.0.0 |bool|`Enable TLS for the connection to the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|`false`|
+|`OC_EVENTS_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_EVENTS_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_PERSISTENT_STORE`<br/>`ACTIVITYLOG_STORE`| 1.0.0 |string|`The type of the store. Supported values are: 'memory', 'nats-js-kv', 'redis-sentinel', 'noop'. See the text description for details.`|`nats-js-kv`|
+|`OC_PERSISTENT_STORE_NODES`<br/>`ACTIVITYLOG_STORE_NODES`| 1.0.0 |[]string|`A list of nodes to access the configured store. This has no effect when 'memory' store is configured. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details.`|`[127.0.0.1:9233]`|
+|`ACTIVITYLOG_STORE_DATABASE`| 1.0.0 |string|`The database name the configured store should use.`|`activitylog`|
+|`OC_PERSISTENT_STORE_TTL`<br/>`ACTIVITYLOG_STORE_TTL`| 1.0.0 |Duration|`Time to live for events in the store. See the Environment Variable Types description for more details.`|`0s`|
+|`OC_PERSISTENT_STORE_AUTH_USERNAME`<br/>`ACTIVITYLOG_STORE_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_PERSISTENT_STORE_AUTH_PASSWORD`<br/>`ACTIVITYLOG_STORE_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_PERSISTENT_STORE_ENABLE_TLS`<br/>`ACTIVITYLOG_STORE_ENABLE_TLS`| next |bool|`Enable TLS for the connection to the store. Only applies when store type 'nats-js-kv' is configured.`|`false`|
+|`OC_INSECURE`<br/>`OC_PERSISTENT_STORE_TLS_INSECURE`<br/>`ACTIVITYLOG_STORE_TLS_INSECURE`| next |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_PERSISTENT_STORE_TLS_ROOT_CA_CERTIFICATE`<br/>`ACTIVITYLOG_STORE_TLS_ROOT_CA_CERTIFICATE`| next |string|`The root CA certificate used to validate the server's TLS certificate. If provided ACTIVITYLOG_STORE_TLS_INSECURE will be seen as false.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`CS3 gateway used to look up user metadata`|`eu.opencloud.api.gateway`|
+|`ACTIVITYLOG_HTTP_ADDR`| 1.0.0 |string|`The bind address of the HTTP service.`|`127.0.0.1:9195`|
+|`ACTIVITYLOG_HTTP_ROOT`| 1.0.0 |string|`Subdirectory that serves as the root for this HTTP service.`|`/`|
+|`OC_CORS_ALLOW_ORIGINS`<br/>`ACTIVITYLOG_CORS_ALLOW_ORIGINS`| 1.0.0 |[]string|`A list of allowed CORS origins. See following chapter for more details: *Access-Control-Allow-Origin* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin. See the Environment Variable Types description for more details.`|`[*]`|
+|`OC_CORS_ALLOW_METHODS`<br/>`ACTIVITYLOG_CORS_ALLOW_METHODS`| 1.0.0 |[]string|`A list of allowed CORS methods. See following chapter for more details: *Access-Control-Request-Method* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Method. See the Environment Variable Types description for more details.`|`[GET]`|
+|`OC_CORS_ALLOW_HEADERS`<br/>`ACTIVITYLOG_CORS_ALLOW_HEADERS`| 1.0.0 |[]string|`A list of allowed CORS headers. See following chapter for more details: *Access-Control-Request-Headers* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Headers. See the Environment Variable Types description for more details.`|`[Authorization Origin Content-Type Accept X-Requested-With X-Request-Id Ocs-Apirequest]`|
+|`OC_CORS_ALLOW_CREDENTIALS`<br/>`ACTIVITYLOG_CORS_ALLOW_CREDENTIALS`| 1.0.0 |bool|`Allow credentials for CORS.See following chapter for more details: *Access-Control-Allow-Credentials* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Credentials.`|`true`|
+|`OC_HTTP_TLS_ENABLED`| 1.0.0 |bool|`Activates TLS for the http based services using the server certifcate and key configured via OC_HTTP_TLS_CERTIFICATE and OC_HTTP_TLS_KEY. If OC_HTTP_TLS_CERTIFICATE is not set a temporary server certificate is generated - to be used with PROXY_INSECURE_BACKEND=true.`|`false`|
+|`OC_HTTP_TLS_CERTIFICATE`| 1.0.0 |string|`Path/File name of the TLS server certificate (in PEM format) for the http services.`|``|
+|`OC_HTTP_TLS_KEY`| 1.0.0 |string|`Path/File name for the TLS certificate key (in PEM format) for the server certificate to use for the http services.`|``|
+|`OC_JWT_SECRET`<br/>`ACTIVITYLOG_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`OC_TRANSLATION_PATH`<br/>`ACTIVITYLOG_TRANSLATION_PATH`| 1.0.0 |string|`(optional) Set this to a path with custom translations to overwrite the builtin translations. Note that file and folder naming rules apply, see the documentation for more details.`|``|
+|`OC_DEFAULT_LANGUAGE`| 1.0.0 |string|`The default language used by services and the WebUI. If not defined, English will be used as default. See the documentation for more details.`|`en`|
+|`OC_SERVICE_ACCOUNT_ID`<br/>`ACTIVITYLOG_SERVICE_ACCOUNT_ID`| 1.0.0 |string|`The ID of the service account the service should use. See the 'auth-service' service description for more details.`|``|
+|`OC_SERVICE_ACCOUNT_SECRET`<br/>`ACTIVITYLOG_SERVICE_ACCOUNT_SECRET`| 1.0.0 |string|`The service account secret.`|``|
+|`ACTIVITYLOG_WRITE_BUFFER_DURATION`| 4.0.0 |Duration|`The duration to wait before flushing the write buffer. This is used to reduce the number of writes to the store.`|`10s`|
+|`ACTIVITYLOG_MAX_ACTIVITIES`| 4.0.0 |int|`The maximum number of activities to keep in the store per resource. If the number of activities exceeds this value, the oldest activities will be removed.`|`6000`|
diff --git a/versioned_docs/version-7.x/_static/env-vars/activitylog_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/activitylog_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/activitylog_readme.md b/versioned_docs/version-7.x/_static/env-vars/activitylog_readme.md
new file mode 100755
index 000000000..ef0a0cd83
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/activitylog_readme.md
@@ -0,0 +1,54 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The `activitylog` service is responsible for storing events (activities) per resource.
+
+
+## Table of Contents
+
+* [The Log Service Ecosystem](#the-log-service-ecosystem)
+* [Activitylog Store](#activitylog-store)
+* [Translations](#translations)
+  * [Translation Rules](#translation-rules)
+* [Default Language](#default-language)
+
+## The Log Service Ecosystem
+
+Log services like the `activitylog`, `userlog`, `clientlog` and `sse` are responsible for composing notifications for a specific audience.
+  -   The `userlog` service translates and adjusts messages to be human readable.
+  -   The `clientlog` service composes machine readable messages, so clients can act without the need to query the server.
+  -   The `sse` service is only responsible for sending these messages. It does not care about their form or language.
+  -   The `activitylog` service stores events per resource. These can be retrieved to show item activities
+
+## Activitylog Store
+
+The `activitylog` stores activities for each resource. It works in conjunction with the `eventhistory` service to keep the data it needs to store to a minimum.
+
+## Translations
+
+The `activitylog` service has embedded translations sourced via transifex to provide a basic set of translated languages. These embedded translations are available for all deployment scenarios. In addition, the service supports custom translations, though it is currently not possible to just add custom translations to embedded ones. If custom translations are configured, the embedded ones are not used. To configure custom translations, the `ACTIVITYLOG_TRANSLATION_PATH` environment variable needs to point to a base folder that will contain the translation files. This path must be available from all instances of the activitylog service, a shared storage is recommended. Translation files must be of type  [.po](https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html#PO-Files) or [.mo](https://www.gnu.org/software/gettext/manual/html_node/Binaries.html). For each language, the filename needs to be `activitylog.po` (or `activitylog.mo`) and stored in a folder structure defining the language code. In general the path/name pattern for a translation file needs to be:
+
+```text
+{ACTIVITYLOG_TRANSLATION_PATH}/{language-code}/LC_MESSAGES/activitylog.po
+```
+
+The language code pattern is composed of `language[_territory]` where  `language` is the base language and `_territory` is optional and defines a country.
+
+For example, for the language `de`, one needs to place the corresponding translation files to `{ACTIVITYLOG_TRANSLATION_PATH}/de_DE/LC_MESSAGES/activitylog.po`.
+
+<!-- also see the notifications readme -->
+
+Important: For the time being, the embedded OpenCloud Web frontend only supports the main language code but does not handle any territory. When strings are available in the language code `language_territory`, the web frontend does not see it as it only requests `language`. In consequence, any translations made must exist in the requested `language` to avoid a fallback to the default.
+
+### Translation Rules
+
+*   If a requested language code is not available, the service tries to fall back to the base language if available. For example, if the requested language-code `de_DE` is not available, the service tries to fall back to translations in the `de` folder.
+*   If the base language `de` is also not available, the service falls back to the system's default English (`en`),
+which is the source of the texts provided by the code.
+
+## Default Language
+
+The default language can be defined via the `OC_DEFAULT_LANGUAGE` environment variable. See the `settings` service for a detailed description.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/antivirus.yaml b/versioned_docs/version-7.x/_static/env-vars/antivirus.yaml
new file mode 100644
index 000000000..28b354ee1
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/antivirus.yaml
@@ -0,0 +1,31 @@
+# Autogenerated
+# Filename: antivirus.yaml
+
+file: ""
+loglevel: error
+debug:
+  addr: 127.0.0.1:9277
+  token: ""
+  pprof: false
+  zpages: false
+infected-file-handling: delete
+events:
+  endpoint: 127.0.0.1:9233
+  cluster: opencloud-cluster
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+  enable_tls: false
+  username: ""
+  password: ""
+workers: 10
+scanner:
+  type: clamav
+  clamav:
+    socket: /run/clamav/clamd.ctl
+    scan_timeout: 5m0s
+  icap:
+    scan_timeout: 5m0s
+    url: icap://127.0.0.1:1344
+    service: avscan
+max-scan-size: 100MB
+max-scan-size-mode: partial
diff --git a/versioned_docs/version-7.x/_static/env-vars/antivirus_configvars.md b/versioned_docs/version-7.x/_static/env-vars/antivirus_configvars.md
new file mode 100644
index 000000000..7bebe2c2a
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/antivirus_configvars.md
@@ -0,0 +1,27 @@
+## Environment variables for the **antivirus** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`ANTIVIRUS_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`ANTIVIRUS_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9277`|
+|`ANTIVIRUS_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`ANTIVIRUS_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`ANTIVIRUS_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`ANTIVIRUS_INFECTED_FILE_HANDLING`| 1.0.0 |string|`Defines the behaviour when a virus has been found. Supported options are: 'delete', 'continue' and 'abort '. Delete will delete the file. Continue will mark the file as infected but continues further processing. Abort will keep the file in the uploads folder for further admin inspection and will not move it to its final destination.`|`delete`|
+|`OC_EVENTS_ENDPOINT`<br/>`ANTIVIRUS_EVENTS_ENDPOINT`| 1.0.0 |string|`The address of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture.`|`127.0.0.1:9233`|
+|`OC_EVENTS_CLUSTER`<br/>`ANTIVIRUS_EVENTS_CLUSTER`| 1.0.0 |string|`The clusterID of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture. Mandatory when using NATS as event system.`|`opencloud-cluster`|
+|`OC_INSECURE`<br/>`OC_EVENTS_TLS_INSECURE`<br/>`ANTIVIRUS_EVENTS_TLS_INSECURE`| 1.0.0 |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_EVENTS_TLS_ROOT_CA_CERTIFICATE`<br/>`ANTIVIRUS_EVENTS_TLS_ROOT_CA_CERTIFICATE`| 1.0.0 |string|`The root CA certificate used to validate the server's TLS certificate. If provided ANTIVIRUS_EVENTS_TLS_INSECURE will be seen as false.`|``|
+|`OC_EVENTS_ENABLE_TLS`<br/>`ANTIVIRUS_EVENTS_ENABLE_TLS`| 1.0.0 |bool|`Enable TLS for the connection to the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|`false`|
+|`OC_EVENTS_AUTH_USERNAME`<br/>`ANTIVIRUS_EVENTS_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_EVENTS_AUTH_PASSWORD`<br/>`ANTIVIRUS_EVENTS_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`ANTIVIRUS_WORKERS`| 1.0.0 |int|`The number of concurrent go routines that fetch events from the event queue.`|`10`|
+|`ANTIVIRUS_SCANNER_TYPE`| 1.0.0 |ScannerType|`The antivirus scanner to use. Supported values are 'clamav' and 'icap'.`|`clamav`|
+|`ANTIVIRUS_CLAMAV_SOCKET`| 1.0.0 |string|`The socket clamav is running on. Note the default value is an example which needs adaption according your OS.`|`/run/clamav/clamd.ctl`|
+|`ANTIVIRUS_CLAMAV_SCAN_TIMEOUT`| 2.1.0 |Duration|`Scan timeout for the ClamAV client. Defaults to '5m' (5 minutes). See the Environment Variable Types description for more details.`|`5m0s`|
+|`ANTIVIRUS_ICAP_SCAN_TIMEOUT`| 1.0.0 |Duration|`Scan timeout for the ICAP client. Defaults to '5m' (5 minutes). See the Environment Variable Types description for more details.`|`5m0s`|
+|`ANTIVIRUS_ICAP_URL`| 1.0.0 |string|`URL of the ICAP server.`|`icap://127.0.0.1:1344`|
+|`ANTIVIRUS_ICAP_SERVICE`| 1.0.0 |string|`The name of the ICAP service.`|`avscan`|
+|`ANTIVIRUS_MAX_SCAN_SIZE`| 1.0.0 |string|`The maximum scan size the virus scanner can handle.0 means unlimited. Usable common abbreviations: [KB, KiB, MB, MiB, GB, GiB, TB, TiB, PB, PiB, EB, EiB], example: 2GB.`|`100MB`|
+|`ANTIVIRUS_MAX_SCAN_SIZE_MODE`| 2.1.0 |MaxScanSizeMode|`Defines the mode of handling files that exceed the maximum scan size. Supported options are: 'skip', which skips files that are bigger than the max scan size, and 'truncate' (default), which only uses the file up to the max size.`|`partial`|
+|`ANTIVIRUS_DEBUG_SCAN_OUTCOME`| 1.0.0 |string|`A predefined outcome for virus scanning, FOR DEBUG PURPOSES ONLY! (example values: 'found,infected')`|``|
diff --git a/versioned_docs/version-7.x/_static/env-vars/antivirus_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/antivirus_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/antivirus_readme.md b/versioned_docs/version-7.x/_static/env-vars/antivirus_readme.md
new file mode 100755
index 000000000..82dcfb8fb
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/antivirus_readme.md
@@ -0,0 +1,99 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The `antivirus` service is responsible for scanning files for viruses.
+
+
+## Table of Contents
+
+* [Memory Considerations](#memory-considerations)
+* [Configuration](#configuration)
+  * [Antivirus Scanner Type](#antivirus-scanner-type)
+  * [Maximum Scan Size](#maximum-scan-size)
+  * [Antivirus Workers](#antivirus-workers)
+  * [Infected File Handling](#infected-file-handling)
+  * [Scanner Inaccessibility](#scanner-inaccessibility)
+* [Operation Modes](#operation-modes)
+  * [Postprocessing](#postprocessing)
+  * [Scaling in Kubernetes](#scaling-in-kubernetes)
+
+## Memory Considerations
+
+The antivirus service can consume considerable amounts of memory.
+This is relevant to provide or define sufficient memory for the deployment selected.
+To avoid out of memory (OOM) situations, the following equation gives a rough overview based on experiences made.
+The memory calculation comes without any guarantee, is intended as overview only and subject of change.
+
+`memory limit` = `max file size` x `workers` x `factor 8 - 14`
+
+With:
+`ANTIVIRUS_WORKERS` == 1
+```plaintext
+ 50MB file --> factor 14   --> 700MB memory
+844MB file --> factor  8,3 -->   7GB memory
+```
+
+## Configuration
+
+### Antivirus Scanner Type
+
+The antivirus service currently supports [ICAP](https://tools.ietf.org/html/rfc3507) and [ClamAV](http://www.clamav.net/index.html) as antivirus scanners.
+The `ANTIVIRUS_SCANNER_TYPE` environment variable is used to select the scanner.
+The detailed configuration for each scanner heavily depends on the scanner type selected.
+See the environment variables for more details.
+
+  -   For `icap`, only scanners using the `X-Infection-Found` header are currently supported.
+  -   For `clamav` only local sockets can currently be configured.
+
+### Maximum Scan Size
+
+Several factors can make it necessary to limit the maximum filesize the antivirus service uses for scanning.
+Use the `ANTIVIRUS_MAX_SCAN_SIZE` environment variable to scan only a given number of bytes,
+or to skip the whole resource.
+
+Even if it is recommended to scan the whole file, several factors like scanner type and version,
+bandwidth, performance issues, etc. might make a limit necessary.
+
+In such cases, the antivirus max scan size mode can be handy, the following modes are available:
+
+  -   `partial`: The file is scanned up to the given size. The rest of the file is not scanned. This is the default mode `ANTIVIRUS_MAX_SCAN_SIZE_MODE=partial`
+  -   `skip`: The file is skipped and not scanned. `ANTIVIRUS_MAX_SCAN_SIZE_MODE=skip`
+
+**IMPORTANT**
+> Streaming of files to the virus scan service still [needs to be implemented](https://github.com/owncloud/ocis/issues/6803).
+> To prevent OOM errors `ANTIVIRUS_MAX_SCAN_SIZE` needs to be set lower than available ram and or the maximum file size that can be scanned by the virus scanner.
+
+### Antivirus Workers
+
+The number of concurrent scans can be increased by setting `ANTIVIRUS_WORKERS`. Be aware that this will also increase memory usage.
+
+### Infected File Handling
+
+The antivirus service allows three different ways of handling infected files. Those can be set via the `ANTIVIRUS_INFECTED_FILE_HANDLING` environment variable:
+
+  -   `delete`: (default): Infected files will be deleted immediately, further postprocessing is cancelled.
+  -   `abort`:  (advanced option): Infected files will be kept, further postprocessing is cancelled. Files can be manually retrieved and inspected by an admin. To identify the file for further investigation, the antivirus service logs the abort/infected state including the file ID. The file is located in the `storage/users/uploads` folder of the OpenCloud data directory and persists until it is manually deleted by the admin via the [Manage Unfinished Uploads](https://github.com/opencloud-eu/opencloud/tree/main/services/storage-users#manage-unfinished-uploads) command.
+  -   `continue`:  (not recommended): Infected files will be marked via metadata as infected, but postprocessing continues normally. Note: Infected Files are moved to their final destination and therefore not prevented from download, which includes the risk of spreading viruses.
+
+In all cases, a log entry is added declaring the infection and handling method and a notification via the `userlog` service sent.
+
+### Scanner Inaccessibility
+
+In case a scanner is not accessible by the antivirus service like a network outage, service outage or hardware outage, the antivirus service uses the `abort` case for further processing, independent of the actual setting made. In any case, an error is logged noting the inaccessibility of the scanner used.
+
+## Operation Modes
+
+The antivirus service can scan files during `postprocessing`. `on demand` scanning is currently not available and might be added in a future release.
+
+### Postprocessing
+
+The antivirus service will scan files during postprocessing. It listens for a postprocessing step called `virusscan`. This step can be added in the environment variable `POSTPROCESSING_STEPS`. Read the documentation of the [postprocessing service](https://github.com/opencloud-eu/opencloud/tree/main/services/postprocessing) for more details.
+
+The number of concurrent scans can be increased by setting `ANTIVIRUS_WORKERS`, but be aware that this will also increase the memory usage.
+
+### Scaling in Kubernetes
+
+In kubernetes, `ANTIVIRUS_WORKERS` and `ANTIVIRUS_MAX_SCAN_SIZE` can be used to trigger the horizontal pod autoscaler by requesting a memory size that is below `ANTIVIRUS_MAX_SCAN_SIZE`. Keep in mind that `ANTIVIRUS_MAX_SCAN_SIZE` amount of memory might be held by `ANTIVIRUS_WORKERS` number of go routines.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/app-provider.yaml b/versioned_docs/version-7.x/_static/env-vars/app-provider.yaml
new file mode 100644
index 000000000..917bf3ac6
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/app-provider.yaml
@@ -0,0 +1,36 @@
+# Autogenerated
+# Filename: app-provider.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9165
+  token: ""
+  pprof: false
+  zpages: false
+grpc:
+  addr: 127.0.0.1:9164
+  tls: null
+  protocol: tcp
+token_manager:
+  jwt_secret: ""
+reva:
+  address: eu.opencloud.api.gateway
+  tls:
+    mode: ""
+    cacert: ""
+external_addr: eu.opencloud.api.app-provider
+driver: ""
+drivers:
+  wopi:
+    app_api_key: ""
+    app_desktop_only: false
+    app_icon_uri: ""
+    app_internal_url: ""
+    app_name: ""
+    app_url: ""
+    app_disable_chat: false
+    insecure: false
+    wopi_server_iop_secret: ""
+    wopi_server_external_url: ""
+    wopi_folder_url_base_url: https://localhost:9200/
+    wopi_folder_url_path_template: /f/{{.ResourceID}}
diff --git a/versioned_docs/version-7.x/_static/env-vars/app-provider_configvars.md b/versioned_docs/version-7.x/_static/env-vars/app-provider_configvars.md
new file mode 100644
index 000000000..371118985
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/app-provider_configvars.md
@@ -0,0 +1,30 @@
+## Environment variables for the **app-provider** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`APP_PROVIDER_SERVICE_NAME`| 1.0.0 |string|`The name of the service. This needs to be changed when using more than one app provider. Each app provider configured needs to be identified by a unique service name. Possible examples are: 'app-provider-collabora', 'app-provider-onlyoffice', 'app-provider-office365'.`|`app-provider`|
+|`OC_LOG_LEVEL`<br/>`APP_PROVIDER_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`APP_PROVIDER_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9165`|
+|`APP_PROVIDER_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint`|``|
+|`APP_PROVIDER_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling`|`false`|
+|`APP_PROVIDER_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can  be used for collecting and viewing traces in-memory.`|`false`|
+|`APP_PROVIDER_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9164`|
+|`OC_GRPC_PROTOCOL`<br/>`APP_PROVIDER_GRPC_PROTOCOL`| 1.0.0 |string|`The transport protocol of the GPRC service.`|`tcp`|
+|`OC_JWT_SECRET`<br/>`APP_PROVIDER_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`The CS3 gateway endpoint.`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
+|`APP_PROVIDER_EXTERNAL_ADDR`| 1.0.0 |string|`Address of the app provider, where the GATEWAY service can reach it.`|`eu.opencloud.api.app-provider`|
+|`APP_PROVIDER_DRIVER`| 1.0.0 |string|`Driver, the APP PROVIDER services uses. Only 'wopi' is supported as of now.`|``|
+|`APP_PROVIDER_WOPI_APP_API_KEY`| 1.0.0 |string|`API key for the wopi app.`|``|
+|`APP_PROVIDER_WOPI_APP_DESKTOP_ONLY`| 1.0.0 |bool|`Offer this app only on desktop.`|`false`|
+|`APP_PROVIDER_WOPI_APP_ICON_URI`| 1.0.0 |string|`URI to an app icon to be used by clients.`|``|
+|`APP_PROVIDER_WOPI_APP_INTERNAL_URL`| 1.0.0 |string|`Internal URL to the app, like in your DMZ.`|``|
+|`APP_PROVIDER_WOPI_APP_NAME`| 1.0.0 |string|`Human readable app name.`|``|
+|`APP_PROVIDER_WOPI_APP_URL`| 1.0.0 |string|`URL for end users to access the app.`|``|
+|`APP_PROVIDER_WOPI_DISABLE_CHAT`<br/>`OC_WOPI_DISABLE_CHAT`| 1.0.0 |bool|`Disable the chat functionality of the office app.`|`false`|
+|`APP_PROVIDER_WOPI_INSECURE`| 1.0.0 |bool|`Disable TLS certificate validation for requests to the WOPI server and the web office application. Do not set this in production environments.`|`false`|
+|`APP_PROVIDER_WOPI_WOPI_SERVER_IOP_SECRET`| 1.0.0 |string|`Shared secret of the CS3org WOPI server.`|``|
+|`APP_PROVIDER_WOPI_WOPI_SERVER_EXTERNAL_URL`| 1.0.0 |string|`External url of the CS3org WOPI server.`|``|
+|`OC_URL`<br/>`APP_PROVIDER_WOPI_FOLDER_URL_BASE_URL`| 1.0.0 |string|`Base url to navigate back from the app to the containing folder in the file list.`|`https://localhost:9200/`|
+|`APP_PROVIDER_WOPI_FOLDER_URL_PATH_TEMPLATE`| 1.0.0 |string|`Path template to navigate back from the app to the containing folder in the file list. Supported template variables are {{.ResourceInfo.ResourceID}}, {{.ResourceInfo.Mtime.Seconds}}, {{.ResourceInfo.Name}}, {{.ResourceInfo.Path}}, {{.ResourceInfo.Type}}, {{.ResourceInfo.Id.SpaceId}}, {{.ResourceInfo.Id.StorageId}}, {{.ResourceInfo.Id.OpaqueId}}, {{.ResourceInfo.MimeType}}`|`/f/{{.ResourceID}}`|
diff --git a/versioned_docs/version-7.x/_static/env-vars/app-provider_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/app-provider_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/app-provider_readme.md b/versioned_docs/version-7.x/_static/env-vars/app-provider_readme.md
new file mode 100755
index 000000000..323ba0304
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/app-provider_readme.md
@@ -0,0 +1,31 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The `app-provider` service provides the CS3 App Provider API for OpenCloud. It is responsible for managing and serving applications that can open files based on their MIME types.
+
+The service works in conjunction with the `app-registry` service, which maintains the registry of available applications and their supported MIME types. When a client requests to open a file with a specific application, the `app-provider` service handles the request and coordinates with the application to provide the appropriate interface.
+
+
+## Table of Contents
+
+* [Integration](#integration)
+* [Configuration](#configuration)
+* [Scalability](#scalability)
+
+## Integration
+
+The `app-provider` service integrates with:
+- `app-registry` - For discovering which applications are available for specific MIME types
+- `frontend` - The frontend service forwards app provider requests (default endpoint `/app`) to this service
+
+## Configuration
+
+The service can be configured via environment variables. Key configuration options include:
+- `APP_PROVIDER_EXTERNAL_ADDR` - External address where the gateway service can reach the app provider
+
+## Scalability
+
+The app-provider service can be scaled horizontally as it primarily acts as a coordinator between applications and the OpenCloud backend services.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/app-registry.yaml b/versioned_docs/version-7.x/_static/env-vars/app-registry.yaml
new file mode 100644
index 000000000..99935923b
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/app-registry.yaml
@@ -0,0 +1,106 @@
+# Autogenerated
+# Filename: app-registry.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9243
+  token: ""
+  pprof: false
+  zpages: false
+grpc:
+  addr: 127.0.0.1:9242
+  tls: null
+  protocol: tcp
+token_manager:
+  jwt_secret: ""
+reva:
+  address: eu.opencloud.api.gateway
+  tls:
+    mode: ""
+    cacert: ""
+app_registry:
+  mimetypes:
+  - mime_type: application/pdf
+    extension: pdf
+    name: PDF
+    description: PDF document
+    icon: ""
+    default_app: ""
+    allow_creation: false
+  - mime_type: application/vnd.oasis.opendocument.text
+    extension: odt
+    name: Document
+    description: OpenDocument text document
+    icon: ""
+    default_app: ""
+    allow_creation: true
+  - mime_type: application/vnd.oasis.opendocument.spreadsheet
+    extension: ods
+    name: Spreadsheet
+    description: OpenDocument spreadsheet document
+    icon: ""
+    default_app: ""
+    allow_creation: true
+  - mime_type: application/vnd.oasis.opendocument.presentation
+    extension: odp
+    name: Presentation
+    description: OpenDocument presentation document
+    icon: ""
+    default_app: ""
+    allow_creation: true
+  - mime_type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
+    extension: docx
+    name: Microsoft Word
+    description: Microsoft Word document
+    icon: ""
+    default_app: ""
+    allow_creation: false
+  - mime_type: application/vnd.openxmlformats-officedocument.wordprocessingml.form
+    extension: docxf
+    name: Form Document
+    description: Form Document
+    icon: ""
+    default_app: ""
+    allow_creation: false
+  - mime_type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
+    extension: xlsx
+    name: Microsoft Excel
+    description: Microsoft Excel document
+    icon: ""
+    default_app: ""
+    allow_creation: false
+  - mime_type: application/vnd.openxmlformats-officedocument.presentationml.presentation
+    extension: pptx
+    name: Microsoft PowerPoint
+    description: Microsoft PowerPoint document
+    icon: ""
+    default_app: ""
+    allow_creation: false
+  - mime_type: application/vnd.jupyter
+    extension: ipynb
+    name: Jupyter Notebook
+    description: Jupyter Notebook
+    icon: ""
+    default_app: ""
+    allow_creation: false
+  - mime_type: text/markdown
+    extension: md
+    name: Markdown file
+    description: Markdown file
+    icon: ""
+    default_app: ""
+    allow_creation: true
+  - mime_type: application/compressed-markdown
+    extension: zmd
+    name: Compressed markdown file
+    description: Compressed markdown file
+    icon: ""
+    default_app: ""
+    allow_creation: false
+  - mime_type: application/vnd.geogebra.slides
+    extension: ggs
+    name: GeoGebra Slides
+    description: GeoGebra Slides
+    icon: ""
+    default_app: ""
+    allow_creation: false
diff --git a/versioned_docs/version-7.x/_static/env-vars/app-registry_configvars.md b/versioned_docs/version-7.x/_static/env-vars/app-registry_configvars.md
new file mode 100644
index 000000000..16f467391
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/app-registry_configvars.md
@@ -0,0 +1,15 @@
+## Environment variables for the **app-registry** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`APP_REGISTRY_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`APP_REGISTRY_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9243`|
+|`APP_REGISTRY_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`APP_REGISTRY_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`APP_REGISTRY_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`APP_REGISTRY_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9242`|
+|`OC_GRPC_PROTOCOL`<br/>`APP_REGISTRY_GRPC_PROTOCOL`| 1.0.0 |string|`The transport protocol of the GRPC service.`|`tcp`|
+|`OC_JWT_SECRET`<br/>`APP_REGISTRY_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`The CS3 gateway endpoint.`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
diff --git a/versioned_docs/version-7.x/_static/env-vars/app-registry_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/app-registry_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/app-registry_readme.md b/versioned_docs/version-7.x/_static/env-vars/app-registry_readme.md
new file mode 100755
index 000000000..5a3886a38
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/app-registry_readme.md
@@ -0,0 +1,463 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The `app-registry` service is the single point where all apps register themselves and their respective supported mime types.
+
+Administrators can set default applications on a per MIME type basis and also allow the creation of new files for certain MIME types. This per MIME type configuration also features a description, file extension option and an icon.
+
+
+## Table of Contents
+
+* [MIME Type Configuration / Creation Allow List](#mime-type-configuration--creation-allow-list)
+  * [MIME Type Configuration](#mime-type-configuration)
+* [Endpoint Access](#endpoint-access)
+  * [Listing available apps and mime types](#listing-available-apps-and-mime-types)
+  * [Open a File With OpenCloud Web](#open-a-file-with-opencloud-web)
+  * [Open a File With the App Provider](#open-a-file-with-the-app-provider)
+  * [Creating a File With the App Provider](#creating-a-file-with-the-app-provider)
+
+## MIME Type Configuration / Creation Allow List
+
+The apps will register their supported MIME types automatically, so that users can open supported files with them.
+
+Administrators can set default applications for each MIME type and also allow the creation of new files for certain mime types. This, per MIME type configuration, also features a description, file extension option and an icon.
+
+### MIME Type Configuration
+
+Modifing the MIME type config can only be achieved via a yaml configuration. Using environment variables is not possible. The following is a brief structure and a field description:
+
+**Structure**
+
+```yaml
+app_registry:
+  mimetypes:
+  - mime_type: application/vnd.oasis.opendocument.spreadsheet
+    extension: ods
+    name: OpenSpreadsheet
+    description: OpenDocument spreadsheet document
+    icon: https://some-website.test/opendocument-spreadsheet-icon.png
+    default_app: Collabora
+    allow_creation: true
+  - mime_type: ...
+```
+
+**Fields**
+
+* `mime_type`\
+The MIME type you want to configure.
+* `extension`\
+The file extension to be used for new files.
+* `name`\
+The name of the file / MIME type.
+* `description`\
+The human-readable description of the file / MIME type.
+* `icon`\
+The URL to an icon which should be used for that MIME type.
+* `default_app`\
+The name of the default app which opens this MIME type if the user doesn’t specify one.
+* `allow_creation`\
+Whether a user should be able to create new files of that MIME type (true or false).
+
+## Endpoint Access
+
+### Listing available apps and mime types
+
+Clients, for example OpenCloud Web, need to offer users the available apps to open files and mime types for new file creation. This information can be obtained from this endpoint.
+
+**Endpoint**: specified in the capabilities in `apps_url`, currently `/app/list`
+
+**Method**: HTTP GET
+
+**Authentication**: None
+
+**Request example**:
+
+```bash
+curl 'https://opencloud.test/app/list'
+```
+
+**Response example**:
+
+HTTP status code: 200
+
+```json
+{
+  "mime-types": [
+    {
+      "mime_type": "application/pdf",
+      "ext": "pdf",
+      "app_providers": [
+        {
+          "name": "OnlyOffice",
+          "icon": "https://some-website.test/onlyoffice-pdf-icon.png"
+        }
+      ],
+      "name": "PDF",
+      "description": "PDF document"
+    },
+    {
+      "mime_type": "application/vnd.oasis.opendocument.text",
+      "ext": "odt",
+      "app_providers": [
+        {
+          "name": "Collabora",
+          "icon": "https://some-website.test/collabora-odt-icon.png"
+        },
+        {
+          "name": "OnlyOffice",
+          "icon": "https://some-website.test/onlyoffice-odt-icon.png"
+        }
+      ],
+      "name": "OpenDocument",
+      "icon": "https://some-website.test/opendocument-text-icon.png",
+      "description": "OpenDocument text document",
+      "allow_creation": true,
+      "default_application": "Collabora"
+    },
+    {
+      "mime_type": "text/markdown",
+      "ext": "md",
+      "app_providers": [
+        {
+          "name": "CodiMD",
+          "icon": "https://some-website.test/codimd-md-icon.png"
+        }
+      ],
+      "name": "Markdown file",
+      "description": "Markdown file",
+      "allow_creation": true,
+      "default_application": "CodiMD"
+    },
+    {
+      "mime_type": "application/vnd.ms-word.document.macroenabled.12",
+      "app_providers": [
+        {
+          "name": "Collabora",
+          "icon": "https://some-website.test/collabora-word-icon.png"
+        },
+        {
+          "name": "OnlyOffice",
+          "icon": "https://some-website.test/onlyoffice-word-icon.png"
+        }
+      ]
+    },
+    {
+      "mime_type": "application/vnd.ms-powerpoint.template.macroenabled.12",
+      "app_providers": [
+        {
+          "name": "Collabora",
+          "icon": "https://some-website.test/collabora-powerpoint-icon.png"
+        }
+      ]
+    }
+  ]
+}
+```
+
+### Open a File With OpenCloud Web
+
+**Endpoint**: specified in the capabilities in `open_web_url`, currently `/app/open-with-web`
+
+**Method**: HTTP POST
+
+**Authentication** (one of them):
+
+- `Authorization` header with OIDC Bearer token for authenticated users or basic auth credentials (if enabled in OpenCloud)
+- `X-Access-Token` header with a REVA token for authenticated users
+
+**Query parameters**:
+
+- `file_id` (mandatory): id of the file to be opened
+- `app_name` (optional)
+  - default (not given): default app for mime type
+  - possible values depend on the app providers for a mimetype from the `/app/open` endpoint
+
+**Request examples**:
+
+```bash
+curl -X POST 'https://opencloud.test/app/open-with-web?file_id=ZmlsZTppZAo='
+
+curl -X POST 'https://opencloud.test/app/open-with-web?file_id=ZmlsZTppZAo=&app_name=Collabora'
+```
+
+**Response examples**:
+
+The URI from the response JSON is intended to be opened with a GET request in a browser. If the user has not yet a session in the browser, a login flow is handled by OpenCloud Web.
+
+HTTP status code: 200
+
+```json
+{
+  "uri": "https://....."
+}
+```
+
+**Example responses (error case)**:
+
+See error cases for [Open a file with the app provider](#open-a-file-with-the-app-provider)
+
+### Open a File With the App Provider
+
+**Endpoint**: specified in the capabilities in `open_url`, currently `/app/open`
+
+**Method**: HTTP POST
+
+**Authentication** (one of them):
+
+- `Authorization` header with OIDC Bearer token for authenticated users or basic auth credentials (if enabled in OpenCloud)
+- `Public-Token` header with public link token for public links
+- `X-Access-Token` header with a REVA token for authenticated users
+
+**Query parameters**:
+
+- `file_id` (mandatory): id of the file to be opened
+- `app_name` (optional)
+  - default (not given): default app for mime type
+  - possible values depend on the app providers for a mimetype from the `/app/open` endpoint
+- `view_mode` (optional)
+  - default (not given): highest possible view mode, depending on the file permissions
+  - possible values:
+    - `write`: user can edit and download in the opening app
+    - `read`: user can view and download from the opening app
+    - `view`: user can view in the opening app (download is not possible)
+- `lang` (optional)
+  - default (not given): default language of the application (which might maybe use the browser language)
+  - possible value is any ISO 639-1 language code. Examples:
+    - de
+    - en
+    - es
+    - ...
+
+**Request examples**:
+
+```bash
+curl -X POST 'https://opencloud.test/app/open?file_id=ZmlsZTppZAo='
+
+curl -X POST 'https://opencloud.test/app/open?file_id=ZmlsZTppZAo=&lang=de'
+
+curl -X POST 'https://opencloud.test/app/open?file_id=ZmlsZTppZAo=&app_name=Collabora'
+
+curl -X POST 'https://opencloud.test/app/open?file_id=ZmlsZTppZAo=&view_mode=read'
+
+curl -X POST 'https://opencloud.test/app/open?file_id=ZmlsZTppZAo=&app_name=Collabora&view_mode=write'
+```
+
+**Response examples**:
+
+All apps are expected to be opened in an iframe and the response will give some parameters for that action.
+
+There are apps, which need to be opened in the iframe with a form post. The form post must include all form parameters included in the response. For these apps the response will look like this:
+
+HTTP status code: 200
+
+```json
+{
+  "app_url": "https://.....",
+  "method": "POST",
+  "form_parameters": {
+    "access_token": "eyJ0...",
+    "access_token_ttl": "1634300912000",
+    "arbitrary_param": "lorem-ipsum"
+  }
+}
+```
+
+There are apps, which need to be opened in the iframe with a GET request. The GET request must have set all headers included in the response. For these apps the response will look like this:
+
+HTTP status code: 200
+
+```json
+{
+  "app_url": "https://...",
+  "method": "GET",
+  "headers": {
+    "access_token": "eyJ0e...",
+    "access_token_ttl": "1634300912000",
+    "arbitrary_header": "lorem-ipsum"
+  }
+}
+```
+
+**Example responses (error case)**:
+
+- missing `file_id`
+
+  HTTP status code: 400
+
+  ```json
+  {
+    "code": "INVALID_PARAMETER",
+    "message": "missing file ID"
+  }
+  ```
+
+- wrong `view_mode`
+
+  HTTP status code: 400
+
+  ```json
+  {
+    "code": "INVALID_PARAMETER",
+    "message": "invalid view mode"
+  }
+  ```
+
+- unknown `app_name`
+
+  HTTP status code: 404
+
+  ```json
+  {
+    "code": "RESOURCE_NOT_FOUND",
+    "message": "error: not found: app 'Collabora' not found"
+  }
+  ```
+
+- wrong / invalid file id
+
+  HTTP status code: 400
+
+  ```json
+  {
+    "code": "INVALID_PARAMETER",
+    "message": "invalid file ID"
+  }
+  ```
+
+- file id does not point to a file
+
+  HTTP status code: 400
+
+  ```json
+  {
+    "code": "INVALID_PARAMETER",
+    "message": "the given file id does not point to a file"
+  }
+  ```
+
+- file does not exist / unauthorized to open the file
+
+  HTTP status code: 404
+
+  ```json
+  {
+    "code": "RESOURCE_NOT_FOUND",
+    "message": "file does not exist"
+  }
+  ```
+
+- invalid language code
+
+  HTTP status code: 400
+
+  ```json
+  {
+    "code": "INVALID_PARAMETER",
+    "message": "lang parameter does not contain a valid ISO 639-1 language code"
+  }
+  ```
+
+### Creating a File With the App Provider
+
+**Endpoint**: specified in the capabilities in `new_file_url`, currently `/app/new`
+
+**Method**: HTTP POST
+
+**Authentication** (one of them):
+
+- `Authorization` header with OIDC Bearer token for authenticated users or basic auth credentials (if enabled in OpenCloud)
+- `Public-Token` header with public link token for public links
+- `X-Access-Token` header with a REVA token for authenticated users
+
+**Query parameters**:
+
+- `parent_container_id` (mandatory): ID of the folder in which the file will be created
+- `filename` (mandatory): name of the new file
+- `template` (optional): not yet implemented
+
+**Request examples**:
+
+```bash
+curl -X POST 'https://opencloud.test/app/new?parent_container_id=c2lkOmNpZAo=&filename=test.odt'
+```
+
+**Response example**:
+
+You will receive a file id of the freshly created file, which you can use to open the file in an editor.
+
+```json
+{
+  "file_id": "ZmlsZTppZAo="
+}
+```
+
+**Example responses (error case)**:
+
+- missing `parent_container_id`
+
+  HTTP status code: 400
+
+  ```json
+  {
+    "code": "INVALID_PARAMETER",
+    "message": "missing parent container ID"
+  }
+  ```
+
+- missing `filename`
+
+  HTTP status code: 400
+
+  ```json
+  {
+    "code": "INVALID_PARAMETER",
+    "message": "missing filename"
+  }
+  ```
+
+- parent container not found
+
+  HTTP status code: 404
+
+  ```json
+  {
+    "code": "RESOURCE_NOT_FOUND",
+    "message": "the parent container is not accessible or does not exist"
+  }
+  ```
+
+- `parent_container_id` does not point to a container
+
+  HTTP status code: 400
+
+  ```json
+  {
+    "code": "INVALID_PARAMETER",
+    "message": "the parent container id does not point to a container"
+  }
+  ```
+
+- `filename` is invalid (e.g. includes a path segment)
+
+  HTTP status code: 400
+
+  ```json
+  {
+    "code": "INVALID_PARAMETER",
+    "message": "the filename must not contain a path segment"
+  }
+  ```
+
+- file already exists
+
+  HTTP status code: 403
+
+  ```json
+  {
+    "code": "RESOURCE_ALREADY_EXISTS",
+    "message": "the file already exists"
+  }
+  ```
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/audit.yaml b/versioned_docs/version-7.x/_static/env-vars/audit.yaml
new file mode 100644
index 000000000..1c6720df6
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/audit.yaml
@@ -0,0 +1,22 @@
+# Autogenerated
+# Filename: audit.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9229
+  token: ""
+  pprof: false
+  zpages: false
+events:
+  endpoint: 127.0.0.1:9233
+  cluster: opencloud-cluster
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+  enable_tls: false
+  username: ""
+  password: ""
+auditlog:
+  log_to_console: true
+  log_to_file: false
+  filepath: ""
+  format: json
diff --git a/versioned_docs/version-7.x/_static/env-vars/audit_configvars.md b/versioned_docs/version-7.x/_static/env-vars/audit_configvars.md
new file mode 100644
index 000000000..d49795b71
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/audit_configvars.md
@@ -0,0 +1,20 @@
+## Environment variables for the **audit** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`AUDIT_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`AUDIT_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9229`|
+|`AUDIT_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`AUDIT_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`AUDIT_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`OC_EVENTS_ENDPOINT`<br/>`AUDIT_EVENTS_ENDPOINT`| 1.0.0 |string|`The address of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture.`|`127.0.0.1:9233`|
+|`OC_EVENTS_CLUSTER`<br/>`AUDIT_EVENTS_CLUSTER`| 1.0.0 |string|`The clusterID of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture. Mandatory when using NATS as event system.`|`opencloud-cluster`|
+|`OC_INSECURE`<br/>`OC_EVENTS_TLS_INSECURE`<br/>`AUDIT_EVENTS_TLS_INSECURE`| 1.0.0 |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_EVENTS_TLS_ROOT_CA_CERTIFICATE`<br/>`AUDIT_EVENTS_TLS_ROOT_CA_CERTIFICATE`| 1.0.0 |string|`The root CA certificate used to validate the server's TLS certificate. If provided AUDIT_EVENTS_TLS_INSECURE will be seen as false.`|``|
+|`OC_EVENTS_ENABLE_TLS`<br/>`AUDIT_EVENTS_ENABLE_TLS`| 1.0.0 |bool|`Enable TLS for the connection to the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|`false`|
+|`OC_EVENTS_AUTH_USERNAME`<br/>`AUDIT_EVENTS_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_EVENTS_AUTH_PASSWORD`<br/>`AUDIT_EVENTS_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`AUDIT_LOG_TO_CONSOLE`| 1.0.0 |bool|`Logs to stdout if set to 'true'. Independent of the LOG_TO_FILE option.`|`true`|
+|`AUDIT_LOG_TO_FILE`| 1.0.0 |bool|`Logs to file if set to 'true'. Independent of the LOG_TO_CONSOLE option.`|`false`|
+|`AUDIT_FILEPATH`| 1.0.0 |string|`Filepath of the logfile. Mandatory if LOG_TO_FILE is set to 'true'.`|``|
+|`AUDIT_FORMAT`| 1.0.0 |string|`Log format. Supported values are '' (empty) and 'json'. Using 'json' is advised, '' (empty) renders the 'minimal' format. See the text description for more details.`|`json`|
diff --git a/versioned_docs/version-7.x/_static/env-vars/audit_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/audit_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/audit_readme.md b/versioned_docs/version-7.x/_static/env-vars/audit_readme.md
new file mode 100755
index 000000000..1d22d217a
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/audit_readme.md
@@ -0,0 +1,38 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The audit service logs all events of the system as an audit log. Per default, it will be logged to standard out, but can also be configured to a file output. Supported log formats are json or a minimal human-readable format.
+
+With audit logs, you are able to prove compliance with corporate guidelines as well as to enable reporting and auditing of operations. The audit service takes note of actions conducted by users and administrators.
+
+Example minimal format:
+```
+file_delete)
+   user 'user_id' trashed file 'item_id'
+file_trash_delete)
+   user 'user_id' removed file 'item_id' from trashbin
+```
+
+Example json:
+```
+{"RemoteAddr":"","User":"user_id","URL":"","Method":"","UserAgent":"","Time":"","App":"admin_audit","Message":"user 'user_id' trashed file 'item_id'","Action":"file_delete","CLI":false,"Level":1,"Path":"path","Owner":"user_id","FileID":"item_id"}
+{"RemoteAddr":"","User":"user_id","URL":"","Method":"","UserAgent":"","Time":"","App":"admin_audit","Message":"user 'user_id' removed file 'item_id' from trashbin","Action":"file_trash_delete","CLI":false,"Level":1,"Path":"path","Owner":"user_id","FileID":"item_id"}
+```
+
+The audit service is not started automatically when running as single binary started via `opencloud server` or when running as docker container and must be started and stopped manually on demand.
+
+The audit service logs:
+
+-   File system operations  
+(create/delete/move; including actions on the trash bin and versioning)
+-   User management operations  
+(creation/deletion of users)
+-   Sharing operations  
+(user/group sharing, sharing via link, changing permissions, calls to sharing API from clients)
+
+## Table of Contents
+
+
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/auth-app.yaml b/versioned_docs/version-7.x/_static/env-vars/auth-app.yaml
new file mode 100644
index 000000000..809240439
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/auth-app.yaml
@@ -0,0 +1,60 @@
+# Autogenerated
+# Filename: auth-app.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9245
+  token: ""
+  pprof: false
+  zpages: false
+grpc:
+  addr: 127.0.0.1:9246
+  tls: null
+  protocol: tcp
+http:
+  addr: 127.0.0.1:9247
+  root: /
+  cors:
+    allow_origins:
+    - '*'
+    allow_methods:
+    - GET
+    - POST
+    - DELETE
+    allow_headers:
+    - Authorization
+    - Origin
+    - Content-Type
+    - Accept
+    - X-Requested-With
+    - X-Request-Id
+    - Ocs-Apirequest
+    allow_credentials: true
+  tls:
+    enabled: false
+    cert: ""
+    key: ""
+grpc_client_tls: null
+token_manager:
+  jwt_secret: ""
+reva:
+  address: eu.opencloud.api.gateway
+  tls:
+    mode: ""
+    cacert: ""
+skip_user_groups_in_token: false
+machine_auth_api_key: ""
+allow_impersonation: false
+storage_driver: jsoncs3
+storage_drivers:
+  jsoncs3:
+    provider_addr: eu.opencloud.api.storage-system
+    system_user_id: ""
+    system_user_idp: internal
+    system_user_api_key: ""
+    password_generator: diceware
+    password_generator_options:
+      diceware:
+        number_of_words: 6
+      randon:
+        password_length: 0
diff --git a/versioned_docs/version-7.x/_static/env-vars/auth-app_configvars.md b/versioned_docs/version-7.x/_static/env-vars/auth-app_configvars.md
new file mode 100644
index 000000000..96115bf95
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/auth-app_configvars.md
@@ -0,0 +1,35 @@
+## Environment variables for the **auth-app** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`AUTH_APP_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`AUTH_APP_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9245`|
+|`AUTH_APP_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`AUTH_APP_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`AUTH_APP_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can  be used for collecting and viewing traces in-memory.`|`false`|
+|`AUTH_APP_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9246`|
+|`OC_GRPC_PROTOCOL`<br/>`AUTH_APP_GRPC_PROTOCOL`| 1.0.0 |string|`The transport protocol of the GRPC service.`|`tcp`|
+|`AUTH_APP_HTTP_ADDR`| 1.0.0 |string|`The bind address of the HTTP service.`|`127.0.0.1:9247`|
+|`AUTH_APP_HTTP_ROOT`| 1.0.0 |string|`Subdirectory that serves as the root for this HTTP service.`|`/`|
+|`OC_CORS_ALLOW_ORIGINS`<br/>`AUTH_APP_CORS_ALLOW_ORIGINS`| 1.0.0 |[]string|`A list of allowed CORS origins. See following chapter for more details: *Access-Control-Allow-Origin* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin. See the Environment Variable Types description for more details.`|`[*]`|
+|`OC_CORS_ALLOW_METHODS`<br/>`AUTH_APP_CORS_ALLOW_METHODS`| 1.0.0 |[]string|`A list of allowed CORS methods. See following chapter for more details: *Access-Control-Request-Method* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Method. See the Environment Variable Types description for more details.`|`[GET POST DELETE]`|
+|`OC_CORS_ALLOW_HEADERS`<br/>`AUTH_APP_CORS_ALLOW_HEADERS`| 1.0.0 |[]string|`A list of allowed CORS headers. See following chapter for more details: *Access-Control-Request-Headers* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Headers. See the Environment Variable Types description for more details.`|`[Authorization Origin Content-Type Accept X-Requested-With X-Request-Id Ocs-Apirequest]`|
+|`OC_CORS_ALLOW_CREDENTIALS`<br/>`AUTH_APP_CORS_ALLOW_CREDENTIALS`| 1.0.0 |bool|`Allow credentials for CORS.See following chapter for more details: *Access-Control-Allow-Credentials* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Credentials.`|`true`|
+|`OC_HTTP_TLS_ENABLED`| 1.0.0 |bool|`Activates TLS for the http based services using the server certifcate and key configured via OC_HTTP_TLS_CERTIFICATE and OC_HTTP_TLS_KEY. If OC_HTTP_TLS_CERTIFICATE is not set a temporary server certificate is generated - to be used with PROXY_INSECURE_BACKEND=true.`|`false`|
+|`OC_HTTP_TLS_CERTIFICATE`| 1.0.0 |string|`Path/File name of the TLS server certificate (in PEM format) for the http services.`|``|
+|`OC_HTTP_TLS_KEY`| 1.0.0 |string|`Path/File name for the TLS certificate key (in PEM format) for the server certificate to use for the http services.`|``|
+|`OC_JWT_SECRET`<br/>`AUTH_APP_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`The CS3 gateway endpoint.`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
+|`AUTH_APP_SKIP_USER_GROUPS_IN_TOKEN`| 1.0.0 |bool|`Disables the encoding of the user's group memberships in the access token. This reduces the token size, especially when users are members of a large number of groups.`|`false`|
+|`OC_MACHINE_AUTH_API_KEY`<br/>`AUTH_APP_MACHINE_AUTH_API_KEY`| 1.0.0 |string|`The machine auth API key used to validate internal requests necessary to access resources from other services.`|``|
+|`AUTH_APP_ENABLE_IMPERSONATION`| 1.0.0 |bool|`Allows admins to create app tokens for other users. Used for migration. Do NOT use in productive deployments.`|`false`|
+|`AUTH_APP_STORAGE_DRIVER`| 4.0.0 |string|`Driver to be used to persist the app tokes . Supported values are 'jsoncs3', 'json'.`|`jsoncs3`|
+|`AUTH_APP_JSONCS3_PROVIDER_ADDR`| 4.0.0 |string|`GRPC address of the STORAGE-SYSTEM service.`|`eu.opencloud.api.storage-system`|
+|`OC_SYSTEM_USER_ID`<br/>`AUTH_APP_JSONCS3_SYSTEM_USER_ID`| 4.0.0 |string|`ID of the OpenCloud STORAGE-SYSTEM system user. Admins need to set the ID for the STORAGE-SYSTEM system user in this config option which is then used to reference the user. Any reasonable long string is possible, preferably this would be an UUIDv4 format.`|``|
+|`OC_SYSTEM_USER_IDP`<br/>`AUTH_APP_JSONCS3_SYSTEM_USER_IDP`| 4.0.0 |string|`IDP of the OpenCloud STORAGE-SYSTEM system user.`|`internal`|
+|`OC_SYSTEM_USER_API_KEY`<br/>`AUTH_APP_JSONCS3_SYSTEM_USER_API_KEY`| 4.0.0 |string|`API key for the STORAGE-SYSTEM system user.`|``|
+|`AUTH_APP_JSONCS3_PASSWORD_GENERATOR`| 4.0.0 |string|`The password generator that should be used for generating app tokens. Supported values are: 'diceware' and 'random'.`|`diceware`|
+|`AUTH_APP_JSONCS3_DICEWARE_NUMBER_OF_WORDS`| 4.0.0 |int|`The number of words the generated passphrase will have.`|`6`|
+|`AUTH_APP_JSONCS3_RANDOM_PASSWORD_LENGTH`| 4.0.0 |int|`The number of charactors the generated passwords will have.`|`0`|
diff --git a/versioned_docs/version-7.x/_static/env-vars/auth-app_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/auth-app_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/auth-app_readme.md b/versioned_docs/version-7.x/_static/env-vars/auth-app_readme.md
new file mode 100755
index 000000000..6d75f889e
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/auth-app_readme.md
@@ -0,0 +1,154 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The auth-app service provides authentication for 3rd party apps unable to use
+OpenID Connect. The service is enabled by default and started automatically. It
+is possible to disable the service by setting:
+
+```bash
+OC_EXCLUDE_RUN_SERVICES=auth-app # deployment specific. Removes service from the list of automatically started services, use with single-binary deployments
+PROXY_ENABLE_APP_AUTH=false      # mandatory, disables app authentication. In case of a distributed environment, this envvar needs to be set in the proxy service.
+```
+
+
+## Table of Contents
+
+* [App Tokens](#app-tokens)
+* [Important Security Note](#important-security-note)
+* [Managing App Tokens](#managing-app-tokens)
+  * [Via API](#via-api)
+  * [Via Impersonation API](#via-impersonation-api)
+  * [Via CLI (developer only)](#via-cli-developer-only)
+* [Authenticating using App Tokens](#authenticating-using-app-tokens)
+
+## App Tokens
+
+App Tokens are password specifically generated to be used by 3rd party applications
+for authentication when accessing the OpenCloud API endpoints. To
+be able to use an app token, one must first create a token. There are different
+options of creating a token.
+
+## Important Security Note
+
+When using an external IDP for authentication, App Token are NOT invalidated
+when the user is disabled or locked in that external IDP. That means the user
+will still be able to use its existing App Tokens for authentication for as
+long as the App Tokes are valid.
+
+## Managing App Tokens
+
+### Via API
+
+Please note: This API is preliminary. In the future we will provide endpoints
+in the `graph` service for allowing the management of App Tokens.
+
+The `auth-app` service provides an API to create (POST), list (GET) and delete (DELETE) tokens at the `/auth-app/tokens` endpoint.
+
+* **Create a token**\
+  The POST request requires:
+  * A `expiry` key/value pair in the form of `expiry=<number><h|m|s>`\
+    Example: `expiry=72h`
+  ```bash
+  curl --request POST 'https://<your host:9200>/auth-app/tokens?expiry={value}' \
+       --header 'accept: application/json'
+  ```
+  Example output:
+  ```
+  {
+  "token": "3s2K7816M4vuSpd5",
+  "expiration_date": "2024-08-08T13:42:42.796888022+02:00",
+  "created_date": "2024-08-07T13:42:42+02:00",
+  "label": "Generated via API"
+  }
+  ```
+
+  Note, that this is the only time the app token will be returned in cleartext. To use the token
+  please copy it from the response.
+
+* **List tokens**\
+  ```bash
+  curl --request GET 'https://<your host:9200>/auth-app/tokens' \
+       --header 'accept: application/json'
+  ```
+
+  Note that the `token` value in the response to the "List Tokens` request is not the actual
+  app token, but the UUID of the token. So this value cannot be used for authenticating
+  with the token.
+
+  Example output:
+  ```
+  [
+    {
+      "token": "155f402e-1c5c-411c-92d4-92f3b612cd99"
+      "expiration_date": "2024-08-08T13:44:31.025199075+02:00",
+      "created_date": "2024-08-07T13:44:31+02:00",
+      "label": "Generated via Impersonation API"
+    },
+    {
+      "token": "8c606bdb-e22e-4094-9304-732fd4702bc9"
+      "expiration_date": "2024-08-08T13:46:41.936052281+02:00",
+      "created_date": "2024-08-07T13:46:42+02:00",
+      "label": "Generated via Impersonation API"
+    }
+  ]
+  ```
+
+* **Delete a token**\
+  The DELETE request requires:
+  * A `token` key/value pair in the form of `token=<token_issued>`. The value needs to be the hashed value as returned by the `List Tokens` respone.\
+    Example: `token=8c606bdb-e22e-4094-9304-732fd4702bc9`
+  ```bash
+  curl --request DELETE 'https://<your host:9200>/auth-app/tokens?token={value}' \
+       --header 'accept: application/json'
+  ```
+
+### Via Impersonation API
+
+When setting the environment variable `AUTH_APP_ENABLE_IMPERSONATION` to
+`true`, admins will be able to use the `/auth-app/tokens` endpoint to create
+tokens for other users. This can be important for migration scenarios, but
+should not be considered for regular tasks on a production system for security
+reasons.
+
+To impersonate, the respective requests from the CLI commands above extend with
+the following parameters, where you can use one or the other:
+
+* The `userID` in the form of: `userID={value}`\
+  Example:\
+  `userID=4c510ada- ... -42cdf82c3d51`
+
+* The `userName` in the form of: `userName={value}`\
+  Example:\
+  `userName=alan`
+
+Example:\
+A final create request would then look like:
+```bash
+curl --request POST 'https://<your host:9200>/auth-app/tokens?expiry={value}&userName={value}' \
+     --header 'accept: application/json'
+```
+
+### Via CLI (developer only)
+
+As the CLI is using the internal CS3Apis this needs access to the reva gateway
+service. This is mainly of developer (and admin) usage.
+Replace the `user-name` with an existing user. For the `token-expiration`, you
+can use any time abbreviation from the following list: `h, m, s`. Examples:
+`72h` or `1h` or `1m` or `1s.` Default is `72h`.
+
+```bash
+opencloud auth-app create --user-name={user-name} --expiration={token-expiration}
+```
+
+## Authenticating using App Tokens
+
+To autenticate using an App Token simply use the username for which token was generated
+and the token value as returned by the "Create Token" request.
+
+```bash
+curl -u <username>:<tokenvalue> 'https://<your host>/graph/v1.0/me' \
+     --header 'accept: application/json'
+```
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/auth-basic.yaml b/versioned_docs/version-7.x/_static/env-vars/auth-basic.yaml
new file mode 100644
index 000000000..f3d2897ef
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/auth-basic.yaml
@@ -0,0 +1,67 @@
+# Autogenerated
+# Filename: auth-basic.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9147
+  token: ""
+  pprof: false
+  zpages: false
+grpc:
+  addr: 127.0.0.1:9146
+  tls: null
+  protocol: tcp
+token_manager:
+  jwt_secret: ""
+reva:
+  address: eu.opencloud.api.gateway
+  tls:
+    mode: ""
+    cacert: ""
+skip_user_groups_in_token: false
+auth_provider: ldap
+auth_providers:
+  ldap:
+    uri: ldap://localhost:9236
+    ca_cert: ""
+    insecure: false
+    bind_dn: uid=reva,ou=sysusers,o=libregraph-idm
+    bind_password: ""
+    user_base_dn: ou=users,o=libregraph-idm
+    group_base_dn: ou=groups,o=libregraph-idm
+    user_scope: sub
+    group_scope: sub
+    user_filter: ""
+    group_filter: ""
+    user_object_class: inetOrgPerson
+    group_object_class: groupOfNames
+    login_attributes:
+    - uid
+    idp: https://localhost:9200
+    disable_user_mechanism: attribute
+    ldap_disabled_users_group_dn: cn=DisabledUsersGroup,ou=groups,o=libregraph-idm
+    user_schema:
+      id: openCloudUUID
+      tenant_id: ""
+      id_is_octet_string: false
+      mail: mail
+      display_name: displayname
+      user_name: uid
+      user_enabled: openCloudUserEnabled
+    group_schema:
+      id: openCloudUUID
+      id_is_octet_string: false
+      mail: mail
+      display_name: cn
+      group_name: cn
+      member: member
+  owncloudsql:
+    db_username: owncloud
+    db_password: ""
+    db_host: mysql
+    db_port: 3306
+    db_name: owncloud
+    idp: https://localhost:9200
+    nobody: 90
+    join_username: false
+    join_owncloud_uuid: false
diff --git a/versioned_docs/version-7.x/_static/env-vars/auth-basic_configvars.md b/versioned_docs/version-7.x/_static/env-vars/auth-basic_configvars.md
new file mode 100644
index 000000000..09331261e
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/auth-basic_configvars.md
@@ -0,0 +1,56 @@
+## Environment variables for the **auth-basic** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`AUTH_BASIC_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`AUTH_BASIC_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9147`|
+|`AUTH_BASIC_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`AUTH_BASIC_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`AUTH_BASIC_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can  be used for collecting and viewing traces in-memory.`|`false`|
+|`AUTH_BASIC_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9146`|
+|`OC_GRPC_PROTOCOL`<br/>`AUTH_BASIC_GRPC_PROTOCOL`| 1.0.0 |string|`The transport protocol of the GRPC service.`|`tcp`|
+|`OC_JWT_SECRET`<br/>`AUTH_BASIC_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`The CS3 gateway endpoint.`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
+|`AUTH_BASIC_SKIP_USER_GROUPS_IN_TOKEN`| 1.0.0 |bool|`Disables the encoding of the user's group memberships in the reva access token. This reduces the token size, especially when users are members of a large number of groups.`|`false`|
+|`AUTH_BASIC_AUTH_MANAGER`| 1.0.0 |string|`The authentication manager to check if credentials are valid. Supported value is 'ldap'.`|`ldap`|
+|`OC_LDAP_URI`<br/>`AUTH_BASIC_LDAP_URI`| 1.0.0 |string|`URI of the LDAP Server to connect to. Supported URI schemes are 'ldaps://' and 'ldap://'`|`ldap://localhost:9236`|
+|`OC_LDAP_CACERT`<br/>`AUTH_BASIC_LDAP_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the LDAP service. If not defined, the root directory derives from $OC_BASE_DATA_PATH/idm.`|``|
+|`OC_LDAP_INSECURE`<br/>`AUTH_BASIC_LDAP_INSECURE`| 1.0.0 |bool|`Disable TLS certificate validation for the LDAP connections. Do not set this in production environments.`|`false`|
+|`OC_LDAP_BIND_DN`<br/>`AUTH_BASIC_LDAP_BIND_DN`| 1.0.0 |string|`LDAP DN to use for simple bind authentication with the target LDAP server.`|`uid=reva,ou=sysusers,o=libregraph-idm`|
+|`OC_LDAP_BIND_PASSWORD`<br/>`AUTH_BASIC_LDAP_BIND_PASSWORD`| 1.0.0 |string|`Password to use for authenticating the 'bind_dn'.`|``|
+|`OC_LDAP_USER_BASE_DN`<br/>`AUTH_BASIC_LDAP_USER_BASE_DN`| 1.0.0 |string|`Search base DN for looking up LDAP users.`|`ou=users,o=libregraph-idm`|
+|`OC_LDAP_GROUP_BASE_DN`<br/>`AUTH_BASIC_LDAP_GROUP_BASE_DN`| 1.0.0 |string|`Search base DN for looking up LDAP groups.`|`ou=groups,o=libregraph-idm`|
+|`OC_LDAP_USER_SCOPE`<br/>`AUTH_BASIC_LDAP_USER_SCOPE`| 1.0.0 |string|`LDAP search scope to use when looking up users. Supported values are 'base', 'one' and 'sub'.`|`sub`|
+|`OC_LDAP_GROUP_SCOPE`<br/>`AUTH_BASIC_LDAP_GROUP_SCOPE`| 1.0.0 |string|`LDAP search scope to use when looking up groups. Supported values are 'base', 'one' and 'sub'.`|`sub`|
+|`OC_LDAP_USER_FILTER`<br/>`AUTH_BASIC_LDAP_USER_FILTER`| 1.0.0 |string|`LDAP filter to add to the default filters for user search like '(objectclass=openCloudUser)'.`|``|
+|`OC_LDAP_GROUP_FILTER`<br/>`AUTH_BASIC_LDAP_GROUP_FILTER`| 1.0.0 |string|`LDAP filter to add to the default filters for group searches.`|``|
+|`OC_LDAP_USER_OBJECTCLASS`<br/>`AUTH_BASIC_LDAP_USER_OBJECTCLASS`| 1.0.0 |string|`The object class to use for users in the default user search filter ('inetOrgPerson').`|`inetOrgPerson`|
+|`OC_LDAP_GROUP_OBJECTCLASS`<br/>`AUTH_BASIC_LDAP_GROUP_OBJECTCLASS`| 1.0.0 |string|`The object class to use for groups in the default group search filter ('groupOfNames').`|`groupOfNames`|
+|`LDAP_LOGIN_ATTRIBUTES`<br/>`AUTH_BASIC_LDAP_LOGIN_ATTRIBUTES`| 1.0.0 |[]string|`A list of user object attributes that can be used for login. See the Environment Variable Types description for more details.`|`[uid]`|
+|`OC_URL`<br/>`OC_OIDC_ISSUER`<br/>`AUTH_BASIC_IDP_URL`| 1.0.0 |string|`The identity provider value to set in the userids of the CS3 user objects for users returned by this user provider.`|`https://localhost:9200`|
+|`OC_LDAP_DISABLE_USER_MECHANISM`<br/>`AUTH_BASIC_DISABLE_USER_MECHANISM`| 1.0.0 |string|`An option to control the behavior for disabling users. Valid options are 'none', 'attribute' and 'group'. If set to 'group', disabling a user via API will add the user to the configured group for disabled users, if set to 'attribute' this will be done in the ldap user entry, if set to 'none' the disable request is not processed.`|`attribute`|
+|`OC_LDAP_DISABLED_USERS_GROUP_DN`<br/>`AUTH_BASIC_DISABLED_USERS_GROUP_DN`| 1.0.0 |string|`The distinguished name of the group to which added users will be classified as disabled when 'disable_user_mechanism' is set to 'group'.`|`cn=DisabledUsersGroup,ou=groups,o=libregraph-idm`|
+|`OC_LDAP_USER_SCHEMA_ID`<br/>`AUTH_BASIC_LDAP_USER_SCHEMA_ID`| 1.0.0 |string|`LDAP Attribute to use as the unique ID for users. This should be a stable globally unique ID like a UUID.`|`openCloudUUID`|
+|`OC_LDAP_USER_SCHEMA_TENANT_ID`<br/>`AUTH_BASIC_LDAP_USER_SCHEMA_TENANT_ID`| 4.0.0 |string|`LDAP Attribute to use for the tenant ID of users. This is used to identify the tenant of a user in a multi-tenant environment.`|``|
+|`OC_LDAP_USER_SCHEMA_ID_IS_OCTETSTRING`<br/>`AUTH_BASIC_LDAP_USER_SCHEMA_ID_IS_OCTETSTRING`| 1.0.0 |bool|`Set this to true if the defined 'ID' attribute for users is of the 'OCTETSTRING' syntax. This is e.g. required when using the 'objectGUID' attribute of Active Directory for the user IDs.`|`false`|
+|`OC_LDAP_USER_SCHEMA_MAIL`<br/>`AUTH_BASIC_LDAP_USER_SCHEMA_MAIL`| 1.0.0 |string|`LDAP Attribute to use for the email address of users.`|`mail`|
+|`OC_LDAP_USER_SCHEMA_DISPLAYNAME`<br/>`AUTH_BASIC_LDAP_USER_SCHEMA_DISPLAYNAME`| 1.0.0 |string|`LDAP Attribute to use for the displayname of users.`|`displayname`|
+|`OC_LDAP_USER_SCHEMA_USERNAME`<br/>`AUTH_BASIC_LDAP_USER_SCHEMA_USERNAME`| 1.0.0 |string|`LDAP Attribute to use for username of users.`|`uid`|
+|`OC_LDAP_USER_ENABLED_ATTRIBUTE`<br/>`AUTH_BASIC_LDAP_USER_ENABLED_ATTRIBUTE`| 1.0.0 |string|`LDAP attribute to use as a flag telling if the user is enabled or disabled.`|`openCloudUserEnabled`|
+|`OC_LDAP_GROUP_SCHEMA_ID`<br/>`AUTH_BASIC_LDAP_GROUP_SCHEMA_ID`| 1.0.0 |string|`LDAP Attribute to use as the unique id for groups. This should be a stable globally unique id (e.g. a UUID).`|`openCloudUUID`|
+|`OC_LDAP_GROUP_SCHEMA_ID_IS_OCTETSTRING`<br/>`AUTH_BASIC_LDAP_GROUP_SCHEMA_ID_IS_OCTETSTRING`| 1.0.0 |bool|`Set this to true if the defined 'id' attribute for groups is of the 'OCTETSTRING' syntax. This is e.g. required when using the 'objectGUID' attribute of Active Directory for the group IDs.`|`false`|
+|`OC_LDAP_GROUP_SCHEMA_MAIL`<br/>`AUTH_BASIC_LDAP_GROUP_SCHEMA_MAIL`| 1.0.0 |string|`LDAP Attribute to use for the email address of groups (can be empty).`|`mail`|
+|`OC_LDAP_GROUP_SCHEMA_DISPLAYNAME`<br/>`AUTH_BASIC_LDAP_GROUP_SCHEMA_DISPLAYNAME`| 1.0.0 |string|`LDAP Attribute to use for the displayname of groups (often the same as groupname attribute).`|`cn`|
+|`OC_LDAP_GROUP_SCHEMA_GROUPNAME`<br/>`AUTH_BASIC_LDAP_GROUP_SCHEMA_GROUPNAME`| 1.0.0 |string|`LDAP Attribute to use for the name of groups.`|`cn`|
+|`OC_LDAP_GROUP_SCHEMA_MEMBER`<br/>`AUTH_BASIC_LDAP_GROUP_SCHEMA_MEMBER`| 1.0.0 |string|`LDAP Attribute that is used for group members.`|`member`|
+|`AUTH_BASIC_OWNCLOUDSQL_DB_USERNAME`| 1.0.0 |string|`Database user to use for authenticating with the owncloud database.`|`owncloud`|
+|`AUTH_BASIC_OWNCLOUDSQL_DB_PASSWORD`| 1.0.0 |string|`Password for the database user.`|``|
+|`AUTH_BASIC_OWNCLOUDSQL_DB_HOST`| 1.0.0 |string|`Hostname of the database server.`|`mysql`|
+|`AUTH_BASIC_OWNCLOUDSQL_DB_PORT`| 1.0.0 |int|`Network port to use for the database connection.`|`3306`|
+|`AUTH_BASIC_OWNCLOUDSQL_DB_NAME`| 1.0.0 |string|`Name of the owncloud database.`|`owncloud`|
+|`AUTH_BASIC_OWNCLOUDSQL_IDP`| 1.0.0 |string|`The identity provider value to set in the userids of the CS3 user objects for users returned by this user provider.`|`https://localhost:9200`|
+|`AUTH_BASIC_OWNCLOUDSQL_NOBODY`| 1.0.0 |int64|`Fallback number if no numeric UID and GID properties are provided.`|`90`|
+|`AUTH_BASIC_OWNCLOUDSQL_JOIN_USERNAME`| 1.0.0 |bool|`Join the user properties table to read usernames`|`false`|
+|`AUTH_BASIC_OWNCLOUDSQL_JOIN_OWNCLOUD_UUID`| 1.0.0 |bool|`Join the user properties table to read user ID's.`|`false`|
diff --git a/versioned_docs/version-7.x/_static/env-vars/auth-basic_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/auth-basic_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/auth-basic_readme.md b/versioned_docs/version-7.x/_static/env-vars/auth-basic_readme.md
new file mode 100755
index 000000000..441fc5d48
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/auth-basic_readme.md
@@ -0,0 +1,46 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The OpenCloud Auth Basic service provides basic authentication for those clients who cannot handle OpenID Connect. This should only be enabled for tests and development.
+
+The `auth-basic` service is responsible for validating authentication of incoming requests. To do so, it will use the configured `auth manager`, see the `Auth Managers` section. Only HTTP basic auth requests to OpenCloud will involve the `auth-basic` service.
+
+To enable `auth-basic`, you first must set `PROXY_ENABLE_BASIC_AUTH` to `true`.
+
+
+## Table of Contents
+
+* [The `auth` Service Family](#the-auth-service-family)
+* [Auth Managers](#auth-managers)
+  * [LDAP Auth Manager](#ldap-auth-manager)
+  * [Other Auth Managers](#other-auth-managers)
+* [Scalability](#scalability)
+
+## The `auth` Service Family
+
+OpenCloud uses serveral authentication services for different use cases. All services that start with `auth-` are part of the authentication service family. Each member authenticates requests with different scopes. As of now, these services exist:
+  -   `auth-app` handles authentication of external 3rd party apps
+  -   `auth-basic` handles basic authentication
+  -   `auth-bearer` handles oidc authentication
+  -   `auth-machine` handles interservice authentication when a user is impersonated
+  -   `auth-service` handles interservice authentication when using service accounts
+
+## Auth Managers
+
+Since the `auth-basic` service does not do any validation itself, it needs to be configured with an authentication manager. One can use the `AUTH_BASIC_AUTH_MANAGER` environment variable to configure this. Currently only one auth manager is supported: `"ldap"`
+
+### LDAP Auth Manager
+
+Setting `AUTH_BASIC_AUTH_MANAGER` to `"ldap"` will configure the `auth-basic` service to use LDAP as auth manager. This is the recommended option for running in a production and testing environment. More details on how to configure LDAP with OpenCloud can be found in the admin docs.
+
+### Other Auth Managers
+
+OpenCloud currently supports no other auth manager
+
+## Scalability
+
+When using `"ldap"` as auth manager, there is no persistance as requests will just be forwarded to the LDAP server. Therefore, multiple instances of the `auth-basic` service can be started without further configuration. Be aware, that other auth managers might not allow that.
+
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/auth-bearer.yaml b/versioned_docs/version-7.x/_static/env-vars/auth-bearer.yaml
new file mode 100644
index 000000000..f7e28e0e9
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/auth-bearer.yaml
@@ -0,0 +1,27 @@
+# Autogenerated
+# Filename: auth-bearer.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9149
+  token: ""
+  pprof: false
+  zpages: false
+grpc:
+  addr: 127.0.0.1:9148
+  tls: null
+  protocol: tcp
+token_manager:
+  jwt_secret: ""
+reva:
+  address: eu.opencloud.api.gateway
+  tls:
+    mode: ""
+    cacert: ""
+skip_user_groups_in_token: false
+oidc:
+  issuer: https://localhost:9200
+  insecure: false
+  id_claim: preferred_username
+  uid_claim: ""
+  gid_claim: ""
diff --git a/versioned_docs/version-7.x/_static/env-vars/auth-bearer_configvars.md b/versioned_docs/version-7.x/_static/env-vars/auth-bearer_configvars.md
new file mode 100644
index 000000000..60896410b
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/auth-bearer_configvars.md
@@ -0,0 +1,21 @@
+## Environment variables for the **auth-bearer** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`AUTH_BEARER_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`AUTH_BEARER_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9149`|
+|`AUTH_BEARER_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`AUTH_BEARER_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`AUTH_BEARER_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`AUTH_BEARER_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9148`|
+|`OC_GRPC_PROTOCOL`<br/>`AUTH_BEARER_GRPC_PROTOCOL`| 1.0.0 |string|`The transport protocol of the GRPC service.`|`tcp`|
+|`OC_JWT_SECRET`<br/>`AUTH_BEARER_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`The CS3 gateway endpoint.`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
+|`AUTH_BEARER_SKIP_USER_GROUPS_IN_TOKEN`| 1.0.0 |bool|`Disables the encoding of the user's group memberships in the reva access token. This reduces the token size, especially when users are members of a large number of groups.`|`false`|
+|`OC_URL`<br/>`OC_OIDC_ISSUER`<br/>`AUTH_BEARER_OIDC_ISSUER`| 1.0.0 |string|`URL of the OIDC issuer. It defaults to URL of the builtin IDP.`|`https://localhost:9200`|
+|`OC_INSECURE`<br/>`AUTH_BEARER_OIDC_INSECURE`| 1.0.0 |bool|`Allow insecure connections to the OIDC issuer.`|`false`|
+|`AUTH_BEARER_OIDC_ID_CLAIM`| 1.0.0 |string|`Name of the claim, which holds the user identifier.`|`preferred_username`|
+|`AUTH_BEARER_OIDC_UID_CLAIM`| 1.0.0 |string|`Name of the claim, which holds the UID.`|``|
+|`AUTH_BEARER_OIDC_GID_CLAIM`| 1.0.0 |string|`Name of the claim, which holds the GID.`|``|
diff --git a/versioned_docs/version-7.x/_static/env-vars/auth-bearer_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/auth-bearer_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/auth-bearer_readme.md b/versioned_docs/version-7.x/_static/env-vars/auth-bearer_readme.md
new file mode 100755
index 000000000..8df3212aa
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/auth-bearer_readme.md
@@ -0,0 +1,33 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The OpenCloud Auth Bearer service communicates with the configured OpenID Connect identity provider to authenticate requests. OpenID Connect is the default authentication mechanism for all clients: web, desktop and mobile. Basic auth is only used for testing and has to be explicity enabled.
+
+
+## Table of Contents
+
+* [The `auth` Service Family](#the-auth-service-family)
+* [Built in OpenID Connect Identity Provider](#built-in-openid-connect-identity-provider)
+* [Scalability](#scalability)
+
+## The `auth` Service Family
+
+OpenCloud uses serveral authentication services for different use cases. All services that start with `auth-` are part of the authentication service family. Each member authenticates requests with different scopes. As of now, these services exist:
+  -   `auth-app` handles authentication of external 3rd party apps
+  -   `auth-basic` handles basic authentication
+  -   `auth-bearer` handles oidc authentication
+  -   `auth-machine` handles interservice authentication when a user is impersonated
+  -   `auth-service` handles interservice authentication when using service accounts
+
+## Built in OpenID Connect Identity Provider
+
+A default OpenCloud deployment will start a [built in OpenID Connect identity provider](https://github.com/opencloud-eu/opencloud/tree/main/services/idp) but can be configured to use an external one as well.
+
+## Scalability
+
+There is no persistance or caching. The proxy caches verified auth bearer tokens. Requests will be forwarded to the identity provider. Therefore, multiple instances of the `auth-bearer` service can be started without further configuration. Currently, the auth registry used by the gateway can only use a single instance of the service. To use more than one auth provider per deployment you need to scale the gateway.
+
+This will change when we use the service registry in more places and use micro clients to select an instance of a service.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/auth-machine.yaml b/versioned_docs/version-7.x/_static/env-vars/auth-machine.yaml
new file mode 100644
index 000000000..fe0287023
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/auth-machine.yaml
@@ -0,0 +1,22 @@
+# Autogenerated
+# Filename: auth-machine.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9167
+  token: ""
+  pprof: false
+  zpages: false
+grpc:
+  addr: 127.0.0.1:9166
+  tls: null
+  protocol: tcp
+token_manager:
+  jwt_secret: ""
+reva:
+  address: eu.opencloud.api.gateway
+  tls:
+    mode: ""
+    cacert: ""
+skip_user_groups_in_token: false
+machine_auth_api_key: ""
diff --git a/versioned_docs/version-7.x/_static/env-vars/auth-machine_configvars.md b/versioned_docs/version-7.x/_static/env-vars/auth-machine_configvars.md
new file mode 100644
index 000000000..d0784ca1d
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/auth-machine_configvars.md
@@ -0,0 +1,17 @@
+## Environment variables for the **auth-machine** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`AUTH_MACHINE_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`AUTH_MACHINE_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9167`|
+|`AUTH_MACHINE_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`AUTH_MACHINE_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`AUTH_MACHINE_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`AUTH_MACHINE_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9166`|
+|`OC_GRPC_PROTOCOL`<br/>`AUTH_MACHINE_GRPC_PROTOCOL`| 1.0.0 |string|`The transport protocol of the GRPC service.`|`tcp`|
+|`OC_JWT_SECRET`<br/>`AUTH_MACHINE_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`The CS3 gateway endpoint.`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
+|`AUTH_MACHINE_SKIP_USER_GROUPS_IN_TOKEN`| 1.0.0 |bool|`Disables the encoding of the user's group memberships in the reva access token. This reduces the token size, especially when users are members of a large number of groups.`|`false`|
+|`OC_MACHINE_AUTH_API_KEY`<br/>`AUTH_MACHINE_API_KEY`| 1.0.0 |string|`Machine auth API key used to validate internal requests necessary for the access to resources from other services.`|``|
diff --git a/versioned_docs/version-7.x/_static/env-vars/auth-machine_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/auth-machine_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/auth-machine_readme.md b/versioned_docs/version-7.x/_static/env-vars/auth-machine_readme.md
new file mode 100755
index 000000000..809fe02bb
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/auth-machine_readme.md
@@ -0,0 +1,28 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The OpenCloud Auth Machine is used for interservice communication when using user impersonation.
+
+OpenCloud uses serveral authentication services for different use cases. All services that start with `auth-` are part of the authentication service family. Each member authenticates requests with different scopes. As of now, these services exist:
+  -   `auth-app` handles authentication of external 3rd party apps
+  -   `auth-basic` handles basic authentication
+  -   `auth-bearer` handles oidc authentication
+  -   `auth-machine` handles interservice authentication when a user is impersonated
+  -   `auth-service` handles interservice authentication when using service accounts
+
+
+## Table of Contents
+
+* [User Impersonation](#user-impersonation)
+* [Deprecation](#deprecation)
+
+## User Impersonation
+
+When one OpenCloud service is trying to talk to other OpenCloud services, it needs to authenticate itself. To do so, it will impersonate a user using the `auth-machine` service. It will then act on behalf of this user. Any action will show up as action of this specific user, which gets visible when e.g. logged in the audit log.
+
+## Deprecation
+
+With the upcoming `auth-service` service, the `auth-machine` service will be used less frequently and is probably a candidate for deprecation.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/auth-service.yaml b/versioned_docs/version-7.x/_static/env-vars/auth-service.yaml
new file mode 100644
index 000000000..e1cd9551b
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/auth-service.yaml
@@ -0,0 +1,23 @@
+# Autogenerated
+# Filename: auth-service.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9198
+  token: ""
+  pprof: false
+  zpages: false
+grpc:
+  addr: 127.0.0.1:9199
+  tls: null
+  protocol: tcp
+token_manager:
+  jwt_secret: ""
+reva:
+  address: eu.opencloud.api.gateway
+  tls:
+    mode: ""
+    cacert: ""
+service_account:
+  service_account_id: ""
+  service_account_secret: ""
diff --git a/versioned_docs/version-7.x/_static/env-vars/auth-service_configvars.md b/versioned_docs/version-7.x/_static/env-vars/auth-service_configvars.md
new file mode 100644
index 000000000..f69c58d97
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/auth-service_configvars.md
@@ -0,0 +1,17 @@
+## Environment variables for the **auth-service** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`AUTH_SERVICE_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`AUTH_SERVICE_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9198`|
+|`AUTH_SERVICE_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`AUTH_SERVICE_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`AUTH_SERVICE_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`AUTH_SERVICE_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9199`|
+|`OC_GRPC_PROTOCOL`<br/>`AUTH_SERVICE_GRPC_PROTOCOL`| 1.0.0 |string|`The transport protocol of the GRPC service.`|`tcp`|
+|`OC_JWT_SECRET`<br/>`AUTH_SERVICE_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`The CS3 gateway endpoint.`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
+|`OC_SERVICE_ACCOUNT_ID`<br/>`AUTH_SERVICE_SERVICE_ACCOUNT_ID`| 1.0.0 |string|`The ID of the service account the service should use. See the 'auth-service' service description for more details.`|``|
+|`OC_SERVICE_ACCOUNT_SECRET`<br/>`AUTH_SERVICE_SERVICE_ACCOUNT_SECRET`| 1.0.0 |string|`The service account secret.`|``|
diff --git a/versioned_docs/version-7.x/_static/env-vars/auth-service_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/auth-service_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/auth-service_readme.md b/versioned_docs/version-7.x/_static/env-vars/auth-service_readme.md
new file mode 100755
index 000000000..81acd16d8
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/auth-service_readme.md
@@ -0,0 +1,31 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The OpenCloud Auth Service is used to authenticate service accounts. Compared to normal accounts, service accounts are OpenCloud internal only and not available as ordinary users like via LDAP.
+
+
+## Table of Contents
+
+* [The `auth` Service Family](#the-auth-service-family)
+* [Service Accounts](#service-accounts)
+* [Configuring Service Accounts](#configuring-service-accounts)
+
+## The `auth` Service Family
+
+OpenCloud uses serveral authentication services for different use cases. All services that start with `auth-` are part of the authentication service family. Each member authenticates requests with different scopes. As of now, these services exist:
+  -   `auth-app` handles authentication of external 3rd party apps
+  -   `auth-basic` handles basic authentication
+  -   `auth-bearer` handles oidc authentication
+  -   `auth-machine` handles interservice authentication when a user is impersonated
+  -   `auth-service` handles interservice authentication when using service accounts
+
+## Service Accounts
+
+Service accounts are user accounts that are only used for inter service communication. The users have no personal space, do not show up in user lists and cannot login via the UI. Service accounts can be configured in the settings service. Only the `admin` service user is available for now. Additionally to the actions it can do via its role, all service users can stat all files on all spaces.
+
+## Configuring Service Accounts
+
+By using the envvars `OC_SERVICE_ACCOUNT_ID` and `OC_SERVICE_ACCOUNT_SECRET`, one can configure the ID and the secret of the service user. The secret can be rotated regulary to increase security. For activating a new secret, all services where the envvars are used need to be restarted. The secret is always and only stored in memory and never written into any persistant store. Though you can use any string for the service account, it is recommmended to use a UUIDv4 string.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/clientlog.yaml b/versioned_docs/version-7.x/_static/env-vars/clientlog.yaml
new file mode 100644
index 000000000..283a4b237
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/clientlog.yaml
@@ -0,0 +1,24 @@
+# Autogenerated
+# Filename: clientlog.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9260
+  token: ""
+  pprof: false
+  zpages: false
+grpc_client_tls: null
+token_manager:
+  jwt_secret: ""
+reva_gateway: eu.opencloud.api.gateway
+events:
+  endpoint: 127.0.0.1:9233
+  cluster: opencloud-cluster
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+  enable_tls: false
+  username: ""
+  password: ""
+service_account:
+  service_account_id: ""
+  service_account_secret: ""
diff --git a/versioned_docs/version-7.x/_static/env-vars/clientlog_configvars.md b/versioned_docs/version-7.x/_static/env-vars/clientlog_configvars.md
new file mode 100644
index 000000000..53cde196e
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/clientlog_configvars.md
@@ -0,0 +1,20 @@
+## Environment variables for the **clientlog** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`CLIENTLOG_USERLOG_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`CLIENTLOG_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9260`|
+|`CLIENTLOG_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`CLIENTLOG_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`CLIENTLOG_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`OC_JWT_SECRET`<br/>`CLIENTLOG_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`CS3 gateway used to look up user metadata`|`eu.opencloud.api.gateway`|
+|`OC_EVENTS_ENDPOINT`<br/>`CLIENTLOG_EVENTS_ENDPOINT`| 1.0.0 |string|`The address of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture.`|`127.0.0.1:9233`|
+|`OC_EVENTS_CLUSTER`<br/>`CLIENTLOG_EVENTS_CLUSTER`| 1.0.0 |string|`The clusterID of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture. Mandatory when using NATS as event system.`|`opencloud-cluster`|
+|`OC_INSECURE`<br/>`OC_EVENTS_TLS_INSECURE`<br/>`CLIENTLOG_EVENTS_TLS_INSECURE`| 1.0.0 |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_EVENTS_TLS_ROOT_CA_CERTIFICATE`<br/>`CLIENTLOG_EVENTS_TLS_ROOT_CA_CERTIFICATE`| 1.0.0 |string|`The root CA certificate used to validate the server's TLS certificate. If provided NOTIFICATIONS_EVENTS_TLS_INSECURE will be seen as false.`|``|
+|`OC_EVENTS_ENABLE_TLS`<br/>`CLIENTLOG_EVENTS_ENABLE_TLS`| 1.0.0 |bool|`Enable TLS for the connection to the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|`false`|
+|`OC_EVENTS_AUTH_USERNAME`<br/>`CLIENTLOG_EVENTS_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_EVENTS_AUTH_PASSWORD`<br/>`CLIENTLOG_EVENTS_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_SERVICE_ACCOUNT_ID`<br/>`CLIENTLOG_SERVICE_ACCOUNT_ID`| 1.0.0 |string|`The ID of the service account the service should use. See the 'auth-service' service description for more details.`|``|
+|`OC_SERVICE_ACCOUNT_SECRET`<br/>`CLIENTLOG_SERVICE_ACCOUNT_SECRET`| 1.0.0 |string|`The service account secret.`|``|
diff --git a/versioned_docs/version-7.x/_static/env-vars/clientlog_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/clientlog_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/clientlog_readme.md b/versioned_docs/version-7.x/_static/env-vars/clientlog_readme.md
new file mode 100755
index 000000000..50e55db18
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/clientlog_readme.md
@@ -0,0 +1,24 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The `clientlog` service is responsible for composing machine readable notifications for clients. Clients are apps and web interfaces.
+
+
+## Table of Contents
+
+* [The Log Service Ecosystem](#the-log-service-ecosystem)
+* [Clientlog Events](#clientlog-events)
+
+## The Log Service Ecosystem
+
+Log services like the `userlog`, `clientlog` and `sse` are responsible for composing notifications for a certain audience.
+  -   The `userlog` service translates and adjusts messages to be human readable.
+  -   The `clientlog` service composes machine readable messages, so clients can act without the need to query the server.
+  -   The `sse` service is only responsible for sending these messages. It does not care about their form or language.
+
+## Clientlog Events
+
+The messages the `clientlog` service sends are intended for the use by clients, not by users. The client might for example be informed that a file has finished post-processing. With that, the client can make the file available to the user without additional server queries.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/collaboration.yaml b/versioned_docs/version-7.x/_static/env-vars/collaboration.yaml
new file mode 100644
index 000000000..138e4658b
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/collaboration.yaml
@@ -0,0 +1,69 @@
+# Autogenerated
+# Filename: collaboration.yaml
+
+app:
+  name: Collabora
+  product: ""
+  description: Open office documents with Collabora
+  icon: image-edit
+  addr: https://127.0.0.1:9980
+  insecure: false
+  proofkeys:
+    disable: false
+    duration: 12h
+  licensecheckenable: false
+font:
+  asset_path: /var/lib/opencloud/collaboration/fonts
+  preview_text: OpenCloud
+store:
+  store: nats-js-kv
+  nodes:
+  - 127.0.0.1:9233
+  database: collaboration
+  table: ""
+  ttl: 30m0s
+  username: ""
+  password: ""
+  enable_tls: false
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+events:
+  endpoint: 127.0.0.1:9233
+  cluster: opencloud-cluster
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+  enable_tls: false
+  username: ""
+  password: ""
+token_manager:
+  jwt_secret: ""
+grpc:
+  addr: 127.0.0.1:9301
+  protocol: tcp
+http:
+  addr: 127.0.0.1:9300
+  tls:
+    enabled: false
+    cert: ""
+    key: ""
+wopi:
+  wopisrc: https://localhost:9300
+  secret: ""
+  disable_chat: false
+  proxy_url: ""
+  proxy_secret: ""
+  short_tokens: false
+cs3api:
+  gateway:
+    name: eu.opencloud.api.gateway
+  datagateway:
+    insecure: false
+  grpc_client_tls: null
+  app_registration_interval: 30s
+loglevel: error
+debug:
+  addr: 127.0.0.1:9304
+  token: ""
+  pprof: false
+  zpages: false
+machine_auth_api_key: ""
diff --git a/versioned_docs/version-7.x/_static/env-vars/collaboration_configvars.md b/versioned_docs/version-7.x/_static/env-vars/collaboration_configvars.md
new file mode 100644
index 000000000..f8adb0c2c
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/collaboration_configvars.md
@@ -0,0 +1,55 @@
+## Environment variables for the **collaboration** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`COLLABORATION_SERVICE_NAME`| 3.6.0 |string|`The name of the service which is registered. You only need to change this when more than one collaboration service is needed.`|`collaboration`|
+|`COLLABORATION_APP_NAME`| 1.0.0 |string|`The name of the app which is shown to the user. You can chose freely but you are limited to a single word without special characters or whitespaces. We recommend to use pascalCase like 'CollaboraOnline'.`|`Collabora`|
+|`COLLABORATION_APP_PRODUCT`| 1.0.0 |string|`The WebOffice app, either Collabora, OnlyOffice, Microsoft365 or MicrosoftOfficeOnline.`|``|
+|`COLLABORATION_APP_DESCRIPTION`| 1.0.0 |string|`App description`|`Open office documents with Collabora`|
+|`COLLABORATION_APP_ICON`| 1.0.0 |string|`Icon for the app`|`image-edit`|
+|`COLLABORATION_APP_ADDR`| 1.0.0 |string|`The URL where the WOPI app is located, such as \https://127.0.0.1:8080.`|`https://127.0.0.1:9980`|
+|`COLLABORATION_APP_INSECURE`| 1.0.0 |bool|`Skip TLS certificate verification when connecting to the WOPI app`|`false`|
+|`COLLABORATION_APP_PROOF_DISABLE`| 1.0.0 |bool|`Disable the proof keys verification`|`false`|
+|`COLLABORATION_APP_PROOF_DURATION`| 1.0.0 |string|`Duration for the proof keys to be cached in memory, using time.ParseDuration format. If the duration can't be parsed, we'll use the default 12h as duration`|`12h`|
+|`COLLABORATION_APP_LICENSE_CHECK_ENABLE`| 1.0.0 |bool|`Enable license checking to edit files. Needs to be enabled when using Microsoft365 with the business flow.`|`false`|
+|`COLLABORATION_FONT_ASSET_PATH`| next |string|`Serve fonts from a path on the filesystem instead of the builtin assets. If not defined, the root directory derives from $OC_BASE_DATA_PATH/collaboration/fonts`|`/var/lib/opencloud/collaboration/fonts`|
+|`COLLABORATION_FONT_PREVIEW_TEXT`| next |string|`The text that will be displayed in the font preview.`|`OpenCloud`|
+|`OC_PERSISTENT_STORE`<br/>`COLLABORATION_STORE`| 1.0.0 |string|`The type of the store. Supported values are: 'memory', 'nats-js-kv', 'redis-sentinel', 'noop'. See the text description for details.`|`nats-js-kv`|
+|`OC_PERSISTENT_STORE_NODES`<br/>`COLLABORATION_STORE_NODES`| 1.0.0 |[]string|`A list of nodes to access the configured store. This has no effect when 'memory' store is configured. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details.`|`[127.0.0.1:9233]`|
+|`COLLABORATION_STORE_DATABASE`| 1.0.0 |string|`The database name the configured store should use.`|`collaboration`|
+|`COLLABORATION_STORE_TABLE`| 1.0.0 |string|`The database table the store should use.`|``|
+|`OC_PERSISTENT_STORE_TTL`<br/>`COLLABORATION_STORE_TTL`| 1.0.0 |Duration|`Time to live for events in the store. Defaults to '30m' (30 minutes). See the Environment Variable Types description for more details.`|`30m0s`|
+|`OC_PERSISTENT_STORE_AUTH_USERNAME`<br/>`COLLABORATION_STORE_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_PERSISTENT_STORE_AUTH_PASSWORD`<br/>`COLLABORATION_STORE_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_PERSISTENT_STORE_ENABLE_TLS`<br/>`COLLABORATION_STORE_ENABLE_TLS`| next |bool|`Enable TLS for the connection to the store. Only applies when store type 'nats-js-kv' is configured.`|`false`|
+|`OC_INSECURE`<br/>`OC_PERSISTENT_STORE_TLS_INSECURE`<br/>`COLLABORATION_STORE_TLS_INSECURE`| next |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_PERSISTENT_STORE_TLS_ROOT_CA_CERTIFICATE`<br/>`COLLABORATION_STORE_TLS_ROOT_CA_CERTIFICATE`| next |string|`The root CA certificate used to validate the server's TLS certificate. If provided COLLABORATION_STORE_TLS_INSECURE will be seen as false.`|``|
+|`OC_EVENTS_ENDPOINT`<br/>`COLLABORATION_EVENTS_ENDPOINT`| next |string|`The address of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture.`|`127.0.0.1:9233`|
+|`OC_EVENTS_CLUSTER`<br/>`COLLABORATION_EVENTS_CLUSTER`| next |string|`The clusterID of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture. Mandatory when using NATS as event system.`|`opencloud-cluster`|
+|`OC_INSECURE`<br/>`OC_EVENTS_TLS_INSECURE`<br/>`COLLABORATION_EVENTS_TLS_INSECURE`| next |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_EVENTS_TLS_ROOT_CA_CERTIFICATE`<br/>`COLLABORATION_EVENTS_TLS_ROOT_CA_CERTIFICATE`| next |string|`The root CA certificate used to validate the server's TLS certificate. If provided COLLABORATION_EVENTS_TLS_INSECURE will be seen as false.`|``|
+|`OC_EVENTS_ENABLE_TLS`<br/>`COLLABORATION_EVENTS_ENABLE_TLS`| next |bool|`Enable TLS for the connection to the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|`false`|
+|`OC_EVENTS_AUTH_USERNAME`<br/>`COLLABORATION_EVENTS_AUTH_USERNAME`| next |string|`The username to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_EVENTS_AUTH_PASSWORD`<br/>`COLLABORATION_EVENTS_AUTH_PASSWORD`| next |string|`The password to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_JWT_SECRET`<br/>`COLLABORATION_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`COLLABORATION_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9301`|
+|`OC_GRPC_PROTOCOL`<br/>`COLLABORATION_GRPC_PROTOCOL`| 1.0.0 |string|`The transport protocol of the GRPC service.`|`tcp`|
+|`COLLABORATION_HTTP_ADDR`| 1.0.0 |string|`The bind address of the HTTP service.`|`127.0.0.1:9300`|
+|`OC_HTTP_TLS_ENABLED`| 1.0.0 |bool|`Activates TLS for the http based services using the server certifcate and key configured via OC_HTTP_TLS_CERTIFICATE and OC_HTTP_TLS_KEY. If OC_HTTP_TLS_CERTIFICATE is not set a temporary server certificate is generated - to be used with PROXY_INSECURE_BACKEND=true.`|`false`|
+|`OC_HTTP_TLS_CERTIFICATE`| 1.0.0 |string|`Path/File name of the TLS server certificate (in PEM format) for the http services.`|``|
+|`OC_HTTP_TLS_KEY`| 1.0.0 |string|`Path/File name for the TLS certificate key (in PEM format) for the server certificate to use for the http services.`|``|
+|`COLLABORATION_WOPI_SRC`| 1.0.0 |string|`The WOPI source base URL containing schema, host and port. Set this to the schema and domain where the collaboration service is reachable for the wopi app, such as \https://office.example.test.`|`https://localhost:9300`|
+|`COLLABORATION_WOPI_SECRET`| 1.0.0 |string|`Used to mint and verify WOPI JWT tokens and encrypt and decrypt the REVA JWT token embedded in the WOPI JWT token.`|``|
+|`COLLABORATION_WOPI_DISABLE_CHAT`<br/>`OC_WOPI_DISABLE_CHAT`| 1.0.0 |bool|`Disable chat in the office web frontend. This feature applies to OnlyOffice and Microsoft.`|`false`|
+|`COLLABORATION_WOPI_PROXY_URL`| 1.0.0 |string|`The URL to the OpenCloud WOPI proxy. Optional. To use this feature, you need an office365 proxy subscription. If you become part of the Microsoft CSP program (\https://learn.microsoft.com/en-us/partner-center/enroll/csp-overview), you can use WebOffice without a proxy.`|``|
+|`COLLABORATION_WOPI_PROXY_SECRET`| 1.0.0 |string|`Optional, the secret to authenticate against the OpenCloud WOPI proxy. This secret can be obtained from OpenCloud via the office365 proxy subscription.`|``|
+|`COLLABORATION_WOPI_SHORTTOKENS`| 1.0.0 |bool|`Use short access tokens for WOPI access. This is useful for office packages, like Microsoft Office Online, which have URL length restrictions. If enabled, a persistent store must be configured.`|`false`|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`CS3 gateway used to look up user metadata.`|`eu.opencloud.api.gateway`|
+|`COLLABORATION_CS3API_DATAGATEWAY_INSECURE`| 1.0.0 |bool|`Connect to the CS3API data gateway insecurely.`|`false`|
+|`COLLABORATION_CS3API_APP_REGISTRATION_INTERVAL`| 4.0.0 |Duration|`The interval at which the app provider registers itself.`|`30s`|
+|`OC_LOG_LEVEL`<br/>`COLLABORATION_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`COLLABORATION_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9304`|
+|`COLLABORATION_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`COLLABORATION_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`COLLABORATION_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`OC_MACHINE_AUTH_API_KEY`<br/>`COLLABORATION_MACHINE_AUTH_API_KEY`| next |string|`The machine auth API key used to validate internal requests necessary to access resources from other services.`|``|
diff --git a/versioned_docs/version-7.x/_static/env-vars/collaboration_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/collaboration_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/collaboration_readme.md b/versioned_docs/version-7.x/_static/env-vars/collaboration_readme.md
new file mode 100755
index 000000000..e9a5c2785
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/collaboration_readme.md
@@ -0,0 +1,81 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The collaboration service connects opencloud with document servers such as Collabora, ONLYOFFICE or Microsoft using the WOPI protocol.
+
+Since this service requires an external document server, it won't start by default when using `opencloud server`. You must start it manually with the `opencloud collaboration server` command.
+
+Because the collaboration service needs to be started manually, the following prerequisite applies: On collaboration service startup, particular environment variables are required to be populated. If environment variables have a default like the `MICRO_REGISTRY_ADDRESS`, the default will be used, if not set otherwise. Use for all others the instance values as defined. If these environment variables are not provided or misconfigured, the collaboration service will not start up.
+
+Required environment variables:
+* `OC_URL`
+* `OC_JWT_SECRET`
+* `OC_REVA_GATEWAY`
+* `MICRO_REGISTRY_ADDRESS`
+
+
+## Table of Contents
+
+* [Requirements](#requirements)
+* [WOPI Configuration](#wopi-configuration)
+* [Storing](#storing)
+
+## Requirements
+
+The collaboration service requires the target document server (ONLYOFFICE, Collabora, etc.) to be up and running. Additionally, some OpenCloud services are also required to be running in order to register the GRPC service for the `open in app` action in the webUI. The following internal and external services need to be available:
+
+* External document server.
+* The gateway service.
+* The app-registry service.
+
+If any of the named services above have not been started or are not reachable, the collaboration service won't start. For the binary or the docker release of OpenCloud, check with the `opencloud list` command if they have been started. If not, you must start them manually upfront before starting the collaboration service.
+
+## WOPI Configuration
+
+There are a few variables that you need to set:
+
+* `COLLABORATION_APP_NAME`:\
+  The name of the app which is shown to the user. You can chose freely but you are limited to a single word without special characters or whitespaces. We recommend to use pascalCase like 'CollaboraOnline'.
+
+* `COLLABORATION_APP_PRODUCT`:\
+  The product name of the connected WebOffice app, which can be one of the following:\
+  `Collabora`, `OnlyOffice`, `Microsoft365` or `MicrosoftOfficeOnline`. This is used to internally control the behavior according to the different features of the used products.
+
+* `COLLABORATION_APP_ADDR`:\
+  The URL of the collaborative editing app (onlyoffice, collabora, etc).\
+  For example: `https://office.example.com`.
+
+* `COLLABORATION_APP_INSECURE`:\
+  In case you are using a self signed certificate for the WOPI app you can tell the collaboration service to allow an insecure connection.
+
+* `COLLABORATION_WOPI_SRC`:\
+  The external address of the collaboration service. The target app (onlyoffice, collabora, etc) will use this address to read and write files from OpenCloud.\
+  For example: `https://wopi.example.com`.
+
+* `COLLABORATION_WOPI_SHORTTOKENS`:\
+  Needs to be set if the office application like `Microsoft Office Online` complains about the URL is too long  (which contains the access token) and refuses to work. If enabled, a store must be configured.
+
+The application can be customized further by changing the `COLLABORATION_APP_*` options to better describe the application.
+
+## Storing
+
+The `collaboration` service persists information via the configured store in `COLLABORATION_STORE`. Possible stores are:
+  -   `memory`: Basic in-memory store. Will not survive a restart. This is not recommended for this service.
+  -   `redis-sentinel`: Stores data in a configured Redis Sentinel cluster.
+  -   `nats-js-kv`: Stores data using key-value-store feature of [nats jetstream](https://docs.nats.io/nats-concepts/jetstream/key-value-store). This is the default value.
+  -   `noop`: Stores nothing. Useful for testing. Not recommended in production environments.
+
+Other store types may work but are not supported currently.
+
+Note: The service can only be scaled if not using `memory` store and the stores are configured identically over all instances!
+
+Note that if you have used one of the deprecated stores, you should reconfigure to one of the supported ones as the deprecated stores will be removed in a later version.
+
+Store specific notes:
+  -   When using `redis-sentinel`, the Redis master to use is configured via e.g. `OC_CACHE_STORE_NODES` in the form of `<sentinel-host>:<sentinel-port>/<redis-master>` like `10.10.0.200:26379/mymaster`.
+  -   When using `nats-js-kv` it is recommended to set `OC_CACHE_STORE_NODES` to the same value as `OC_EVENTS_ENDPOINT`. That way the cache uses the same nats instance as the event bus.
+  -   When using the `nats-js-kv` store, it is possible to set `OC_CACHE_DISABLE_PERSISTENCE` to instruct nats to not persist cache data on disc.
+
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/eventhistory.yaml b/versioned_docs/version-7.x/_static/env-vars/eventhistory.yaml
new file mode 100644
index 000000000..32797e2f5
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/eventhistory.yaml
@@ -0,0 +1,33 @@
+# Autogenerated
+# Filename: eventhistory.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9270
+  token: ""
+  pprof: false
+  zpages: false
+grpc:
+  addr: 127.0.0.1:9274
+  tls: null
+grpc_client_tls: null
+events:
+  endpoint: 127.0.0.1:9233
+  cluster: opencloud-cluster
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+  enable_tls: false
+  username: ""
+  password: ""
+store:
+  store: nats-js-kv
+  nodes:
+  - 127.0.0.1:9233
+  database: eventhistory
+  table: ""
+  ttl: 0s
+  username: ""
+  password: ""
+  enable_tls: false
+  tls_insecure: false
+  tls_root_ca_certificate: ""
diff --git a/versioned_docs/version-7.x/_static/env-vars/eventhistory_configvars.md b/versioned_docs/version-7.x/_static/env-vars/eventhistory_configvars.md
new file mode 100644
index 000000000..c34fc641f
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/eventhistory_configvars.md
@@ -0,0 +1,27 @@
+## Environment variables for the **eventhistory** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`EVENTHISTORY_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`EVENTHISTORY_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9270`|
+|`EVENTHISTORY_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`EVENTHISTORY_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`EVENTHISTORY_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`EVENTHISTORY_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9274`|
+|`OC_EVENTS_ENDPOINT`<br/>`EVENTHISTORY_EVENTS_ENDPOINT`| 1.0.0 |string|`The address of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture.`|`127.0.0.1:9233`|
+|`OC_EVENTS_CLUSTER`<br/>`EVENTHISTORY_EVENTS_CLUSTER`| 1.0.0 |string|`The clusterID of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture. Mandatory when using NATS as event system.`|`opencloud-cluster`|
+|`OC_INSECURE`<br/>`OC_EVENTS_TLS_INSECURE`<br/>`EVENTHISTORY_EVENTS_TLS_INSECURE`| 1.0.0 |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_EVENTS_TLS_ROOT_CA_CERTIFICATE`<br/>`EVENTHISTORY_EVENTS_TLS_ROOT_CA_CERTIFICATE`| 1.0.0 |string|`The root CA certificate used to validate the server's TLS certificate. Will be seen as empty if NOTIFICATIONS_EVENTS_TLS_INSECURE is provided.`|``|
+|`OC_EVENTS_ENABLE_TLS`<br/>`EVENTHISTORY_EVENTS_ENABLE_TLS`| 1.0.0 |bool|`Enable TLS for the connection to the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|`false`|
+|`OC_EVENTS_AUTH_USERNAME`<br/>`EVENTHISTORY_EVENTS_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_EVENTS_AUTH_PASSWORD`<br/>`EVENTHISTORY_EVENTS_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_PERSISTENT_STORE`<br/>`EVENTHISTORY_STORE`| 1.0.0 |string|`The type of the store. Supported values are: 'memory', 'nats-js-kv', 'redis-sentinel', 'noop'. See the text description for details.`|`nats-js-kv`|
+|`OC_PERSISTENT_STORE_NODES`<br/>`EVENTHISTORY_STORE_NODES`| 1.0.0 |[]string|`A list of nodes to access the configured store. This has no effect when 'memory' store is configured. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details.`|`[127.0.0.1:9233]`|
+|`EVENTHISTORY_STORE_DATABASE`| 1.0.0 |string|`The database name the configured store should use.`|`eventhistory`|
+|`EVENTHISTORY_STORE_TABLE`| 1.0.0 |string|`The database table the store should use.`|``|
+|`OC_PERSISTENT_STORE_TTL`<br/>`EVENTHISTORY_STORE_TTL`| 1.0.0 |Duration|`Time to live for events in the store. Defaults to '336h' (2 weeks). See the Environment Variable Types description for more details.`|`0s`|
+|`OC_PERSISTENT_STORE_AUTH_USERNAME`<br/>`EVENTHISTORY_STORE_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_PERSISTENT_STORE_AUTH_PASSWORD`<br/>`EVENTHISTORY_STORE_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_PERSISTENT_STORE_ENABLE_TLS`<br/>`EVENTHISTORY_STORE_ENABLE_TLS`| next |bool|`Enable TLS for the connection to the store. Only applies when store type 'nats-js-kv' is configured.`|`false`|
+|`OC_INSECURE`<br/>`OC_PERSISTENT_STORE_TLS_INSECURE`<br/>`EVENTHISTORY_STORE_TLS_INSECURE`| next |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_PERSISTENT_STORE_TLS_ROOT_CA_CERTIFICATE`<br/>`EVENTHISTORY_STORE_TLS_ROOT_CA_CERTIFICATE`| next |string|`The root CA certificate used to validate the server's TLS certificate. If provided EVENTHISTORY_STORE_TLS_INSECURE will be seen as false.`|``|
diff --git a/versioned_docs/version-7.x/_static/env-vars/eventhistory_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/eventhistory_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/eventhistory_readme.md b/versioned_docs/version-7.x/_static/env-vars/eventhistory_readme.md
new file mode 100755
index 000000000..e1cd04886
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/eventhistory_readme.md
@@ -0,0 +1,46 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The `eventhistory` consumes all events from the configured event system like NATS, stores them and allows other services to retrieve them via an event ID.
+
+
+## Table of Contents
+
+* [Prerequisites](#prerequisites)
+* [Consuming](#consuming)
+* [Storing](#storing)
+* [Retrieving](#retrieving)
+
+## Prerequisites
+
+Running the eventhistory service without an event system like NATS is not possible.
+
+## Consuming
+
+The `eventhistory` services consumes all events from the configured event system.
+
+## Storing
+
+The `eventhistory` service stores each consumed event via the configured store in `EVENTHISTORY_STORE`. Possible stores are:
+  -   `memory`: Basic in-memory store and the default.
+  -   `redis-sentinel`: Stores data in a configured Redis Sentinel cluster.
+  -   `nats-js-kv`: Stores data using key-value-store feature of [nats jetstream](https://docs.nats.io/nats-concepts/jetstream/key-value-store)
+  -   `noop`: Stores nothing. Useful for testing. Not recommended in production environments.
+
+Other store types may work but are not supported currently.
+
+Note: The service can only be scaled if not using `memory` store and the stores are configured identically over all instances!
+
+Note that if you have used one of the deprecated stores, you should reconfigure to one of the supported ones as the deprecated stores will be removed in a later version.
+
+Store specific notes:
+  -   When using `redis-sentinel`, the Redis master to use is configured via e.g. `OC_CACHE_STORE_NODES` in the form of `<sentinel-host>:<sentinel-port>/<redis-master>` like `10.10.0.200:26379/mymaster`.
+  -   When using `nats-js-kv` it is recommended to set `OC_CACHE_STORE_NODES` to the same value as `OC_EVENTS_ENDPOINT`. That way the cache uses the same nats instance as the event bus.
+  -   When using the `nats-js-kv` store, it is possible to set `OC_CACHE_DISABLE_PERSISTENCE` to instruct nats to not persist cache data on disc.
+
+## Retrieving
+
+Other services can call the `eventhistory` service via a gRPC call to retrieve events. The request must contain the event ID that should be retrieved.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/extended_configvars.md b/versioned_docs/version-7.x/_static/env-vars/extended_configvars.md
new file mode 100644
index 000000000..3ff7880da
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/extended_configvars.md
@@ -0,0 +1,17 @@
+# Environment variables with extended scope not included in a service
+
+| Name | Type | Default Value | Description |
+|---|---|---|---|
+`CS3_GATEWAY` |  |  | Adress of the CS3 backend |
+`CS3_MACHINE_AUTH_API_KEY` |  |  | Authentication API-Key for CS3 backend |
+`EXPERIMENTAL_REGISTER_INTERVAL` | duration | 25s | The interval at which services will re-register themselves with the registry to prevent expiry. Only change on supervision of openCloud Support. |
+`EXPERIMENTAL_REGISTER_TTL` | duration | 30s | The time-to-live for a service registration in the registry. Services must re-register before this time to prevent expiry. Only change on supervision of openCloud Support. |
+`GRPC_MAX_CONNECTION_AGE` | duration | 9223372036854775807 | Timeout for GRPC connections. After timeout, a new connection will be established automatically. The default value is in ns and is about 2.5 mio h. |
+`MICRO_LOG_LEVEL` | string | Error | Set the log level for the internal go micro framework. Only change on supervision of openCloud Support. |
+`MICRO_REGISTRY` | string | nats-js-kv | The type of registry to use. Only change on supervision of openCloud Support. |
+`MICRO_REGISTRY_ADDRESS` | string | 127.0.0.1:9233 | The bind address of the internal natsjs registry. Only change on supervision of openCloud Support. |
+`MICRO_REGISTRY_AUTH_PASSWORD` | string |  | Optional when using nats to authenticate with the nats cluster. |
+`MICRO_REGISTRY_AUTH_USERNAME` | string |  | Optional when using nats to authenticate with the nats cluster. |
+`OC_BASE_DATA_PATH` | string |  | The base directory location used by several services and for user data. See the General Info section in the documentation for more details on defaults. Services can have, if available, an individual setting with an own environment variable. |
+`OC_CONFIG_DIR` | string |  | The default directory location for config files. See the General Info section in the documentation for more details on defaults. |
+`OC_GRPC_MAX_RECEIVED_MESSAGE_SIZE` | integer | 10240000 | Sets the maximum message size in bytes the GRPC client can receive. |
\ No newline at end of file
diff --git a/versioned_docs/version-7.x/_static/env-vars/frontend.yaml b/versioned_docs/version-7.x/_static/env-vars/frontend.yaml
new file mode 100644
index 000000000..a2e0f0017
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/frontend.yaml
@@ -0,0 +1,168 @@
+# Autogenerated
+# Filename: frontend.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9141
+  token: ""
+  pprof: false
+  zpages: false
+http:
+  addr: 127.0.0.1:9140
+  protocol: tcp
+  prefix: ""
+  cors:
+    allow_origins:
+    - https://localhost:9200
+    allow_methods:
+    - OPTIONS
+    - HEAD
+    - GET
+    - PUT
+    - POST
+    - PATCH
+    - DELETE
+    - MKCOL
+    - PROPFIND
+    - PROPPATCH
+    - MOVE
+    - COPY
+    - REPORT
+    - SEARCH
+    allow_headers:
+    - Origin
+    - Accept
+    - Content-Type
+    - Depth
+    - Authorization
+    - Ocs-Apirequest
+    - If-None-Match
+    - If-Match
+    - Destination
+    - Overwrite
+    - X-Request-Id
+    - X-Requested-With
+    - Tus-Resumable
+    - Tus-Checksum-Algorithm
+    - Upload-Concat
+    - Upload-Length
+    - Upload-Metadata
+    - Upload-Defer-Length
+    - Upload-Expires
+    - Upload-Checksum
+    - Upload-Offset
+    - X-HTTP-Method-Override
+    - Cache-Control
+    allow_credentials: false
+transfer_secret: ""
+token_manager:
+  jwt_secret: ""
+reva:
+  address: eu.opencloud.api.gateway
+  tls:
+    mode: ""
+    cacert: ""
+machine_auth_api_key: ""
+skip_user_groups_in_token: false
+max_quota: 0
+upload_max_chunk_size: 10000000
+upload_http_method_override: ""
+default_upload_protocol: tus
+enable_federated_sharing_incoming: false
+enable_federated_sharing_outgoing: false
+search_min_length: 3
+disable_sse: false
+disable_radicale: false
+default_link_permissions: 1
+public_url: https://localhost:9200
+max_concurrency: 1
+app_handler:
+  insecure: false
+  secure_view_app_addr: eu.opencloud.api.collaboration
+archiver:
+  max_num_files: 10000
+  max_size: 1073741824
+  insecure: false
+data_gateway:
+  prefix: data
+ocs:
+  prefix: ocs
+  share_prefix: /Shares
+  home_namespace: /users/{{.Id.OpaqueId}}
+  additional_info_attribute: '{{.Mail}}'
+  stat_cache_type: memory
+  stat_cache_nodes:
+  - 127.0.0.1:9233
+  stat_cache_database: cache-stat
+  stat_cache_table: ""
+  stat_cache_ttl: 5m0s
+  stat_cache_disable_persistence: false
+  stat_cache_auth_username: ""
+  stat_cache_auth_password: ""
+  stat_cache_enable_tls: false
+  stat_cache_tls_insecure: false
+  stat_cache_tls_root_ca_certificate: ""
+  enable_denials: false
+  list_ocm_shares: true
+  include_ocm_sharees: false
+  public_sharing_share_must_have_password: true
+  public_sharing_writeableshare_must_have_password: false
+  show_email_in_results: false
+ocdav:
+  prefix: ""
+  skip_user_groups_in_token: false
+  webdav_namespace: /users/{{.Id.OpaqueId}}
+  files_namespace: /users/{{.Id.OpaqueId}}
+  shares_namespace: /Shares
+  ocm_namespace: /public
+  public_url: https://localhost:9200
+  insecure: false
+  enable_http_tpc: false
+  gateway_request_timeout: 84300
+  machine_auth_api_key: ""
+  allow_propfind_depth_infinity: false
+  name_validation:
+    invalid_chars:
+    - "\f"
+    - "\r"
+    - |2+
+
+    - \
+    max_length: 255
+checksums:
+  supported_types:
+  - sha1
+  - md5
+  - adler32
+  preferred_upload_type: sha1
+read_only_user_attributes: []
+ldap_server_write_enabled: true
+edit_login_allowed_disabled: false
+full_text_search: false
+check_for_updates: true
+middleware:
+  auth:
+    credentials_by_user_agent: {}
+events:
+  endpoint: 127.0.0.1:9233
+  cluster: opencloud-cluster
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+  enable_tls: false
+  username: ""
+  password: ""
+grpc_client_tls: null
+auto_accept_shares: true
+service_account:
+  service_account_id: ""
+  service_account_secret: ""
+password_policy:
+  min_characters: 8
+  min_lowercase_characters: 1
+  min_uppercase_characters: 1
+  min_digits: 1
+  min_special_characters: 1
+  banned_passwords_list: ""
+configurable_notifications: false
+groupware:
+  enabled: false
diff --git a/versioned_docs/version-7.x/_static/env-vars/frontend_configvars.md b/versioned_docs/version-7.x/_static/env-vars/frontend_configvars.md
new file mode 100644
index 000000000..d9ded4bb0
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/frontend_configvars.md
@@ -0,0 +1,126 @@
+
+2026-06-19-00-12-13
+
+## Deprecation Notice
+
+| Deprecation Info | Deprecation Version | Removal Version | Deprecation Replacement |
+|---|---|---|:---|
+| The OCS API is deprecated | 1.0.0 | next-prod |  |
+| The OCS API is deprecated | 1.0.0 | next-prod |  |
+| The OCS API is deprecated | 1.0.0 | next-prod |  |
+| The OCS API is deprecated | 1.0.0 | next-prod |  |
+| FRONTEND_OCS_STAT_CACHE_STORE, the OCS API is deprecated | 1.0.0 | next-prod |  |
+| FRONTEND_OCS_STAT_CACHE_STORE_NODES, the OCS API is deprecated | 1.0.0 | next-prod |  |
+| The OCS API is deprecated | 1.0.0 | next-prod |  |
+| FRONTEND_OCS_STAT_CACHE_TTL, the OCS API is deprecated | 1.0.0 | next-prod |  |
+| FRONTEND_OCS_STAT_CACHE_DISABLE_PERSISTENCE, the OCS API is deprecated | 1.0.0 | next-prod |  |
+| FRONTEND_OCS_STAT_CACHE_AUTH_USERNAME, the OCS API is deprecated | 1.0.0 | next-prod |  |
+| FRONTEND_OCS_STAT_CACHE_AUTH_PASSWORD, the OCS API is deprecated | 1.0.0 | next-prod |  |
+| The OCS API is deprecated | 1.0.0 | next-prod |  |
+| FRONTEND_OCS_LIST_OCM_SHARES, the OCS API is deprecated | 1.0.0 | next-prod |  |
+| FRONTEND_OCS_INCLUDE_OCM_SHAREES, the OCS API is deprecated | 1.0.0 | next-prod |  |
+| FRONTEND_OCS_PUBLIC_SHARE_MUST_HAVE_PASSWORD, the OCS API is deprecated | 1.0.0 | next-prod |  |
+| FRONTEND_OCS_PUBLIC_WRITABLE_SHARE_MUST_HAVE_PASSWORD, the OCS API is deprecated | 1.0.0 | next-prod |  |
+
+## Environment variables for the **frontend** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`FRONTEND_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`FRONTEND_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9141`|
+|`FRONTEND_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`FRONTEND_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`FRONTEND_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`FRONTEND_HTTP_ADDR`| 1.0.0 |string|`The bind address of the HTTP service.`|`127.0.0.1:9140`|
+|`FRONTEND_HTTP_PROTOCOL`| 1.0.0 |string|`The transport protocol of the HTTP service.`|`tcp`|
+|`FRONTEND_HTTP_PREFIX`| 1.0.0 |string|`The Path prefix where the frontend can be accessed (defaults to /).`|``|
+|`OC_CORS_ALLOW_ORIGINS`<br/>`FRONTEND_CORS_ALLOW_ORIGINS`| 1.0.0 |[]string|`A list of allowed CORS origins. See following chapter for more details: *Access-Control-Allow-Origin* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin. See the Environment Variable Types description for more details.`|`[https://localhost:9200]`|
+|`OC_CORS_ALLOW_METHODS`<br/>`FRONTEND_CORS_ALLOW_METHODS`| 1.0.0 |[]string|`A list of allowed CORS methods. See following chapter for more details: *Access-Control-Request-Method* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Method. See the Environment Variable Types description for more details.`|`[OPTIONS HEAD GET PUT POST PATCH DELETE MKCOL PROPFIND PROPPATCH MOVE COPY REPORT SEARCH]`|
+|`OC_CORS_ALLOW_HEADERS`<br/>`FRONTEND_CORS_ALLOW_HEADERS`| 1.0.0 |[]string|`A list of allowed CORS headers. See following chapter for more details: *Access-Control-Request-Headers* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Headers. See the Environment Variable Types description for more details.`|`[Origin Accept Content-Type Depth Authorization Ocs-Apirequest If-None-Match If-Match Destination Overwrite X-Request-Id X-Requested-With Tus-Resumable Tus-Checksum-Algorithm Upload-Concat Upload-Length Upload-Metadata Upload-Defer-Length Upload-Expires Upload-Checksum Upload-Offset X-HTTP-Method-Override Cache-Control]`|
+|`OC_CORS_ALLOW_CREDENTIALS`<br/>`FRONTEND_CORS_ALLOW_CREDENTIALS`| 1.0.0 |bool|`Allow credentials for CORS.See following chapter for more details: *Access-Control-Allow-Credentials* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Credentials.`|`false`|
+|`OC_TRANSFER_SECRET`| 1.0.0 |string|`Transfer secret for signing file up- and download requests.`|``|
+|`OC_JWT_SECRET`<br/>`FRONTEND_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`The CS3 gateway endpoint.`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
+|`OC_MACHINE_AUTH_API_KEY`<br/>`FRONTEND_MACHINE_AUTH_API_KEY`| 1.0.0 |string|`The machine auth API key used to validate internal requests necessary to access resources from other services.`|``|
+|`FRONTEND_SKIP_USER_GROUPS_IN_TOKEN`| 1.0.0 |bool|`Disables the loading of user's group memberships from the reva access token.`|`false`|
+|`OC_SPACES_MAX_QUOTA`<br/>`FRONTEND_MAX_QUOTA`| 1.0.0 |uint64|`Set the global max quota value in bytes. A value of 0 equals unlimited. The value is provided via capabilities.`|`0`|
+|`FRONTEND_UPLOAD_MAX_CHUNK_SIZE`| 1.0.0 |int|`Sets the max chunk sizes in bytes for uploads via the clients.`|`10000000`|
+|`FRONTEND_UPLOAD_HTTP_METHOD_OVERRIDE`| 1.0.0 |string|`Advise TUS to replace PATCH requests by POST requests.`|``|
+|`FRONTEND_DEFAULT_UPLOAD_PROTOCOL`| 1.0.0 |string|`The default upload protocol to use in clients. Currently only 'tus' is available. See the developer API documentation for more details about TUS.`|`tus`|
+|`OC_ENABLE_OCM`<br/>`FRONTEND_ENABLE_FEDERATED_SHARING_INCOMING`| 1.0.0 |bool|`Changing this value is NOT supported. Enables support for incoming federated sharing for clients. The backend behaviour is not changed.`|`false`|
+|`OC_ENABLE_OCM`<br/>`FRONTEND_ENABLE_FEDERATED_SHARING_OUTGOING`| 1.0.0 |bool|`Changing this value is NOT supported. Enables support for outgoing federated sharing for clients. The backend behaviour is not changed.`|`false`|
+|`FRONTEND_SEARCH_MIN_LENGTH`| 1.0.0 |int|`Minimum number of characters to enter before a client should start a search for Share receivers. This setting can be used to customize the user experience if e.g too many results are displayed.`|`3`|
+|`OC_DISABLE_SSE`<br/>`FRONTEND_DISABLE_SSE`| 1.0.0 |bool|`When set to true, clients are informed that the Server-Sent Events endpoint is not accessible.`|`false`|
+|`FRONTEND_DISABLE_RADICALE`| 4.0.0 |bool|`When set to true, clients are informed that the Radicale (CalDAV/CardDAV) is not accessible.`|`false`|
+|`FRONTEND_DEFAULT_LINK_PERMISSIONS`| 1.0.0 |int|`Defines the default permissions a link is being created with. Possible values are 0 (= internal link, for instance members only) and 1 (= public link with viewer permissions). Defaults to 1.`|`1`|
+|`OC_URL`<br/>`FRONTEND_PUBLIC_URL`| 1.0.0 |string|`The public facing URL of the OpenCloud frontend.`|`https://localhost:9200`|
+|`OC_MAX_CONCURRENCY`<br/>`FRONTEND_MAX_CONCURRENCY`| 1.0.0 |int|`Maximum number of concurrent go-routines. Higher values can potentially get work done faster but will also cause more load on the system. Values of 0 or below will be ignored and the default value will be used.`|`1`|
+|`OC_INSECURE`<br/>`FRONTEND_APP_HANDLER_INSECURE`| 1.0.0 |bool|`Allow insecure connections to the frontend.`|`false`|
+|`FRONTEND_APP_HANDLER_SECURE_VIEW_APP_ADDR`| 1.0.0 |string|`Service name or address of the app provider to use for secure view. Should match the service name or address of the registered CS3 app provider.`|`eu.opencloud.api.collaboration`|
+|`FRONTEND_ARCHIVER_MAX_NUM_FILES`| 1.0.0 |int64|`Max number of files that can be packed into an archive.`|`10000`|
+|`FRONTEND_ARCHIVER_MAX_SIZE`| 1.0.0 |int64|`Max size in bytes of the zip archive the archiver can create.`|`1073741824`|
+|`OC_INSECURE`<br/>`FRONTEND_ARCHIVER_INSECURE`| 1.0.0 |bool|`Allow insecure connections to the archiver.`|`false`|
+|`FRONTEND_DATA_GATEWAY_PREFIX`| 1.0.0 |string|`Path prefix for the data gateway.`|`data`|
+|`FRONTEND_OCS_PREFIX`| 1.0.0 |string|`URL path prefix for the OCS service. Note that the string must not start with '/'.`|`ocs`|
+|`FRONTEND_OCS_SHARE_PREFIX`| 1.0.0 |string|`Path prefix for shares as part of a CS3 resource. Note that the path must start with '/'.`|`/Shares`|
+|`FRONTEND_OCS_PERSONAL_NAMESPACE`| 1.0.0 |string|`Home namespace identifier.`|`/users/{{.Id.OpaqueId}}`|
+|`FRONTEND_OCS_ADDITIONAL_INFO_ATTRIBUTE`| 1.0.0 |string|`Additional information attribute for the user like {{.Mail}}.`|`{{.Mail}}`|
+|`OC_CACHE_STORE`<br/>`FRONTEND_OCS_STAT_CACHE_STORE`| 1.0.0 |string|`The type of the cache store. Supported values are: 'memory', 'redis-sentinel', 'nats-js-kv', 'noop'. See the text description for details.`|`memory`|
+|`OC_CACHE_STORE_NODES`<br/>`FRONTEND_OCS_STAT_CACHE_STORE_NODES`| 1.0.0 |[]string|`A list of nodes to access the configured store. This has no effect when 'memory' store is configured. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details.`|`[127.0.0.1:9233]`|
+|`OC_CACHE_DATABASE`| 1.0.0 |string|`The database name the configured store should use.`|`cache-stat`|
+|`FRONTEND_OCS_STAT_CACHE_TABLE`| 1.0.0 |string|`The database table the store should use.`|``|
+|`OC_CACHE_TTL`<br/>`FRONTEND_OCS_STAT_CACHE_TTL`| 1.0.0 |Duration|`Default time to live for user info in the cache. Only applied when access tokens has no expiration. See the Environment Variable Types description for more details.`|`5m0s`|
+|`OC_CACHE_DISABLE_PERSISTENCE`<br/>`FRONTEND_OCS_STAT_CACHE_DISABLE_PERSISTENCE`| 1.0.0 |bool|`Disable persistence of the cache. Only applies when using the 'nats-js-kv' store type. Defaults to false.`|`false`|
+|`OC_CACHE_AUTH_USERNAME`<br/>`FRONTEND_OCS_STAT_CACHE_AUTH_USERNAME`| 1.0.0 |string|`The username to use for authentication. Only applies when using the 'nats-js-kv' store type.`|``|
+|`OC_CACHE_AUTH_PASSWORD`<br/>`FRONTEND_OCS_STAT_CACHE_AUTH_PASSWORD`| 1.0.0 |string|`The password to use for authentication. Only applies when using the 'nats-js-kv' store type.`|``|
+|`OC_CACHE_ENABLE_TLS`<br/>`FRONTEND_OCS_STAT_CACHE_ENABLE_TLS`| next |bool|`Enable TLS for the connection to file metadata cache.`|`false`|
+|`OC_INSECURE`<br/>`OC_CACHE_TLS_INSECURE`<br/>`FRONTEND_OCS_STAT_CACHE_TLS_INSECURE`| next |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_CACHE_TLS_ROOT_CA_CERTIFICATE`<br/>`FRONTEND_OCS_STAT_CACHE_TLS_ROOT_CA_CERTIFICATE`| next |string|`The root CA certificate used to validate the server's TLS certificate. If provided FRONTEND_OCS_STAT_CACHE_TLS_INSECURE will be seen as false.`|``|
+|`FRONTEND_OCS_ENABLE_DENIALS`| 1.0.0 |bool|`EXPERIMENTAL: enable the feature to deny access on folders.`|`false`|
+|`OC_ENABLE_OCM`<br/>`FRONTEND_OCS_LIST_OCM_SHARES`| 1.0.0 |bool|`Include OCM shares when listing shares. See the OCM service documentation for more details.`|`true`|
+|`OC_ENABLE_OCM`<br/>`FRONTEND_OCS_INCLUDE_OCM_SHAREES`| 1.0.0 |bool|`Include OCM sharees when listing sharees.`|`false`|
+|`OC_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD`<br/>`FRONTEND_OCS_PUBLIC_SHARE_MUST_HAVE_PASSWORD`| 1.0.0 |bool|`Set this to true if you want to enforce passwords on all public shares.`|`true`|
+|`OC_SHARING_PUBLIC_WRITEABLE_SHARE_MUST_HAVE_PASSWORD`<br/>`FRONTEND_OCS_PUBLIC_WRITEABLE_SHARE_MUST_HAVE_PASSWORD`| 1.0.0 |bool|`Set this to true if you want to enforce passwords for writable shares. Only effective if the setting for 'passwords on all public shares' is set to false.`|`false`|
+|`OC_SHOW_USER_EMAIL_IN_RESULTS`| 1.0.0 |bool|`Include user email addresses in responses. If absent or set to false emails will be omitted from results. Please note that admin users can always see all email addresses.`|`false`|
+|`OCDAV_HTTP_PREFIX`<br/>`FRONTENT_OCDAV_HTTP_PREFIX`| 1.0.0 |string|`A URL path prefix for the handler.`|``|
+|`OCDAV_SKIP_USER_GROUPS_IN_TOKEN`<br/>`FRONTENT_OCDAV_SKIP_USER_GROUPS_IN_TOKEN`| 1.0.0 |bool|`Disables the loading of user's group memberships from the reva access token.`|`false`|
+|`OCDAV_WEBDAV_NAMESPACE`<br/>`FRONTENT_OCDAV_WEBDAV_NAMESPACE`| 1.0.0 |string|`Jail requests to /dav/webdav into this CS3 namespace. Supports template layouting with CS3 User properties.`|`/users/{{.Id.OpaqueId}}`|
+|`OCDAV_FILES_NAMESPACE`<br/>`FRONTENT_OCDAV_FILES_NAMESPACE`| 1.0.0 |string|`Jail requests to /dav/files/{username} into this CS3 namespace. Supports template layouting with CS3 User properties.`|`/users/{{.Id.OpaqueId}}`|
+|`OCDAV_SHARES_NAMESPACE`<br/>`FRONTENT_OCDAV_SHARES_NAMESPACE`| 1.0.0 |string|`The human readable path for the share jail. Relative to a users personal space root. Upcased intentionally.`|`/Shares`|
+|`OCDAV_OCM_NAMESPACE`<br/>`FRONTENT_OCDAV_OCM_NAMESPACE`| 1.0.0 |string|`The human readable path prefix for the ocm shares.`|`/public`|
+|`OC_URL`<br/>`OCDAV_PUBLIC_URL`<br/>`FRONTENT_OCDAV_PUBLIC_URL`| 1.0.0 |string|`URL where OpenCloud is reachable for users.`|`https://localhost:9200`|
+|`OC_INSECURE`<br/>`OCDAV_INSECURE`<br/>`FRONTENT_OCDAV_INSECURE`| 1.0.0 |bool|`Allow insecure connections to the GATEWAY service.`|`false`|
+|`OCDAV_ENABLE_HTTP_TPC`<br/>`FRONTENT_OCDAV_ENABLE_HTTP_TPC`| 6.0.0 |bool|`Enable HTTP / WebDAV Third-Party-Copy support.`|`false`|
+|`OCDAV_GATEWAY_REQUEST_TIME`<br/>`FRONTENT_OUTOCDAV_GATEWAY_REQUEST_TIMEOUT`| 1.0.0 |int64|`Request timeout in seconds for requests from the oCDAV service to the GATEWAY service.`|`84300`|
+|`OC_MACHINE_AUTH_API_KEY`<br/>`OCDAV_MACHINE_AUTH_API_KEY`<br/>`FRONTENT_OCDAV_MACHINE_AUTH_API_KEY`| 1.0.0 |string|`Machine auth API key used to validate internal requests necessary for the access to resources from other services.`|``|
+|`OCDAV_ALLOW_PROPFIND_DEPTH_INFINITY`<br/>`FRONTENT_OCDAV_ALLOW_PROPFIND_DEPTH_INFINITY`| 1.0.0 |bool|`Allow the use of depth infinity in PROPFINDS. When enabled, a propfind will traverse through all subfolders. If many subfolders are expected, depth infinity can cause heavy server load and/or delayed response times.`|`false`|
+|`OCDAV_NAME_VALIDATION_INVALID_CHARS`<br/>`FRONTENT_OCDAV_NAME_VALIDATION_INVALID_CHARS`| 6.0.0 |[]string|`List of characters that are not allowed in file or folder names.`|``|
+|`OCDAV_NAME_VALIDATION_MAX_LENGTH`<br/>`FRONTENT_OCDAV_NAME_VALIDATION_MAX_LENGTH`| 6.0.0 |int|`Max length of file or folder names.`|`255`|
+|`FRONTEND_CHECKSUMS_SUPPORTED_TYPES`| 1.0.0 |[]string|`A list of checksum types that indicate to clients which hashes the server can use to verify upload integrity. Supported types are 'sha1', 'md5' and 'adler32'. See the Environment Variable Types description for more details.`|`[sha1 md5 adler32]`|
+|`FRONTEND_CHECKSUMS_PREFERRED_UPLOAD_TYPE`| 1.0.0 |string|`The supported checksum type for uploads that indicates to clients supporting multiple hash algorithms which one is preferred by the server. Must be one out of the defined list of SUPPORTED_TYPES.`|`sha1`|
+|`FRONTEND_READONLY_USER_ATTRIBUTES`| 1.0.0 |[]string|`A list of user attributes to indicate as read-only. Supported values: 'user.onPremisesSamAccountName' (username), 'user.displayName', 'user.mail', 'user.passwordProfile' (password), 'user.appRoleAssignments' (role), 'user.memberOf' (groups), 'user.accountEnabled' (login allowed), 'drive.quota' (quota). See the Environment Variable Types description for more details.`|`[]`|
+|`OC_LDAP_SERVER_WRITE_ENABLED`<br/>`FRONTEND_LDAP_SERVER_WRITE_ENABLED`| 1.0.0 |bool|`Allow creating, modifying and deleting LDAP users via the GRAPH API. This can only be set to 'true' when keeping default settings for the LDAP user and group attribute types (the 'OC_LDAP_USER_SCHEMA_* and 'OC_LDAP_GROUP_SCHEMA_* variables).`|`true`|
+|`FRONTEND_EDIT_LOGIN_ALLOWED_DISABLED`| 3.4.0 |bool|`Used to set if login is allowed/forbidden for for User.`|`false`|
+|`FRONTEND_FULL_TEXT_SEARCH_ENABLED`| 1.0.0 |bool|`Set to true to signal the web client that full-text search is enabled.`|`false`|
+|`FRONTEND_CHECK_FOR_UPDATES`| 3.6.0 |bool|`Enable automatic checking for updates. Defaults to true.`|`true`|
+|`OC_EVENTS_ENDPOINT`<br/>`FRONTEND_EVENTS_ENDPOINT`| 1.0.0 |string|`The address of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture.`|`127.0.0.1:9233`|
+|`OC_EVENTS_CLUSTER`<br/>`FRONTEND_EVENTS_CLUSTER`| 1.0.0 |string|`The clusterID of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture. Mandatory when using NATS as event system.`|`opencloud-cluster`|
+|`OC_INSECURE`<br/>`OC_EVENTS_TLS_INSECURE`<br/>`FRONTEND_EVENTS_TLS_INSECURE`| 1.0.0 |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_EVENTS_TLS_ROOT_CA_CERTIFICATE`<br/>`FRONTEND_EVENTS_TLS_ROOT_CA_CERTIFICATE`<br/>`OCS_EVENTS_TLS_ROOT_CA_CERTIFICATE`| 1.0.0 |string|`The root CA certificate used to validate the server's TLS certificate. If provided NOTIFICATIONS_EVENTS_TLS_INSECURE will be seen as false.`|``|
+|`OC_EVENTS_ENABLE_TLS`<br/>`FRONTEND_EVENTS_ENABLE_TLS`| 1.0.0 |bool|`Enable TLS for the connection to the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|`false`|
+|`OC_EVENTS_AUTH_USERNAME`<br/>`FRONTEND_EVENTS_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_EVENTS_AUTH_PASSWORD`<br/>`FRONTEND_EVENTS_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`FRONTEND_AUTO_ACCEPT_SHARES`| 1.0.0 |bool|`Defines if shares should be auto accepted by default. Users can change this setting individually in their profile.`|`true`|
+|`OC_SERVICE_ACCOUNT_ID`<br/>`FRONTEND_SERVICE_ACCOUNT_ID`| 1.0.0 |string|`The ID of the service account the service should use. See the 'auth-service' service description for more details.`|``|
+|`OC_SERVICE_ACCOUNT_SECRET`<br/>`FRONTEND_SERVICE_ACCOUNT_SECRET`| 1.0.0 |string|`The service account secret.`|``|
+|`OC_PASSWORD_POLICY_DISABLED`<br/>`FRONTEND_PASSWORD_POLICY_DISABLED`| 1.0.0 |bool|`Disable the password policy. Defaults to false if not set.`|`false`|
+|`OC_PASSWORD_POLICY_MIN_CHARACTERS`<br/>`FRONTEND_PASSWORD_POLICY_MIN_CHARACTERS`| 1.0.0 |int|`Define the minimum password length. Defaults to 8 if not set.`|`8`|
+|`OC_PASSWORD_POLICY_MIN_LOWERCASE_CHARACTERS`<br/>`FRONTEND_PASSWORD_POLICY_MIN_LOWERCASE_CHARACTERS`| 1.0.0 |int|`Define the minimum number of uppercase letters. Defaults to 1 if not set.`|`1`|
+|`OC_PASSWORD_POLICY_MIN_UPPERCASE_CHARACTERS`<br/>`FRONTEND_PASSWORD_POLICY_MIN_UPPERCASE_CHARACTERS`| 1.0.0 |int|`Define the minimum number of lowercase letters. Defaults to 1 if not set.`|`1`|
+|`OC_PASSWORD_POLICY_MIN_DIGITS`<br/>`FRONTEND_PASSWORD_POLICY_MIN_DIGITS`| 1.0.0 |int|`Define the minimum number of digits. Defaults to 1 if not set.`|`1`|
+|`OC_PASSWORD_POLICY_MIN_SPECIAL_CHARACTERS`<br/>`FRONTEND_PASSWORD_POLICY_MIN_SPECIAL_CHARACTERS`| 1.0.0 |int|`Define the minimum number of characters from the special characters list to be present. Defaults to 1 if not set.`|`1`|
+|`OC_PASSWORD_POLICY_BANNED_PASSWORDS_LIST`<br/>`FRONTEND_PASSWORD_POLICY_BANNED_PASSWORDS_LIST`| 1.0.0 |string|`Path to the 'banned passwords list' file. This only impacts public link password validation. See the documentation for more details.`|``|
+|`FRONTEND_CONFIGURABLE_NOTIFICATIONS`| 1.0.0 |bool|`Allow configuring notifications via web client.`|`false`|
+|`FRONTEND_GROUPWARE_ENABLED`| 3.7.0 |bool|`Enable groupware features. Defaults to false.`|`false`|
diff --git a/versioned_docs/version-7.x/_static/env-vars/frontend_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/frontend_deprecation.md
new file mode 100644
index 000000000..d7c2fb719
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/frontend_deprecation.md
@@ -0,0 +1,4 @@
+
+:::danger
+frontend has deprecated environment variables. Please refer to the table below for more information.
+:::
\ No newline at end of file
diff --git a/versioned_docs/version-7.x/_static/env-vars/frontend_readme.md b/versioned_docs/version-7.x/_static/env-vars/frontend_readme.md
new file mode 100755
index 000000000..a5a7aee3b
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/frontend_readme.md
@@ -0,0 +1,166 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The frontend service translates various OpenCloud related HTTP APIs to CS3 requests.
+
+
+## Table of Contents
+
+* [Endpoints Overview](#endpoints-overview)
+  * [appprovider](#appprovider)
+  * [archiver](#archiver)
+  * [datagateway](#datagateway)
+  * [ocs](#ocs)
+    * [Event Handler](#event-handler)
+  * [Sharing](#sharing)
+* [Scalability](#scalability)
+* [Define Read-Only Attributes](#define-readonly-attributes)
+* [Caching](#caching)
+  * [Auto-Accept Shares](#autoaccept-shares)
+* [Passwords](#passwords)
+  * [The Password Policy](#the-password-policy)
+  * [The Password Policy Capability](#the-password-policy-capability)
+  * [Password Enforcement for all Public Links](#password-enforcement-for-all-public-links)
+  * [Password Enforcement for Writeable Public Links](#password-enforcement-for-writeable-public-links)
+
+## Endpoints Overview
+
+Currently, the frontend service handles requests for three functionalities, which are `appprovider`, `archiver`, `datagateway` and `ocs`.
+
+### appprovider
+
+The appprovider endpoint, by default `/app`, forwards HTTP requests to the CS3 [App Registry API](https://cs3org.github.io/cs3apis/#cs3.app.registry.v1beta1.RegistryAPI)
+
+### archiver
+
+The archiver endpoint, by default `/archiver`, implements zip and tar download for collections of files. It will internally use the CS3 API to initiate downloads and then stream the individual files as part of a compressed file.
+
+### datagateway
+
+The datagateway endpoint, by default `/data`, forwards file up- and download requests to the correct CS3 data provider. OpenCloud starts a dataprovider as part of the storage-* services. The routing happens based on the JWT that was created by a storage provider in response to an `InitiateFileDownload` or `InitiateFileUpload` request.
+
+### ocs
+
+The ocs endpoint, by default `/ocs`, implements the Open Collaboration Services API by translating it into CS3 API requests. It can handle users, groups, capabilities and also implements the files sharing functionality on top of CS3. The `/ocs/v[12].php/cloud/user/signing-key` is currently handled by the dedicated [ocs](https://github.com/opencloud-eu/opencloud/tree/main/services/ocs) service.
+
+#### Event Handler
+
+The `frontend` service contains an eventhandler for handling `ocs` related events. As of now, it only listens to the `ShareCreated` event.
+
+### Sharing
+
+Aggregating share information is one of the most time consuming operations in OpenCloud. The service fetches a list of either received or created shares and has to stat every resource individually. While stats are fast, the default behavior scales linearly with the number of shares.
+
+To save network trips the sharing implementation can cache the stat requests with an in memory cache or in Redis. It will shorten the response time by the network round-trip overhead at the cost of the API only eventually being updated.
+
+Setting `FRONTEND_OCS_RESOURCE_INFO_CACHE_TTL=60` (deprecated) would cache the stat info for 60 seconds. Increasing this value makes sense for large deployments with thousands of active users that keep the cache up to date. Low frequency usage scenarios should not expect a noticeable improvement.
+
+## Scalability
+
+While the frontend service does not persist any data, it does cache information about files and filesystem (`Stat()`) responses and user information. Therefore, multiple instances of this service can be spawned in a bigger deployment like when using container orchestration with Kubernetes, when configuring `FRONTEND_OCS_RESOURCE_INFO_CACHE_STORE` (deprecated) and the related config options.
+
+## Define Read-Only Attributes
+
+A lot of user management is made via the standardized libregraph API. Depending on how the system is configured, there might be some user attributes that an OpenCloud instance admin can't change because of properties coming from an external LDAP server, or similar. This can be the case when the OpenCloud admin is not the LDAP admin. To ease life for admins, there are hints as capabilites telling the frontend which attributes are read-only to enable a different optical representation like being grayed out. To configure these hints, use the environment variable `FRONTEND_READONLY_USER_ATTRIBUTES`, which takes a comma separated list of attributes, see the envvar for supported values.
+
+You can find more details regarding available attributes at the [libre-graph-api openapi-spec](https://github.com/opencloud-eu/libre-graph-api/blob/main/api/openapi-spec/v1.0.yaml) and on [docs.opencloud.eu](https://docs.opencloud.eu/swagger/libre-graph-api/).
+
+## Caching
+
+The `frontend` service can use a configured store via `FRONTEND_OCS_STAT_CACHE_STORE` (deprecated). Possible stores are:
+  -   `memory`: Basic in-memory store and the default.
+  -   `redis-sentinel`: Stores data in a configured Redis Sentinel cluster.
+  -   `nats-js-kv`: Stores data using key-value-store feature of [nats jetstream](https://docs.nats.io/nats-concepts/jetstream/key-value-store)
+  -   `noop`: Stores nothing. Useful for testing. Not recommended in production environments.
+
+Other store types may work but are not supported currently.
+
+Note: The service can only be scaled if not using `memory` store and the stores are configured identically over all instances!
+
+Note that if you have used one of the deprecated stores, you should reconfigure to one of the supported ones as the deprecated stores will be removed in a later version.
+
+Store specific notes:
+  -   When using `redis-sentinel`, the Redis master to use is configured via e.g. `OC_CACHE_STORE_NODES` in the form of `<sentinel-host>:<sentinel-port>/<redis-master>` like `10.10.0.200:26379/mymaster`.
+  -   When using `nats-js-kv` it is recommended to set `OC_CACHE_STORE_NODES` to the same value as `OC_EVENTS_ENDPOINT`. That way the cache uses the same nats instance as the event bus.
+  -   When using the `nats-js-kv` store, it is possible to set `OC_CACHE_DISABLE_PERSISTENCE` to instruct nats to not persist cache data on disc.
+
+### Auto-Accept Shares
+
+When setting the `FRONTEND_AUTO_ACCEPT_SHARES` to `true`, all incoming shares will be accepted automatically. Users can overwrite this setting individually in their profile.
+
+## Passwords
+
+### The Password Policy
+
+Note that the password policy currently impacts only **public link password validation**.
+
+In OpenCloud, the password policy is always enabled because the max-length restriction is always applying and should be taken into account by the clients.
+
+With the password policy, mandatory criteria for the password can be defined via the environment variables listed below.
+
+Generally, a password can contain any UTF-8 characters, however some characters are regarded as special since they are not used in ordinary texts. Which characters should be treated as special is defined by "The OWASP® Foundation" [password-special-characters](https://owasp.org/www-community/password-special-characters) (between double quotes): ```" !"#$%&'()*+,-./:;<=>?@[\]^_`{|}~"```
+
+The validation against the banned passwords list can be configured via a text file with words separated by new lines. If a user tries to set a password listed in the banned passwords list, the password can not be used (is invalid) even if the other mandatory criteria are passed. The admin can define the path of the banned passwords list file. If the file doesn't exist in a location, OpenCloud tries to load a file from the `OC_CONFIG_DIR/OC_PASSWORD_POLICY_BANNED_PASSWORDS_LIST`. An option will be enabled when the file has been loaded successfully.
+
+Following environment variables can be set to define the password policy behaviour:
+
+-   `OC_PASSWORD_POLICY_DISABLED`
+Disable the password policy
+-   `OC_PASSWORD_POLICY_MIN_CHARACTERS`
+Define the minimum password length.
+-   `OC_PASSWORD_POLICY_MIN_LOWERCASE_CHARACTERS`
+Define the minimum number of uppercase letters.
+-   `OC_PASSWORD_POLICY_MIN_UPPERCASE_CHARACTERS`
+Define the minimum number of lowercase letters.
+-   `OC_PASSWORD_POLICY_MIN_DIGITS`
+Define the minimum number of digits.
+-   `OC_PASSWORD_POLICY_MIN_SPECIAL_CHARACTERS`
+Define the minimum number of special characters.
+-   `OC_PASSWORD_POLICY_BANNED_PASSWORDS_LIST`
+Path to the 'banned passwords list' file.
+
+These variables are global OpenCloud variables because they are used not only in the frontend service, but also in the sharing service.
+
+Note that a password can have a maximum length of **72 bytes**. Depending on the alphabet used, a character is encoded by 1 to 4 bytes, defining the maximum length of a password indirectly. While US-ASCII will only need one byte, Latin alphabets and also Greek or Cyrillic ones need two bytes. Three bytes are needed for characters in Chinese, Japanese and Korean etc.
+
+### The Password Policy Capability
+
+The capabilities endpoint (e.g. https://cloud.opencloud.test/ocs/v1.php/cloud/capabilities?format=json) gives you following capabilities which are relevant for the password policy:
+
+```json
+{
+  "ocs": {
+    "data": {
+      "capabilities": {
+        "password_policy": {
+          "min_characters": 10,
+          "max_characters": 72,
+          "min_lowercase_characters": 1,
+          "min_uppercase_characters": 2,
+          "min_digits": 1,
+          "min_special_characters": 1
+        }
+      }
+    }
+  }
+}
+```
+
+### Password Enforcement for all Public Links
+
+For public accessible shares, independent if read only or writable, a password is enforced. To change this requirement, set the following environment variable to `false`:
+
+`OC_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD`
+
+### Password Enforcement for Writeable Public Links
+
+For public accessible writable shares, a password can be enforced. To change the current setting, set the following environment variable to `true`:
+
+`OC_SHARING_PUBLIC_WRITEABLE_SHARE_MUST_HAVE_PASSWORD`
+
+Note that changing this environment variable only makes sense if\
+`OC_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD`\
+is set to `false`.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/gateway.yaml b/versioned_docs/version-7.x/_static/env-vars/gateway.yaml
new file mode 100644
index 000000000..3a84ad195
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/gateway.yaml
@@ -0,0 +1,69 @@
+# Autogenerated
+# Filename: gateway.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9143
+  token: ""
+  pprof: false
+  zpages: false
+grpc:
+  addr: 127.0.0.1:9142
+  tls: null
+  protocol: tcp
+token_manager:
+  jwt_secret: ""
+reva:
+  address: eu.opencloud.api.gateway
+  tls:
+    mode: ""
+    cacert: ""
+skip_user_groups_in_token: false
+commit_share_to_storage_grant: true
+share_folder_name: Shares
+disable_home_creation_on_login: true
+transfer_secret: ""
+transfer_expires: 86400
+cache:
+  provider_cache_store: noop
+  provider_cache_nodes:
+  - 127.0.0.1:9233
+  provider_cache_database: cache-providers
+  provider_cache_ttl: 5m0s
+  provider_cache_disable_persistence: false
+  provider_cache_auth_username: ""
+  provider_cache_auth_password: ""
+  provider_cache_enable_tls: false
+  provider_cache_tls_insecure: false
+  provider_cache_tls_root_ca_certificate: ""
+  create_home_cache_store: memory
+  create_home_cache_nodes:
+  - 127.0.0.1:9233
+  create_home_cache_database: cache-createhome
+  create_home_cache_ttl: 5m0s
+  create_home_cache_disable_persistence: false
+  create_home_cache_auth_username: ""
+  create_home_cache_auth_password: ""
+  create_home_cache_enable_tls: false
+  create_home_cache_tls_insecure: false
+  create_home_cache_tls_root_ca_certificate: ""
+frontend_public_url: https://localhost:9200
+users_endpoint: eu.opencloud.api.users
+groups_endpoint: eu.opencloud.api.groups
+permissions_endpoint: eu.opencloud.api.settings
+sharing_endpoint: eu.opencloud.api.sharing
+auth_app_endpoint: eu.opencloud.api.auth-app
+auth_basic_endpoint: eu.opencloud.api.auth-basic
+auth_bearer_endpoint: ""
+auth_machine_endpoint: eu.opencloud.api.auth-machine
+auth_service_endpoint: eu.opencloud.api.auth-service
+storage_public_link_endpoint: eu.opencloud.api.storage-publiclink
+storage_users_endpoint: eu.opencloud.api.storage-users
+storage_shares_endpoint: eu.opencloud.api.storage-shares
+app_registry_endpoint: eu.opencloud.api.app-registry
+ocm_endpoint: eu.opencloud.api.ocm
+storage_registry:
+  driver: spaces
+  rules: []
+  json: ""
+  storage_users_mount_id: ""
diff --git a/versioned_docs/version-7.x/_static/env-vars/gateway_configvars.md b/versioned_docs/version-7.x/_static/env-vars/gateway_configvars.md
new file mode 100644
index 000000000..1f2ba988b
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/gateway_configvars.md
@@ -0,0 +1,60 @@
+## Environment variables for the **gateway** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`GATEWAY_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`GATEWAY_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9143`|
+|`GATEWAY_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`GATEWAY_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`GATEWAY_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`OC_GATEWAY_GRPC_ADDR`<br/>`GATEWAY_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9142`|
+|`OC_GRPC_PROTOCOL`<br/>`GATEWAY_GRPC_PROTOCOL`| 1.0.0 |string|`The transport protocol of the GRPC service.`|`tcp`|
+|`OC_JWT_SECRET`<br/>`GATEWAY_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`The CS3 gateway endpoint.`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
+|`GATEWAY_SKIP_USER_GROUPS_IN_TOKEN`| 1.0.0 |bool|`Disables the loading of user's group memberships from the reva access token.`|`false`|
+|`GATEWAY_COMMIT_SHARE_TO_STORAGE_GRANT`| 1.0.0 |bool|`Commit shares to storage grants. This grants access to shared resources for the share receiver directly on the storage.`|`true`|
+|`GATEWAY_SHARE_FOLDER_NAME`| 1.0.0 |string|`Name of the share folder in users' home space.`|`Shares`|
+|`GATEWAY_DISABLE_HOME_CREATION_ON_LOGIN`| 1.0.0 |bool|`Disable creation of the home space on login.`|`true`|
+|`OC_TRANSFER_SECRET`| 1.0.0 |string|`The storage transfer secret.`|``|
+|`GATEWAY_TRANSFER_EXPIRES`| 1.0.0 |int|`Expiry for the gateway tokens.`|`86400`|
+|`OC_CACHE_STORE`<br/>`GATEWAY_PROVIDER_CACHE_STORE`| 1.0.0 |string|`The type of the cache store. Supported values are: 'memory', 'redis-sentinel', 'nats-js-kv', 'noop'. See the text description for details.`|`noop`|
+|`OC_CACHE_STORE_NODES`<br/>`GATEWAY_PROVIDER_CACHE_STORE_NODES`| 1.0.0 |[]string|`A list of nodes to access the configured store. This has no effect when 'memory' store is configured. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details.`|`[127.0.0.1:9233]`|
+|`OC_CACHE_DATABASE`| 1.0.0 |string|`The database name the configured store should use.`|`cache-providers`|
+|`OC_CACHE_TTL`<br/>`GATEWAY_PROVIDER_CACHE_TTL`| 1.0.0 |Duration|`Default time to live for user info in the cache. Only applied when access tokens has no expiration. See the Environment Variable Types description for more details.`|`5m0s`|
+|`OC_CACHE_DISABLE_PERSISTENCE`<br/>`GATEWAY_PROVIDER_CACHE_DISABLE_PERSISTENCE`| 1.0.0 |bool|`Disables persistence of the provider cache. Only applies when store type 'nats-js-kv' is configured. Defaults to false.`|`false`|
+|`OC_CACHE_AUTH_USERNAME`<br/>`GATEWAY_PROVIDER_CACHE_AUTH_USERNAME`| 1.0.0 |string|`The username to use for authentication. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_CACHE_AUTH_PASSWORD`<br/>`GATEWAY_PROVIDER_CACHE_AUTH_PASSWORD`| 1.0.0 |string|`The password to use for authentication. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_CACHE_ENABLE_TLS`<br/>`GATEWAY_PROVIDER_CACHE_ENABLE_TLS`| next |bool|`Enable TLS for the connection to file metadata cache.`|`false`|
+|`OC_INSECURE`<br/>`OC_CACHE_TLS_INSECURE`<br/>`GATEWAY_PROVIDER_CACHE_TLS_INSECURE`| next |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_CACHE_TLS_ROOT_CA_CERTIFICATE`<br/>`GATEWAY_PROVIDER_CACHE_TLS_ROOT_CA_CERTIFICATE`| next |string|`The root CA certificate used to validate the server's TLS certificate. If provided GATEWAY_PROVIDER_CACHE_TLS_INSECURE will be seen as false.`|``|
+|`OC_CACHE_STORE`<br/>`GATEWAY_CREATE_HOME_CACHE_STORE`| 1.0.0 |string|`The type of the cache store. Supported values are: 'memory', 'redis-sentinel', 'nats-js-kv', 'noop'. See the text description for details.`|`memory`|
+|`OC_CACHE_STORE_NODES`<br/>`GATEWAY_CREATE_HOME_CACHE_STORE_NODES`| 1.0.0 |[]string|`A list of nodes to access the configured store. This has no effect when 'memory' store is configured. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details.`|`[127.0.0.1:9233]`|
+|`OC_CACHE_DATABASE`| 1.0.0 |string|`The database name the configured store should use.`|`cache-createhome`|
+|`OC_CACHE_TTL`<br/>`GATEWAY_CREATE_HOME_CACHE_TTL`| 1.0.0 |Duration|`Default time to live for user info in the cache. Only applied when access tokens has no expiration. See the Environment Variable Types description for more details.`|`5m0s`|
+|`OC_CACHE_DISABLE_PERSISTENCE`<br/>`GATEWAY_CREATE_HOME_CACHE_DISABLE_PERSISTENCE`| 1.0.0 |bool|`Disables persistence of the create home cache. Only applies when store type 'nats-js-kv' is configured. Defaults to false.`|`false`|
+|`OC_CACHE_AUTH_USERNAME`<br/>`GATEWAY_CREATE_HOME_CACHE_AUTH_USERNAME`| 1.0.0 |string|`The username to use for authentication. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_CACHE_AUTH_PASSWORD`<br/>`GATEWAY_CREATE_HOME_CACHE_AUTH_PASSWORD`| 1.0.0 |string|`The password to use for authentication. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_CACHE_ENABLE_TLS`<br/>`GATEWAY_CREATE_HOME_CACHE_ENABLE_TLS`| next |bool|`Enable TLS for the connection to file metadata cache.`|`false`|
+|`OC_INSECURE`<br/>`OC_CACHE_TLS_INSECURE`<br/>`GATEWAY_CREATE_HOME_CACHE_TLS_INSECURE`| next |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_CACHE_TLS_ROOT_CA_CERTIFICATE`<br/>`GATEWAY_CREATE_HOME_CACHE_TLS_ROOT_CA_CERTIFICATE`| next |string|`The root CA certificate used to validate the server's TLS certificate. If provided GATEWAY_CREATE_HOME_CACHE_TLS_INSECURE will be seen as false.`|``|
+|`OC_URL`<br/>`GATEWAY_FRONTEND_PUBLIC_URL`| 1.0.0 |string|`The public facing URL of the OpenCloud frontend.`|`https://localhost:9200`|
+|`GATEWAY_USERS_ENDPOINT`| 1.0.0 |string|`The endpoint of the users service. Can take a service name or a gRPC URI with the dns, kubernetes or unix protocol.`|`eu.opencloud.api.users`|
+|`GATEWAY_GROUPS_ENDPOINT`| 1.0.0 |string|`The endpoint of the groups service. Can take a service name or a gRPC URI with the dns, kubernetes or unix protocol.`|`eu.opencloud.api.groups`|
+|`GATEWAY_PERMISSIONS_ENDPOINT`| 1.0.0 |string|`The endpoint of the permissions service. Can take a service name or a gRPC URI with the dns, kubernetes or unix protocol.`|`eu.opencloud.api.settings`|
+|`GATEWAY_SHARING_ENDPOINT`| 1.0.0 |string|`The endpoint of the shares service. Can take a service name or a gRPC URI with the dns, kubernetes or unix protocol.`|`eu.opencloud.api.sharing`|
+|`GATEWAY_AUTH_APP_ENDPOINT`| 1.0.0 |string|`The endpoint of the auth-app service. Can take a service name or a gRPC URI with the dns, kubernetes or unix protocol.`|`eu.opencloud.api.auth-app`|
+|`GATEWAY_AUTH_BASIC_ENDPOINT`| 1.0.0 |string|`The endpoint of the auth-basic service. Can take a service name or a gRPC URI with the dns, kubernetes or unix protocol.`|`eu.opencloud.api.auth-basic`|
+|`GATEWAY_AUTH_BEARER_ENDPOINT`| 1.0.0 |string|`The endpoint of the auth-bearer service. Can take a service name or a gRPC URI with the dns, kubernetes or unix protocol.`|``|
+|`GATEWAY_AUTH_MACHINE_ENDPOINT`| 1.0.0 |string|`The endpoint of the auth-machine service. Can take a service name or a gRPC URI with the dns, kubernetes or unix protocol.`|`eu.opencloud.api.auth-machine`|
+|`GATEWAY_AUTH_SERVICE_ENDPOINT`| 1.0.0 |string|`The endpoint of the auth-service service. Can take a service name or a gRPC URI with the dns, kubernetes or unix protocol.`|`eu.opencloud.api.auth-service`|
+|`GATEWAY_STORAGE_PUBLIC_LINK_ENDPOINT`| 1.0.0 |string|`The endpoint of the storage-publiclink service. Can take a service name or a gRPC URI with the dns, kubernetes or unix protocol.`|`eu.opencloud.api.storage-publiclink`|
+|`GATEWAY_STORAGE_USERS_ENDPOINT`| 1.0.0 |string|`The endpoint of the storage-users service. Can take a service name or a gRPC URI with the dns, kubernetes or unix protocol.`|`eu.opencloud.api.storage-users`|
+|`GATEWAY_STORAGE_SHARES_ENDPOINT`| 1.0.0 |string|`The endpoint of the storage-shares service. Can take a service name or a gRPC URI with the dns, kubernetes or unix protocol.`|`eu.opencloud.api.storage-shares`|
+|`GATEWAY_APP_REGISTRY_ENDPOINT`| 1.0.0 |string|`The endpoint of the app-registry service. Can take a service name or a gRPC URI with the dns, kubernetes or unix protocol.`|`eu.opencloud.api.app-registry`|
+|`GATEWAY_OCM_ENDPOINT`| 1.0.0 |string|`The endpoint of the ocm service. Can take a service name or a gRPC URI with the dns, kubernetes or unix protocol.`|`eu.opencloud.api.ocm`|
+|`GATEWAY_STORAGE_REGISTRY_DRIVER`| 1.0.0 |string|`The driver name of the storage registry to use.`|`spaces`|
+|`GATEWAY_STORAGE_REGISTRY_RULES`| 1.0.0 |[]string|`The rules for the storage registry. See the Environment Variable Types description for more details.`|`[]`|
+|`GATEWAY_STORAGE_REGISTRY_CONFIG_JSON`| 1.0.0 |string|`Additional configuration for the storage registry in json format.`|``|
+|`GATEWAY_STORAGE_USERS_MOUNT_ID`| 1.0.0 |string|`Mount ID of this storage. Admins can set the ID for the storage in this config option manually which is then used to reference the storage. Any reasonable long string is possible, preferably this would be an UUIDv4 format.`|``|
diff --git a/versioned_docs/version-7.x/_static/env-vars/gateway_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/gateway_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/gateway_readme.md b/versioned_docs/version-7.x/_static/env-vars/gateway_readme.md
new file mode 100755
index 000000000..47b4707c5
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/gateway_readme.md
@@ -0,0 +1,186 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The gateway service is responsible for passing requests to the storage providers. Other services never talk to the storage providers directly but will always send their requests via the `gateway` service.
+
+
+## Table of Contents
+
+* [Caching](#caching)
+* [Service Endpoints](#service-endpoints)
+* [Storage Registry](#storage-registry)
+
+## Caching
+
+The gateway service is using caching as it is highly frequented with the same requests. As of now it uses two different caches:
+  -   the `provider cache` is caching requests to list or get storage providers.
+  -   the `create home cache` is caching requests to create personal spaces (as they only need to be executed once).
+
+Both caches can be configured via the `OC_CACHE_*` envvars (or `GATEWAY_PROVIDER_CACHE_*` and `GATEWAY_CREATE_HOME_CACHE_*` respectively).
+
+Use `OC_CACHE_STORE` (`GATEWAY_PROVIDER_CACHE_STORE`, `GATEWAY_CREATE_HOME_CACHE_STORE`) to define the type of cache to use:
+  -   `memory`: Basic in-memory store and the default.
+  -   `redis-sentinel`: Stores data in a configured Redis Sentinel cluster.
+  -   `nats-js-kv`: Stores data using key-value-store feature of [nats jetstream](https://docs.nats.io/nats-concepts/jetstream/key-value-store)
+  -   `noop`: Stores nothing. Useful for testing. Not recommended in production environments.
+
+Other store types may work but are not supported currently.
+
+Note: The service can only be scaled if not using `memory` store and the stores are configured identically over all instances!
+
+Note that if you have used one of the deprecated stores, you should reconfigure to one of the supported ones as the deprecated stores will be removed in a later version.
+
+Store specific notes:
+  -   When using `redis-sentinel`, the Redis master to use is configured via e.g. `OC_CACHE_STORE_NODES` in the form of `<sentinel-host>:<sentinel-port>/<redis-master>` like `10.10.0.200:26379/mymaster`.
+  -   When using `nats-js-kv` it is recommended to set `OC_CACHE_STORE_NODES` to the same value as `OC_EVENTS_ENDPOINT`. That way the cache uses the same nats instance as the event bus.
+  -   When using the `nats-js-kv` store, it is possible to set `OC_CACHE_DISABLE_PERSISTENCE` to instruct nats to not persist cache data on disc.
+
+## Service Endpoints
+
+**IMPORTANT**\
+This functionality is currently highly experimental and intended for testing only! There are known bugs that need to be sorted out like not removing sockets when a service ends.
+
+The gateway acts as a proxy for other CS3 services. As such it has to forward requests to a lot of services and needs to establish connections by looking up the IP address using the service registry. Instead of using the service registry each endpoint can also be configured to use the grpc `dns://` or `kubernetes://` URLs, which might be useful when running in kubernetes.
+
+For a local single node deployment you might want to use `unix:` sockets as shown below. Using unix sockets will reduce the amount of service lookups and omit the TCP stack. For now, this is experimental and the services do not delete the socket on shutdown. PRs welcome.
+
+The scheme for this setup is the following. Note that there is, except storage, always a service and a gateway envvar triple:
+
+| **envvar** | **default** | **alternative** |
+|------|------|------|
+| OC_GRPC_PROTOCOL or <br /> `<service>`_GRPC_PROTOCOL | tcp | unix |
+| `<service>`_GRPC_ADDR | 127.0.0.1:`<port>` | /var/run/opencloud/`<service>`.sock |
+| GATEWAY_`<service>`_ENDPOINT | eu.opencloud.api.`<service>` | unix:/var/run/opencloud/`<service>`.sock <br /> dns: ... <br /> kubernetes: ... |
+
+```console
+USERS_GRPC_PROTOCOL=unix"
+USERS_GRPC_ADDR=/var/run/opencloud/users.sock"
+GATEWAY_USERS_ENDPOINT=unix:/var/run/opencloud/users.sock"
+
+GROUPS_GRPC_PROTOCOL=unix"
+GROUPS_GRPC_ADDR=/var/run/opencloud/groups.sock"
+GATEWAY_GROUPS_ENDPOINT=unix:/var/run/opencloud/groups.sock"
+
+AUTH_APP_GRPC_PROTOCOL=unix"
+AUTH_APP_GRPC_ADDR=/var/run/opencloud/auth-app.sock"
+GATEWAY_AUTH_APP_ENDPOINT=unix:/var/run/opencloud/auth-app.sock"
+
+AUTH_BASIC_GRPC_PROTOCOL=unix"
+AUTH_BASIC_GRPC_ADDR=/var/run/opencloud/auth-basic.sock"
+GATEWAY_AUTH_BASIC_ENDPOINT=unix:/var/run/opencloud/auth-basic.sock"
+
+AUTH_MACHINE_GRPC_PROTOCOL=unix"
+AUTH_MACHINE_GRPC_ADDR=/var/run/opencloud/auth-machine.sock"
+GATEWAY_AUTH_MACHINE_ENDPOINT=unix:/var/run/opencloud/auth-machine.sock"
+
+AUTH_SERVICE_GRPC_PROTOCOL=unix"
+AUTH_SERVICE_GRPC_ADDR=/var/run/opencloud/auth-service.sock"
+GATEWAY_AUTH_SERVICE_ENDPOINT=unix:/var/run/opencloud/auth-service.sock"
+
+STORAGE_PUBLIC_LINK_GRPC_PROTOCOL=unix"
+STORAGE_PUBLIC_LINK_GRPC_ADDR=/var/run/opencloud/storage-public-link.sock"
+GATEWAY_STORAGE_PUBLIC_LINK_ENDPOINT=unix:/var/run/opencloud/storage-public-link.sock"
+
+STORAGE_USERS_GRPC_PROTOCOL=unix"
+STORAGE_USERS_GRPC_ADDR=/var/run/opencloud/storage-users.sock"
+GATEWAY_STORAGE_USERS_ENDPOINT=unix:/var/run/opencloud/storage-users.sock"
+// graph sometimes bypasses the gateway so we need to configure the socket here as wel
+GRAPH_SPACES_STORAGE_USERS_ADDRESS=unix:/var/run/opencloud/storage-users.sock"
+
+STORAGE_SHARES_GRPC_PROTOCOL=unix"
+STORAGE_SHARES_GRPC_ADDR=/var/run/opencloud/storage-shares.sock"
+GATEWAY_STORAGE_SHARES_ENDPOINT=unix:/var/run/opencloud/storage-shares.sock"
+
+APP_REGISTRY_GRPC_PROTOCOL=unix"
+APP_REGISTRY_GRPC_ADDR=/var/run/opencloud/app-registry.sock"
+GATEWAY_APP_REGISTRY_ENDPOINT=unix:/var/run/opencloud/app-registry.sock"
+
+OCM_GRPC_PROTOCOL=unix"
+OCM_GRPC_ADDR=/var/run/opencloud/ocm.sock"
+GATEWAY_OCM_ENDPOINT=unix:/var/run/opencloud/ocm.sock"
+
+// storage related
+SETTINGS_STORAGE_GATEWAY_GRPC_ADDR="unix:/var/run/opencloud/storage-system.sock"
+SETTINGS_STORAGE_GRPC_ADDR="unix:/var/run/opencloud/storage-system.sock"
+STORAGE_SYSTEM_GRPC_PROTOCOL="unix"
+STORAGE_SYSTEM_GRPC_ADDR="/var/run/opencloud/storage-system.sock"
+SHARING_USER_CS3_PROVIDER_ADDR="unix:/var/run/opencloud/storage-system.sock"
+SHARING_USER_JSONCS3_PROVIDER_ADDR="unix:/var/run/opencloud/storage-system.sock"
+SHARING_PUBLIC_CS3_PROVIDER_ADDR="unix:/var/run/opencloud/storage-system.sock"
+SHARING_PUBLIC_JSONCS3_PROVIDER_ADDR="unix:/var/run/opencloud/storage-system.sock"
+```
+
+## Storage Registry
+
+In order to add another storage provider the CS3 storage registry that is running as part of the CS3 gateway has to be made aware of it. The easiest and cleanest way to do it is to set `GATEWAY_STORAGE_REGISTRY_CONFIG_JSON=/path/to/storages.json` and list all storage providers like this:
+
+```json
+{
+  "eu.opencloud.api.storage-users": {
+    "providerid": "{storage-users-mount-uuid}",
+    "spaces": {
+      "personal": {
+        "mount_point":   "/users",
+        "path_template": "/users/{{.Space.Owner.Id.OpaqueId}}"
+      },
+      "project": {
+        "mount_point":   "/projects",
+        "path_template": "/projects/{{.Space.Name}}"
+      }
+    }
+  },
+  "eu.opencloud.api.storage-shares": {
+    "providerid": "a0ca6a90-a365-4782-871e-d44447bbc668",
+    "spaces": {
+      "virtual": {
+        "mount_point": "/users/{{.CurrentUser.Id.OpaqueId}}/Shares"
+      },
+      "grant": {
+        "mount_point": "."
+      },
+      "mountpoint": {
+        "mount_point":   "/users/{{.CurrentUser.Id.OpaqueId}}/Shares",
+        "path_template": "/users/{{.CurrentUser.Id.OpaqueId}}/Shares/{{.Space.Name}}"
+      }
+    }
+  },
+  "eu.opencloud.api.storage-publiclink": {
+    "providerid": "7993447f-687f-490d-875c-ac95e89a62a4",
+    "spaces": {
+      "grant": {
+        "mount_point": "."
+      },
+      "mountpoint": {
+        "mount_point":   "/public",
+        "path_template": "/public/{{.Space.Root.OpaqueId}}"
+      }
+    }
+  },
+  "eu.opencloud.api.ocm": {
+    "providerid": "89f37a33-858b-45fa-8890-a1f2b27d90e1",
+    "spaces": {
+      "grant": {
+        "mount_point": "."
+      },
+      "mountpoint": {
+        "mount_point":   "/ocm",
+        "path_template": "/ocm/{{.Space.Root.OpaqueId}}"
+      }
+    }
+  },
+  "eu.opencloud.api.storage-hello": {
+    "providerid": "hello-storage-id",
+    "spaces": {
+      "project": {
+        "mount_point":   "/hello",
+        "path_template": "/hello/{{.Space.Name}}"
+      }
+    }
+  }
+}
+```
+
+In the above replace `{storage-users-mount-uuid}` with the mount UUID that was generated for the storage-users service. You can find it in the `config.yaml` generated on by `opencloud init`. The last entry `eu.opencloud.api.storage-hello` and its `providerid` `"hello-storage-id"` are an example for an additional storage provider, in this case running `hellofs`, an example minimal storage driver.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/global_configvars.md b/versioned_docs/version-7.x/_static/env-vars/global_configvars.md
new file mode 100644
index 000000000..24c2ef591
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/global_configvars.md
@@ -0,0 +1,120 @@
+# Environment variables with global scope available in multiple services
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|---|
+| `IDM_CREATE_DEMO_USERS` | 1.0.0 | bool | The default role assignments the demo users should be setup. | false |
+| `OC_ADMIN_USER_ID` | 1.0.0 | string | ID of the user that should receive admin privileges. Consider that the UUID can be encoded in some LDAP deployment configurations like in .ldif files. These need to be decoded beforehand. |  |
+| `OC_ASYNC_UPLOADS` | 1.0.0 | bool | Enable asynchronous file uploads. | true |
+| `OC_CACHE_AUTH_PASSWORD` | 1.0.0 | string | The password to use for authentication. Only applies when using the 'nats-js-kv' store type. |  |
+| `OC_CACHE_AUTH_USERNAME` | 1.0.0 | string | The username to use for authentication. Only applies when using the 'nats-js-kv' store type. |  |
+| `OC_CACHE_DATABASE` | 1.0.0 | string | The database name the configured store should use. | cache-stat |
+| `OC_CACHE_DISABLE_PERSISTENCE` | 1.0.0 | bool | Disable persistence of the cache. Only applies when using the 'nats-js-kv' store type. Defaults to false. | false |
+| `OC_CACHE_ENABLE_TLS` | next | bool | Enable TLS for the connection to file metadata cache. | false |
+| `OC_CACHE_STORE` | 1.0.0 | string | The type of the cache store. Supported values are: 'memory', 'redis-sentinel', 'nats-js-kv', 'noop'. See the text description for details. | memory |
+| `OC_CACHE_STORE_NODES` | 1.0.0 | []string | A list of nodes to access the configured store. This has no effect when 'memory' store is configured. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details. | [127.0.0.1:9233] |
+| `OC_CACHE_TLS_INSECURE` | next | bool | Whether to verify the server TLS certificates. | false |
+| `OC_CACHE_TLS_ROOT_CA_CERTIFICATE` | next | string | The root CA certificate used to validate the server's TLS certificate. If provided FRONTEND_OCS_STAT_CACHE_TLS_INSECURE will be seen as false. |  |
+| `OC_CACHE_TTL` | 1.0.0 | Duration | Default time to live for user info in the cache. Only applied when access tokens has no expiration. See the Environment Variable Types description for more details. | 5m0s |
+| `OC_CORS_ALLOW_CREDENTIALS` | 1.0.0 | bool | Allow credentials for CORS.See following chapter for more details: *Access-Control-Allow-Credentials* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Credentials. | false |
+| `OC_CORS_ALLOW_HEADERS` | 1.0.0 | []string | A list of allowed CORS headers. See following chapter for more details: *Access-Control-Request-Headers* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Headers. See the Environment Variable Types description for more details. | [Origin Accept Content-Type Depth Authorization Ocs-Apirequest If-None-Match If-Match Destination Overwrite X-Request-Id X-Requested-With Tus-Resumable Tus-Checksum-Algorithm Upload-Concat Upload-Length Upload-Metadata Upload-Defer-Length Upload-Expires Upload-Checksum Upload-Offset X-HTTP-Method-Override Cache-Control] |
+| `OC_CORS_ALLOW_METHODS` | 1.0.0 | []string | A list of allowed CORS methods. See following chapter for more details: *Access-Control-Request-Method* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Method. See the Environment Variable Types description for more details. | [OPTIONS HEAD GET PUT POST PATCH DELETE MKCOL PROPFIND PROPPATCH MOVE COPY REPORT SEARCH] |
+| `OC_CORS_ALLOW_ORIGINS` | 1.0.0 | []string | A list of allowed CORS origins. See following chapter for more details: *Access-Control-Allow-Origin* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin. See the Environment Variable Types description for more details. | [https://localhost:9200] |
+| `OC_DECOMPOSEDFS_PROPAGATOR` | 1.0.0 | string | The propagator used for decomposedfs. At the moment, only 'sync' is fully supported, 'async' is available as an experimental option. | sync |
+| `OC_DEFAULT_LANGUAGE` | 1.0.0 | string | The default language used by services and the WebUI. If not defined, English will be used as default. See the documentation for more details. |  |
+| `OC_DISABLE_VERSIONING` | 1.0.0 | bool | Disables versioning of files. When set to true, new uploads with the same filename will overwrite existing files instead of creating a new version. | false |
+| `OC_ENABLE_OCM` | 1.0.0 | bool | Changing this value is NOT supported. Enables support for incoming federated sharing for clients. The backend behaviour is not changed. | false |
+| `OC_EVENTS_AUTH_PASSWORD` | 1.0.0 | string | The password to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services. |  |
+| `OC_EVENTS_AUTH_USERNAME` | 1.0.0 | string | The username to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services. |  |
+| `OC_EVENTS_CLUSTER` | 1.0.0 | string | The clusterID of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture. Mandatory when using NATS as event system. | opencloud-cluster |
+| `OC_EVENTS_ENABLE_TLS` | 1.0.0 | bool | Enable TLS for the connection to the events broker. The events broker is the OpenCloud service which receives and delivers events between the services. | false |
+| `OC_EVENTS_ENDPOINT` | 1.0.0 | string | The address of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture. | 127.0.0.1:9233 |
+| `OC_EVENTS_TLS_INSECURE` | 1.0.0 | bool | Whether to verify the server TLS certificates. | false |
+| `OC_EVENTS_TLS_ROOT_CA_CERTIFICATE` | 1.0.0 | string | The root CA certificate used to validate the server's TLS certificate. If provided NOTIFICATIONS_EVENTS_TLS_INSECURE will be seen as false. |  |
+| `OC_GATEWAY_GRPC_ADDR` | 1.0.0 | string | The bind address of the GRPC service. | 127.0.0.1:9142 |
+| `OC_GRPC_CLIENT_TLS_CACERT` | 1.0.0 | string | Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services. |  |
+| `OC_GRPC_CLIENT_TLS_MODE` | 1.0.0 | string | TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification. |  |
+| `OC_GRPC_PROTOCOL` | 1.0.0 | string | The transport protocol of the GRPC service. | tcp |
+| `OC_HTTP_TLS_CERTIFICATE` | 1.0.0 | string | Path/File name of the TLS server certificate (in PEM format) for the http services. |  |
+| `OC_HTTP_TLS_ENABLED` | 1.0.0 | bool | Activates TLS for the http based services using the server certifcate and key configured via OC_HTTP_TLS_CERTIFICATE and OC_HTTP_TLS_KEY. If OC_HTTP_TLS_CERTIFICATE is not set a temporary server certificate is generated - to be used with PROXY_INSECURE_BACKEND=true. | false |
+| `OC_HTTP_TLS_KEY` | 1.0.0 | string | Path/File name for the TLS certificate key (in PEM format) for the server certificate to use for the http services. |  |
+| `OC_INSECURE` | 1.0.0 | bool | Allow insecure connections to the frontend. | false |
+| `OC_JWT_SECRET` | 1.0.0 | string | The secret to mint and validate jwt tokens. |  |
+| `OC_KEYCLOAK_BASE_PATH` | 1.0.0 | string | The URL to access keycloak. |  |
+| `OC_KEYCLOAK_CLIENT_ID` | 1.0.0 | string | The client ID to authenticate with keycloak. |  |
+| `OC_KEYCLOAK_CLIENT_REALM` | 1.0.0 | string | The realm the client is defined in. |  |
+| `OC_KEYCLOAK_CLIENT_SECRET` | 1.0.0 | string | The client secret to use in authentication. |  |
+| `OC_KEYCLOAK_INSECURE_SKIP_VERIFY` | 1.0.0 | bool | Disable TLS certificate validation for Keycloak connections. Do not set this in production environments. | false |
+| `OC_KEYCLOAK_USER_REALM` | 1.0.0 | string | The realm users are defined. |  |
+| `OC_LDAP_BIND_DN` | 1.0.0 | string | LDAP DN to use for simple bind authentication with the target LDAP server. | uid=idp,ou=sysusers,o=libregraph-idm |
+| `OC_LDAP_BIND_PASSWORD` | 1.0.0 | string | Password to use for authenticating the 'bind_dn'. |  |
+| `OC_LDAP_CACERT` | 1.0.0 | string | Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the LDAP service. If not defined, the root directory derives from $OC_BASE_DATA_PATH/idp. |  |
+| `OC_LDAP_DISABLED_USERS_GROUP_DN` | 1.0.0 | string | The distinguished name of the group to which added users will be classified as disabled when 'disable_user_mechanism' is set to 'group'. | cn=DisabledUsersGroup,ou=groups,o=libregraph-idm |
+| `OC_LDAP_DISABLE_USER_MECHANISM` | 1.0.0 | string | An option to control the behavior for disabling users. Valid options are 'none', 'attribute' and 'group'. If set to 'group', disabling a user via API will add the user to the configured group for disabled users, if set to 'attribute' this will be done in the ldap user entry, if set to 'none' the disable request is not processed. | attribute |
+| `OC_LDAP_GROUP_BASE_DN` | 1.0.0 | string | Search base DN for looking up LDAP groups. | ou=groups,o=libregraph-idm |
+| `OC_LDAP_GROUP_FILTER` | 1.0.0 | string | LDAP filter to add to the default filters for group searches. |  |
+| `OC_LDAP_GROUP_OBJECTCLASS` | 1.0.0 | string | The object class to use for groups in the default group search filter ('groupOfNames'). | groupOfNames |
+| `OC_LDAP_GROUP_SCHEMA_DISPLAYNAME` | 1.0.0 | string | LDAP Attribute to use for the displayname of groups (often the same as groupname attribute). | cn |
+| `OC_LDAP_GROUP_SCHEMA_GROUPNAME` | 1.0.0 | string | LDAP Attribute to use for the name of groups. | cn |
+| `OC_LDAP_GROUP_SCHEMA_ID` | 1.0.0 | string | LDAP Attribute to use as the unique id for groups. This should be a stable globally unique id (e.g. a UUID). | openCloudUUID |
+| `OC_LDAP_GROUP_SCHEMA_ID_IS_OCTETSTRING` | 1.0.0 | bool | Set this to true if the defined 'id' attribute for groups is of the 'OCTETSTRING' syntax. This is e.g. required when using the 'objectGUID' attribute of Active Directory for the group IDs. | false |
+| `OC_LDAP_GROUP_SCHEMA_MAIL` | 1.0.0 | string | LDAP Attribute to use for the email address of groups (can be empty). | mail |
+| `OC_LDAP_GROUP_SCHEMA_MEMBER` | 1.0.0 | string | LDAP Attribute that is used for group members. | member |
+| `OC_LDAP_GROUP_SCOPE` | 1.0.0 | string | LDAP search scope to use when looking up groups. Supported values are 'base', 'one' and 'sub'. | sub |
+| `OC_LDAP_INSECURE` | 1.0.0 | bool | Disable TLS certificate validation for the LDAP connections. Do not set this in production environments. | false |
+| `OC_LDAP_SERVER_WRITE_ENABLED` | 1.0.0 | bool | Allow creating, modifying and deleting LDAP users via the GRAPH API. This can only be set to 'true' when keeping default settings for the LDAP user and group attribute types (the 'OC_LDAP_USER_SCHEMA_* and 'OC_LDAP_GROUP_SCHEMA_* variables). | true |
+| `OC_LDAP_URI` | 1.0.0 | string | Url of the LDAP service to use as IDP. | ldap://localhost:9236 |
+| `OC_LDAP_USER_BASE_DN` | 1.0.0 | string | Search base DN for looking up LDAP users. | ou=users,o=libregraph-idm |
+| `OC_LDAP_USER_ENABLED_ATTRIBUTE` | 1.0.0 | string | LDAP Attribute to use as a flag telling if the user is enabled or disabled. | openCloudUserEnabled |
+| `OC_LDAP_USER_FILTER` | 1.0.0 | string | LDAP filter to add to the default filters for user search like '(objectclass=openCloudUser)'. |  |
+| `OC_LDAP_USER_OBJECTCLASS` | 1.0.0 | string | LDAP User ObjectClass like 'inetOrgPerson'. | inetOrgPerson |
+| `OC_LDAP_USER_SCHEMA_DISPLAYNAME` | 1.0.0 | string | LDAP Attribute to use for the displayname of users. | displayname |
+| `OC_LDAP_USER_SCHEMA_ID` | 1.0.0 | string | LDAP User UUID attribute like 'uid'. | openCloudUUID |
+| `OC_LDAP_USER_SCHEMA_ID_IS_OCTETSTRING` | 1.0.0 | bool | Set this to true if the defined 'ID' attribute for users is of the 'OCTETSTRING' syntax. This is e.g. required when using the 'objectGUID' attribute of Active Directory for the user IDs. | false |
+| `OC_LDAP_USER_SCHEMA_MAIL` | 1.0.0 | string | LDAP User email attribute like 'mail'. | mail |
+| `OC_LDAP_USER_SCHEMA_TENANT_ID` | 4.0.0 | string | LDAP Attribute to use for the tenant ID of users. This is used to identify the tenant of a user in a multi-tenant environment. |  |
+| `OC_LDAP_USER_SCHEMA_USERNAME` | 1.0.0 | string | LDAP User name attribute like 'displayName'. | displayName |
+| `OC_LDAP_USER_SCHEMA_USER_TYPE` | 1.0.0 | string | LDAP Attribute to distinguish between 'Member' and 'Guest' users. Default is 'openCloudUserType'. | openCloudUserType |
+| `OC_LDAP_USER_SCOPE` | 1.0.0 | string | LDAP search scope to use when looking up users. Supported scopes are 'base', 'one' and 'sub'. | sub |
+| `OC_LOG_LEVEL` | 1.0.0 | string | The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'. | error |
+| `OC_MACHINE_AUTH_API_KEY` | 1.0.0 | string | The machine auth API key used to validate internal requests necessary to access resources from other services. |  |
+| `OC_MAX_CONCURRENCY` | 1.0.0 | int | Maximum number of concurrent go-routines. Higher values can potentially get work done faster but will also cause more load on the system. Values of 0 or below will be ignored and the default value will be used. | 1 |
+| `OC_OIDC_CLIENT_ID` | 1.0.0 | string | The OIDC client ID which OpenCloud Web uses. This client needs to be set up in your IDP. Note that this setting has no effect when using the builtin IDP. | web |
+| `OC_OIDC_CLIENT_SCOPES` | 6.0.0 | []string | The OIDC client scopes the Android app should request. | [openid profile email offline_access] |
+| `OC_OIDC_ISSUER` | 1.0.0 | string | URL of the OIDC issuer. It defaults to URL of the builtin IDP. | https://localhost:9200 |
+| `OC_PASSWORD_POLICY_BANNED_PASSWORDS_LIST` | 1.0.0 | string | Path to the 'banned passwords list' file. This only impacts public link password validation. See the documentation for more details. |  |
+| `OC_PASSWORD_POLICY_DISABLED` | 1.0.0 | bool | Disable the password policy. Defaults to false if not set. | false |
+| `OC_PASSWORD_POLICY_MIN_CHARACTERS` | 1.0.0 | int | Define the minimum password length. Defaults to 8 if not set. | 8 |
+| `OC_PASSWORD_POLICY_MIN_DIGITS` | 1.0.0 | int | Define the minimum number of digits. Defaults to 1 if not set. | 1 |
+| `OC_PASSWORD_POLICY_MIN_LOWERCASE_CHARACTERS` | 1.0.0 | int | Define the minimum number of uppercase letters. Defaults to 1 if not set. | 1 |
+| `OC_PASSWORD_POLICY_MIN_SPECIAL_CHARACTERS` | 1.0.0 | int | Define the minimum number of characters from the special characters list to be present. Defaults to 1 if not set. | 1 |
+| `OC_PASSWORD_POLICY_MIN_UPPERCASE_CHARACTERS` | 1.0.0 | int | Define the minimum number of lowercase letters. Defaults to 1 if not set. | 1 |
+| `OC_PERSISTENT_STORE` | 1.0.0 | string | The type of the store. Supported values are: 'memory', 'nats-js-kv', 'redis-sentinel', 'noop'. See the text description for details. | memory |
+| `OC_PERSISTENT_STORE_AUTH_PASSWORD` | 1.0.0 | string | The password to authenticate with the store. Only applies when store type 'nats-js-kv' is configured. |  |
+| `OC_PERSISTENT_STORE_AUTH_USERNAME` | 1.0.0 | string | The username to authenticate with the store. Only applies when store type 'nats-js-kv' is configured. |  |
+| `OC_PERSISTENT_STORE_ENABLE_TLS` | next | bool | Enable TLS for the connection to the store. Only applies when store type 'nats-js-kv' is configured. | false |
+| `OC_PERSISTENT_STORE_NODES` | 1.0.0 | []string | A list of nodes to access the configured store. This has no effect when 'memory' store is configured. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details. | [] |
+| `OC_PERSISTENT_STORE_TLS_INSECURE` | next | bool | Whether to verify the server TLS certificates. | false |
+| `OC_PERSISTENT_STORE_TLS_ROOT_CA_CERTIFICATE` | next | string | The root CA certificate used to validate the server's TLS certificate. If provided USERLOG_STORE_TLS_INSECURE will be seen as false. |  |
+| `OC_PERSISTENT_STORE_TTL` | 1.0.0 | Duration | Time to live for events in the store. Defaults to '336h' (2 weeks). See the Environment Variable Types description for more details. | 336h0m0s |
+| `OC_REVA_GATEWAY` | 1.0.0 | string | The CS3 gateway endpoint. | eu.opencloud.api.gateway |
+| `OC_SERVICE_ACCOUNT_ID` | 1.0.0 | string | The ID of the service account the service should use. See the 'auth-service' service description for more details. |  |
+| `OC_SERVICE_ACCOUNT_SECRET` | 1.0.0 | string | The service account secret. |  |
+| `OC_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD` | 1.0.0 | bool | Set this to true if you want to enforce passwords on all public shares. | true |
+| `OC_SHARING_PUBLIC_WRITEABLE_SHARE_MUST_HAVE_PASSWORD` | 1.0.0 | bool | Set this to true if you want to enforce passwords for writable shares. Only effective if the setting for 'passwords on all public shares' is set to false. | false |
+| `OC_SHOW_USER_EMAIL_IN_RESULTS` | 1.0.0 | bool | Include user email addresses in responses. If absent or set to false emails will be omitted from results. Please note that admin users can always see all email addresses. | false |
+| `OC_SPACES_MAX_QUOTA` | 1.0.0 | uint64 | Set the global max quota value in bytes. A value of 0 equals unlimited. The value is provided via capabilities. | 0 |
+| `OC_SYSTEM_USER_API_KEY` | 1.0.0 | string | API key for the STORAGE-SYSTEM system user. |  |
+| `OC_SYSTEM_USER_ID` | 1.0.0 | string | ID of the OpenCloud STORAGE-SYSTEM system user. Admins need to set the ID for the STORAGE-SYSTEM system user in this config option which is then used to reference the user. Any reasonable long string is possible, preferably this would be an UUIDv4 format. |  |
+| `OC_SYSTEM_USER_IDP` | 1.0.0 | string | IDP of the OpenCloud STORAGE-SYSTEM system user. | internal |
+| `OC_TRANSFER_SECRET` | 1.0.0 | string | Transfer secret for signing file up- and download requests. |  |
+| `OC_TRANSLATION_PATH` | 1.0.0 | string | (optional) Set this to a path with custom translations to overwrite the builtin translations. Note that file and folder naming rules apply, see the documentation for more details. |  |
+| `OC_URL` | 1.0.0 | string | The public facing URL of the OpenCloud frontend. | https://localhost:9200 |
+| `OC_WOPI_DISABLE_CHAT` | 1.0.0 | bool | Disable the chat functionality of the office app. | false |
+| `SEARCH_EVENTS_ACK_WAIT` | 4.0.0 | Duration | The time to wait for an ack before the message is redelivered. This is used to ensure that messages are not lost if the consumer crashes. | 1m0s |
+| `SEARCH_EVENTS_MAX_ACK_PENDING` | 4.0.0 | int | The maximum number of unacknowledged messages. This is used to limit the number of messages that can be in flight at the same time. | 10000 |
+| `STORAGE_GATEWAY_GRPC_ADDR` | 1.0.0 | string | GRPC address of the STORAGE-SYSTEM service. | eu.opencloud.api.storage-system |
+| `STORAGE_GRPC_ADDR` | 1.0.0 | string | GRPC address of the STORAGE-SYSTEM service. | eu.opencloud.api.storage-system |
+| `STORAGE_USERS_ASYNC_PROPAGATOR_PROPAGATION_DELAY` | 1.0.0 | Duration | The delay between a change made to a tree and the propagation start on treesize and treetime. Multiple propagations are computed to a single one. See the Environment Variable Types description for more details. | 0s |
+| `STORAGE_USERS_PERMISSION_ENDPOINT` | 1.0.0 | string | Endpoint of the permissions service. The endpoints can differ for 'decomposed' and 'decomposeds3'. | eu.opencloud.api.settings |
+| `WEB_OIDC_CLIENT_ID` | 1.0.0 | string | The OIDC client ID which OpenCloud Web uses. This client needs to be set up in your IDP. Note that this setting has no effect when using the builtin IDP. | web |
+| `WEB_OIDC_SCOPE` | 1.0.0 | string | OIDC scopes to request during authentication to authorize access to user details. Defaults to 'openid profile email'. Values are separated by blank. More example values but not limited to are 'address' or 'phone' etc. | openid profile email |
diff --git a/versioned_docs/version-7.x/_static/env-vars/graph.yaml b/versioned_docs/version-7.x/_static/env-vars/graph.yaml
new file mode 100644
index 000000000..845691247
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/graph.yaml
@@ -0,0 +1,166 @@
+# Autogenerated
+# Filename: graph.yaml
+
+loglevel: error
+cache:
+  store: memory
+  nodes:
+  - 127.0.0.1:9233
+  database: cache-roles
+  table: ""
+  ttl: 24h0m0s
+  disable_persistence: false
+  username: ""
+  password: ""
+  enable_tls: false
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+debug:
+  addr: 127.0.0.1:9124
+  token: ""
+  pprof: false
+  zpages: false
+http:
+  addr: 127.0.0.1:9120
+  root: /graph
+  tls:
+    enabled: false
+    cert: ""
+    key: ""
+  apitoken: ""
+  cors:
+    allow_origins:
+    - '*'
+    allow_methods:
+    - GET
+    - POST
+    - PUT
+    - PATCH
+    - DELETE
+    - OPTIONS
+    allow_headers:
+    - Authorization
+    - Origin
+    - Content-Type
+    - Accept
+    - X-Requested-With
+    - X-Request-Id
+    - Purge
+    - Restore
+    allow_credentials: true
+api:
+  group_members_patch_limit: 20
+  graph_username_match: default
+  graph_assign_default_user_role: true
+  graph_identity_search_min_length: 3
+  show_email_in_results: false
+reva:
+  address: eu.opencloud.api.gateway
+  tls:
+    mode: ""
+    cacert: ""
+token_manager:
+  jwt_secret: ""
+grpc_client_tls: null
+application:
+  id: ""
+  displayname: OpenCloud
+spaces:
+  webdav_base: https://localhost:9200
+  webdav_path: /dav/spaces/
+  default_quota: "1000000000"
+  extended_space_properties_cache_ttl: 60000000000
+  users_cache_ttl: 60000000000
+  groups_cache_ttl: 60000000000
+  storage_users_address: eu.opencloud.api.storage-users
+  default_language: ""
+  translation_path: ""
+identity:
+  backend: ldap
+  ldap:
+    uri: ldap://localhost:9236
+    cacert: ""
+    insecure: false
+    bind_dn: uid=libregraph,ou=sysusers,o=libregraph-idm
+    bind_password: ""
+    use_server_uuid: false
+    use_password_modify_exop: true
+    write_enabled: true
+    refint_enabled: false
+    user_base_dn: ou=users,o=libregraph-idm
+    user_search_scope: sub
+    user_filter: ""
+    user_objectclass: inetOrgPerson
+    user_mail_attribute: mail
+    user_displayname_attribute: displayName
+    user_name_attribute: uid
+    user_id_attribute: openCloudUUID
+    user_id_is_octet_string: false
+    user_type_attribute: openCloudUserType
+    user_enabled_attribute: openCloudUserEnabled
+    disable_user_mechanism: attribute
+    ldap_disabled_users_group_dn: cn=DisabledUsersGroup,ou=groups,o=libregraph-idm
+    group_base_dn: ou=groups,o=libregraph-idm
+    group_create_base_dn: ou=groups,o=libregraph-idm
+    group_search_scope: sub
+    group_filter: ""
+    group_objectclass: groupOfNames
+    group_name_attribute: cn
+    group_member_attribute: member
+    group_id_attribute: openCloudUUID
+    group_id_is_octet_string: false
+    education_resources_enabled: false
+    educationconfig:
+      school_base_dn: ""
+      school_search_scope: ""
+      school_filter: ""
+      school_objectclass: ""
+      school_name_attribute: ""
+      school_number_attribute: ""
+      school_id_attribute: ""
+      school_termination_min_grace_days: 0
+include_ocm_sharees: false
+events:
+  endpoint: 127.0.0.1:9233
+  cluster: opencloud-cluster
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+  enable_tls: false
+  username: ""
+  password: ""
+unified_roles:
+  available_roles:
+  - b1e2218d-eef8-4d4c-b82d-0f1a1b48f3b5
+  - a8d5fe5e-96e3-418d-825b-534dbdf22b99
+  - fb6c3e19-e378-47e5-b277-9732f9de6e21
+  - 58c63c02-1d89-4572-916a-870abc5a1b7d
+  - 2d00ce52-1fc2-4dbc-8b95-a73b73395f5a
+  - 1c996275-f1c9-4e71-abdf-a42f6495e960
+  - 312c0871-5ef7-4b3a-85b6-0e4074c64049
+max_concurrency: 20
+keycloak:
+  base_path: ""
+  client_id: ""
+  client_secret: ""
+  client_realm: ""
+  user_realm: ""
+  insecure_skip_verify: false
+service_account:
+  service_account_id: ""
+  service_account_secret: ""
+metadata_config:
+  gateway_addr: eu.opencloud.api.storage-system
+  storage_addr: eu.opencloud.api.storage-system
+  system_user_id: ""
+  system_user_idp: internal
+  system_user_api_key: ""
+user_soft_delete_retention_time: 0s
+store:
+  nodes:
+  - 127.0.0.1:9233
+  database: graph
+  username: ""
+  password: ""
+  enable_tls: false
+  tls_insecure: false
+  tls_root_ca_certificate: ""
diff --git a/versioned_docs/version-7.x/_static/env-vars/graph_configvars.md b/versioned_docs/version-7.x/_static/env-vars/graph_configvars.md
new file mode 100644
index 000000000..b3228de03
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/graph_configvars.md
@@ -0,0 +1,122 @@
+## Environment variables for the **graph** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`GRAPH_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`OC_CACHE_STORE`<br/>`GRAPH_CACHE_STORE`| 1.0.0 |string|`The type of the cache store. Supported values are: 'memory', 'redis-sentinel', 'nats-js-kv', 'noop'. See the text description for details.`|`memory`|
+|`OC_CACHE_STORE_NODES`<br/>`GRAPH_CACHE_STORE_NODES`| 1.0.0 |[]string|`A list of nodes to access the configured store. This has no effect when 'memory' store are configured. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details.`|`[127.0.0.1:9233]`|
+|`GRAPH_CACHE_STORE_DATABASE`| 1.0.0 |string|`The database name the configured store should use.`|`cache-roles`|
+|`GRAPH_CACHE_STORE_TABLE`| 1.0.0 |string|`The database table the store should use.`|``|
+|`OC_CACHE_TTL`<br/>`GRAPH_CACHE_TTL`| 1.0.0 |Duration|`Time to live for cache records in the graph. Defaults to '336h' (2 weeks). See the Environment Variable Types description for more details.`|`24h0m0s`|
+|`OC_CACHE_DISABLE_PERSISTENCE`<br/>`GRAPH_CACHE_DISABLE_PERSISTENCE`| 1.0.0 |bool|`Disables persistence of the cache. Only applies when store type 'nats-js-kv' is configured. Defaults to false.`|`false`|
+|`OC_CACHE_AUTH_USERNAME`<br/>`GRAPH_CACHE_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the cache. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_CACHE_AUTH_PASSWORD`<br/>`GRAPH_CACHE_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the cache. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_CACHE_ENABLE_TLS`<br/>`GRAPH_CACHE_ENABLE_TLS`| next |bool|`Enable TLS for the connection to file metadata cache.`|`false`|
+|`OC_INSECURE`<br/>`OC_CACHE_TLS_INSECURE`<br/>`GRAPH_CACHE_TLS_INSECURE`| next |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_CACHE_TLS_ROOT_CA_CERTIFICATE`<br/>`GRAPH_CACHE_TLS_ROOT_CA_CERTIFICATE`| next |string|`The root CA certificate used to validate the server's TLS certificate. If provided GRAPH_CACHE_TLS_INSECURE will be seen as false.`|``|
+|`GRAPH_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9124`|
+|`GRAPH_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`GRAPH_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`GRAPH_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`GRAPH_HTTP_ADDR`| 1.0.0 |string|`The bind address of the HTTP service.`|`127.0.0.1:9120`|
+|`GRAPH_HTTP_ROOT`| 1.0.0 |string|`Subdirectory that serves as the root for this HTTP service.`|`/graph`|
+|`OC_HTTP_TLS_ENABLED`| 1.0.0 |bool|`Activates TLS for the http based services using the server certifcate and key configured via OC_HTTP_TLS_CERTIFICATE and OC_HTTP_TLS_KEY. If OC_HTTP_TLS_CERTIFICATE is not set a temporary server certificate is generated - to be used with PROXY_INSECURE_BACKEND=true.`|`false`|
+|`OC_HTTP_TLS_CERTIFICATE`| 1.0.0 |string|`Path/File name of the TLS server certificate (in PEM format) for the http services.`|``|
+|`OC_HTTP_TLS_KEY`| 1.0.0 |string|`Path/File name for the TLS certificate key (in PEM format) for the server certificate to use for the http services.`|``|
+|`GRAPH_HTTP_API_TOKEN`| 1.0.0 |string|`An optional API bearer token`|``|
+|`OC_CORS_ALLOW_ORIGINS`<br/>`GRAPH_CORS_ALLOW_ORIGINS`| 1.0.0 |[]string|`A list of allowed CORS origins. See following chapter for more details: *Access-Control-Allow-Origin* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin. See the Environment Variable Types description for more details.`|`[*]`|
+|`OC_CORS_ALLOW_METHODS`<br/>`GRAPH_CORS_ALLOW_METHODS`| 1.0.0 |[]string|`A list of allowed CORS methods. See following chapter for more details: *Access-Control-Request-Method* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Method. See the Environment Variable Types description for more details.`|`[GET POST PUT PATCH DELETE OPTIONS]`|
+|`OC_CORS_ALLOW_HEADERS`<br/>`GRAPH_CORS_ALLOW_HEADERS`| 1.0.0 |[]string|`A list of allowed CORS headers. See following chapter for more details: *Access-Control-Request-Headers* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Headers. See the Environment Variable Types description for more details.`|`[Authorization Origin Content-Type Accept X-Requested-With X-Request-Id Purge Restore]`|
+|`OC_CORS_ALLOW_CREDENTIALS`<br/>`GRAPH_CORS_ALLOW_CREDENTIALS`| 1.0.0 |bool|`Allow credentials for CORS.See following chapter for more details: *Access-Control-Allow-Credentials* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Credentials.`|`true`|
+|`GRAPH_GROUP_MEMBERS_PATCH_LIMIT`| 1.0.0 |int|`The amount of group members allowed to be added with a single patch request.`|`20`|
+|`GRAPH_USERNAME_MATCH`| 1.0.0 |string|`Apply restrictions to usernames. Supported values are 'default' and 'none'. When set to 'default', user names must not start with a number and are restricted to ASCII characters. When set to 'none', no restrictions are applied. The default value is 'default'.`|`default`|
+|`GRAPH_ASSIGN_DEFAULT_USER_ROLE`| 1.0.0 |bool|`Whether to assign newly created users the default role 'User'. Set this to 'false' if you want to assign roles manually, or if the role assignment should happen at first login. Set this to 'true' (the default) to assign the role 'User' when creating a new user.`|`true`|
+|`GRAPH_IDENTITY_SEARCH_MIN_LENGTH`| 1.0.0 |int|`The minimum length the search term needs to have for unprivileged users when searching for users or groups.`|`3`|
+|`OC_SHOW_USER_EMAIL_IN_RESULTS`| 1.0.0 |bool|`Include user email addresses in responses. If absent or set to false emails will be omitted from results. Please note that admin users can always see all email addresses.`|`false`|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`The CS3 gateway endpoint.`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
+|`OC_JWT_SECRET`<br/>`GRAPH_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`GRAPH_APPLICATION_ID`| 1.0.0 |string|`The OpenCloud application ID shown in the graph. All app roles are tied to this ID.`|``|
+|`GRAPH_APPLICATION_DISPLAYNAME`| 1.0.0 |string|`The OpenCloud application name.`|`OpenCloud`|
+|`OC_URL`<br/>`GRAPH_SPACES_WEBDAV_BASE`| 1.0.0 |string|`The public facing URL of WebDAV.`|`https://localhost:9200`|
+|`GRAPH_SPACES_WEBDAV_PATH`| 1.0.0 |string|`The WebDAV sub-path for spaces.`|`/dav/spaces/`|
+|`GRAPH_SPACES_DEFAULT_QUOTA`| 1.0.0 |string|`The default quota in bytes.`|`1000000000`|
+|`GRAPH_SPACES_EXTENDED_SPACE_PROPERTIES_CACHE_TTL`| 1.0.0 |int|`Max TTL in seconds for the spaces property cache.`|`60000000000`|
+|`GRAPH_SPACES_USERS_CACHE_TTL`| 1.0.0 |int|`Max TTL in seconds for the spaces users cache.`|`60000000000`|
+|`GRAPH_SPACES_GROUPS_CACHE_TTL`| 1.0.0 |int|`Max TTL in seconds for the spaces groups cache.`|`60000000000`|
+|`GRAPH_SPACES_STORAGE_USERS_ADDRESS`| 1.0.0 |string|`The address of the storage-users service.`|`eu.opencloud.api.storage-users`|
+|`OC_DEFAULT_LANGUAGE`| 1.0.0 |string|`The default language used by services and the WebUI. If not defined, English will be used as default. See the documentation for more details.`|``|
+|`OC_TRANSLATION_PATH`<br/>`GRAPH_TRANSLATION_PATH`| 1.0.0 |string|`(optional) Set this to a path with custom translations to overwrite the builtin translations. Note that file and folder naming rules apply, see the documentation for more details.`|``|
+|`GRAPH_IDENTITY_BACKEND`| 1.0.0 |string|`The user identity backend to use. Supported backend types are 'ldap' and 'cs3'.`|`ldap`|
+|`OC_LDAP_URI`<br/>`GRAPH_LDAP_URI`| 1.0.0 |string|`URI of the LDAP Server to connect to. Supported URI schemes are 'ldaps://' and 'ldap://'`|`ldap://localhost:9236`|
+|`OC_LDAP_CACERT`<br/>`GRAPH_LDAP_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the LDAP service. If not defined, the root directory derives from $OC_BASE_DATA_PATH/idm.`|``|
+|`OC_LDAP_INSECURE`<br/>`GRAPH_LDAP_INSECURE`| 1.0.0 |bool|`Disable TLS certificate validation for the LDAP connections. Do not set this in production environments.`|`false`|
+|`OC_LDAP_BIND_DN`<br/>`GRAPH_LDAP_BIND_DN`| 1.0.0 |string|`LDAP DN to use for simple bind authentication with the target LDAP server.`|`uid=libregraph,ou=sysusers,o=libregraph-idm`|
+|`OC_LDAP_BIND_PASSWORD`<br/>`GRAPH_LDAP_BIND_PASSWORD`| 1.0.0 |string|`Password to use for authenticating the 'bind_dn'.`|``|
+|`GRAPH_LDAP_SERVER_UUID`| 1.0.0 |bool|`If set to true, rely on the LDAP Server to generate a unique ID for users and groups, like when using 'entryUUID' as the user ID attribute.`|`false`|
+|`GRAPH_LDAP_SERVER_USE_PASSWORD_MODIFY_EXOP`| 1.0.0 |bool|`Use the 'Password Modify Extended Operation' for updating user passwords.`|`true`|
+|`OC_LDAP_SERVER_WRITE_ENABLED`<br/>`GRAPH_LDAP_SERVER_WRITE_ENABLED`| 1.0.0 |bool|`Allow creating, modifying and deleting LDAP users via the GRAPH API. This can only be set to 'true' when keeping default settings for the LDAP user and group attribute types (the 'OC_LDAP_USER_SCHEMA_* and 'OC_LDAP_GROUP_SCHEMA_* variables).`|`true`|
+|`GRAPH_LDAP_REFINT_ENABLED`| 1.0.0 |bool|`Signals that the server has the refint plugin enabled, which makes some actions not needed.`|`false`|
+|`OC_LDAP_USER_BASE_DN`<br/>`GRAPH_LDAP_USER_BASE_DN`| 1.0.0 |string|`Search base DN for looking up LDAP users.`|`ou=users,o=libregraph-idm`|
+|`OC_LDAP_USER_SCOPE`<br/>`GRAPH_LDAP_USER_SCOPE`| 1.0.0 |string|`LDAP search scope to use when looking up users. Supported scopes are 'base', 'one' and 'sub'.`|`sub`|
+|`OC_LDAP_USER_FILTER`<br/>`GRAPH_LDAP_USER_FILTER`| 1.0.0 |string|`LDAP filter to add to the default filters for user search like '(objectclass=openCloudUser)'.`|``|
+|`OC_LDAP_USER_OBJECTCLASS`<br/>`GRAPH_LDAP_USER_OBJECTCLASS`| 1.0.0 |string|`The object class to use for users in the default user search filter ('inetOrgPerson').`|`inetOrgPerson`|
+|`OC_LDAP_USER_SCHEMA_MAIL`<br/>`GRAPH_LDAP_USER_EMAIL_ATTRIBUTE`| 1.0.0 |string|`LDAP Attribute to use for the email address of users.`|`mail`|
+|`OC_LDAP_USER_SCHEMA_DISPLAYNAME`<br/>`GRAPH_LDAP_USER_DISPLAYNAME_ATTRIBUTE`| 1.0.0 |string|`LDAP Attribute to use for the display name of users.`|`displayName`|
+|`OC_LDAP_USER_SCHEMA_USERNAME`<br/>`GRAPH_LDAP_USER_NAME_ATTRIBUTE`| 1.0.0 |string|`LDAP Attribute to use for username of users.`|`uid`|
+|`OC_LDAP_USER_SCHEMA_ID`<br/>`GRAPH_LDAP_USER_UID_ATTRIBUTE`| 1.0.0 |string|`LDAP Attribute to use as the unique ID for users. This should be a stable globally unique ID like a UUID.`|`openCloudUUID`|
+|`OC_LDAP_USER_SCHEMA_ID_IS_OCTETSTRING`<br/>`GRAPH_LDAP_USER_SCHEMA_ID_IS_OCTETSTRING`| 1.0.0 |bool|`Set this to true if the defined 'ID' attribute for users is of the 'OCTETSTRING' syntax. This is required when using the 'objectGUID' attribute of Active Directory for the user ID's.`|`false`|
+|`OC_LDAP_USER_SCHEMA_USER_TYPE`<br/>`GRAPH_LDAP_USER_TYPE_ATTRIBUTE`| 1.0.0 |string|`LDAP Attribute to distinguish between 'Member' and 'Guest' users. Default is 'openCloudUserType'.`|`openCloudUserType`|
+|`OC_LDAP_USER_ENABLED_ATTRIBUTE`<br/>`GRAPH_USER_ENABLED_ATTRIBUTE`| 1.0.0 |string|`LDAP Attribute to use as a flag telling if the user is enabled or disabled.`|`openCloudUserEnabled`|
+|`OC_LDAP_DISABLE_USER_MECHANISM`<br/>`GRAPH_DISABLE_USER_MECHANISM`| 1.0.0 |string|`An option to control the behavior for disabling users. Supported options are 'none', 'attribute' and 'group'. If set to 'group', disabling a user via API will add the user to the configured group for disabled users, if set to 'attribute' this will be done in the ldap user entry, if set to 'none' the disable request is not processed. Default is 'attribute'.`|`attribute`|
+|`OC_LDAP_DISABLED_USERS_GROUP_DN`<br/>`GRAPH_DISABLED_USERS_GROUP_DN`| 1.0.0 |string|`The distinguished name of the group to which added users will be classified as disabled when 'disable_user_mechanism' is set to 'group'.`|`cn=DisabledUsersGroup,ou=groups,o=libregraph-idm`|
+|`OC_LDAP_GROUP_BASE_DN`<br/>`GRAPH_LDAP_GROUP_BASE_DN`| 1.0.0 |string|`Search base DN for looking up LDAP groups.`|`ou=groups,o=libregraph-idm`|
+|`GRAPH_LDAP_GROUP_CREATE_BASE_DN`| 1.0.0 |string|`Parent DN under which new groups are created. This DN needs to be subordinate to the 'GRAPH_LDAP_GROUP_BASE_DN'. This setting is only relevant when 'GRAPH_LDAP_SERVER_WRITE_ENABLED' is 'true'. It defaults to the value of 'GRAPH_LDAP_GROUP_BASE_DN'. All groups outside of this subtree are treated as readonly groups and cannot be updated.`|`ou=groups,o=libregraph-idm`|
+|`OC_LDAP_GROUP_SCOPE`<br/>`GRAPH_LDAP_GROUP_SEARCH_SCOPE`| 1.0.0 |string|`LDAP search scope to use when looking up groups. Supported scopes are 'base', 'one' and 'sub'.`|`sub`|
+|`OC_LDAP_GROUP_FILTER`<br/>`GRAPH_LDAP_GROUP_FILTER`| 1.0.0 |string|`LDAP filter to add to the default filters for group searches.`|``|
+|`OC_LDAP_GROUP_OBJECTCLASS`<br/>`GRAPH_LDAP_GROUP_OBJECTCLASS`| 1.0.0 |string|`The object class to use for groups in the default group search filter ('groupOfNames').`|`groupOfNames`|
+|`OC_LDAP_GROUP_SCHEMA_GROUPNAME`<br/>`GRAPH_LDAP_GROUP_NAME_ATTRIBUTE`| 1.0.0 |string|`LDAP Attribute to use for the name of groups.`|`cn`|
+|`OC_LDAP_GROUP_SCHEMA_MEMBER`<br/>`GRAPH_LDAP_GROUP_MEMBER_ATTRIBUTE`| 1.0.0 |string|`LDAP Attribute that is used for group members.`|`member`|
+|`OC_LDAP_GROUP_SCHEMA_ID`<br/>`GRAPH_LDAP_GROUP_ID_ATTRIBUTE`| 1.0.0 |string|`LDAP Attribute to use as the unique id for groups. This should be a stable globally unique ID like a UUID.`|`openCloudUUID`|
+|`OC_LDAP_GROUP_SCHEMA_ID_IS_OCTETSTRING`<br/>`GRAPH_LDAP_GROUP_SCHEMA_ID_IS_OCTETSTRING`| 1.0.0 |bool|`Set this to true if the defined 'ID' attribute for groups is of the 'OCTETSTRING' syntax. This is required when using the 'objectGUID' attribute of Active Directory for the group ID's.`|`false`|
+|`GRAPH_LDAP_EDUCATION_RESOURCES_ENABLED`| 1.0.0 |bool|`Enable LDAP support for managing education related resources.`|`false`|
+|`GRAPH_LDAP_SCHOOL_BASE_DN`| 1.0.0 |string|`Search base DN for looking up LDAP schools.`|``|
+|`GRAPH_LDAP_SCHOOL_SEARCH_SCOPE`| 1.0.0 |string|`LDAP search scope to use when looking up schools. Supported scopes are 'base', 'one' and 'sub'.`|``|
+|`GRAPH_LDAP_SCHOOL_FILTER`| 1.0.0 |string|`LDAP filter to add to the default filters for school searches.`|``|
+|`GRAPH_LDAP_SCHOOL_OBJECTCLASS`| 1.0.0 |string|`The object class to use for schools in the default school search filter.`|``|
+|`GRAPH_LDAP_SCHOOL_NAME_ATTRIBUTE`| 1.0.0 |string|`LDAP Attribute to use for the name of a school.`|``|
+|`GRAPH_LDAP_SCHOOL_NUMBER_ATTRIBUTE`| 1.0.0 |string|`LDAP Attribute to use for the number of a school.`|``|
+|`GRAPH_LDAP_SCHOOL_ID_ATTRIBUTE`| 1.0.0 |string|`LDAP Attribute to use as the unique id for schools. This should be a stable globally unique ID like a UUID.`|``|
+|`GRAPH_LDAP_SCHOOL_TERMINATION_MIN_GRACE_DAYS`| 1.0.0 |int|`When setting a 'terminationDate' for a school, require the date to be at least this number of days in the future.`|`0`|
+|`OC_ENABLE_OCM`<br/>`GRAPH_INCLUDE_OCM_SHAREES`| 1.0.0 |bool|`Include OCM sharees when listing users.`|`false`|
+|`OC_EVENTS_ENDPOINT`<br/>`GRAPH_EVENTS_ENDPOINT`| 1.0.0 |string|`The address of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture. Set to a empty string to disable emitting events.`|`127.0.0.1:9233`|
+|`OC_EVENTS_CLUSTER`<br/>`GRAPH_EVENTS_CLUSTER`| 1.0.0 |string|`The clusterID of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture.`|`opencloud-cluster`|
+|`OC_INSECURE`<br/>`OC_EVENTS_TLS_INSECURE`<br/>`GRAPH_EVENTS_TLS_INSECURE`| 1.0.0 |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_EVENTS_TLS_ROOT_CA_CERTIFICATE`<br/>`GRAPH_EVENTS_TLS_ROOT_CA_CERTIFICATE`| 1.0.0 |string|`The root CA certificate used to validate the server's TLS certificate. If provided GRAPH_EVENTS_TLS_INSECURE will be seen as false.`|``|
+|`OC_EVENTS_ENABLE_TLS`<br/>`GRAPH_EVENTS_ENABLE_TLS`| 1.0.0 |bool|`Enable TLS for the connection to the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|`false`|
+|`OC_EVENTS_AUTH_USERNAME`<br/>`GRAPH_EVENTS_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_EVENTS_AUTH_PASSWORD`<br/>`GRAPH_EVENTS_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`GRAPH_AVAILABLE_ROLES`| 1.0.0 |[]string|`A comma separated list of roles that are available for assignment.`|`[b1e2218d-eef8-4d4c-b82d-0f1a1b48f3b5 a8d5fe5e-96e3-418d-825b-534dbdf22b99 fb6c3e19-e378-47e5-b277-9732f9de6e21 58c63c02-1d89-4572-916a-870abc5a1b7d 2d00ce52-1fc2-4dbc-8b95-a73b73395f5a 1c996275-f1c9-4e71-abdf-a42f6495e960 312c0871-5ef7-4b3a-85b6-0e4074c64049]`|
+|`OC_MAX_CONCURRENCY`<br/>`GRAPH_MAX_CONCURRENCY`| 1.0.0 |int|`The maximum number of concurrent requests the service will handle.`|`20`|
+|`OC_KEYCLOAK_BASE_PATH`<br/>`GRAPH_KEYCLOAK_BASE_PATH`| 1.0.0 |string|`The URL to access keycloak.`|``|
+|`OC_KEYCLOAK_CLIENT_ID`<br/>`GRAPH_KEYCLOAK_CLIENT_ID`| 1.0.0 |string|`The client id to authenticate with keycloak.`|``|
+|`OC_KEYCLOAK_CLIENT_SECRET`<br/>`GRAPH_KEYCLOAK_CLIENT_SECRET`| 1.0.0 |string|`The client secret to use in authentication.`|``|
+|`OC_KEYCLOAK_CLIENT_REALM`<br/>`GRAPH_KEYCLOAK_CLIENT_REALM`| 1.0.0 |string|`The realm the client is defined in.`|``|
+|`OC_KEYCLOAK_USER_REALM`<br/>`GRAPH_KEYCLOAK_USER_REALM`| 1.0.0 |string|`The realm users are defined.`|``|
+|`OC_KEYCLOAK_INSECURE_SKIP_VERIFY`<br/>`GRAPH_KEYCLOAK_INSECURE_SKIP_VERIFY`| 1.0.0 |bool|`Disable TLS certificate validation for Keycloak connections. Do not set this in production environments.`|`false`|
+|`OC_SERVICE_ACCOUNT_ID`<br/>`GRAPH_SERVICE_ACCOUNT_ID`| 1.0.0 |string|`The ID of the service account the service should use. See the 'auth-service' service description for more details.`|``|
+|`OC_SERVICE_ACCOUNT_SECRET`<br/>`GRAPH_SERVICE_ACCOUNT_SECRET`| 1.0.0 |string|`The service account secret.`|``|
+|`GRAPH_STORAGE_GATEWAY_GRPC_ADDR`<br/>`STORAGE_GATEWAY_GRPC_ADDR`| 4.0.0 |string|`GRPC address of the STORAGE-SYSTEM service.`|`eu.opencloud.api.storage-system`|
+|`GRAPH_STORAGE_GRPC_ADDR`<br/>`STORAGE_GRPC_ADDR`| 4.0.0 |string|`GRPC address of the STORAGE-SYSTEM service.`|`eu.opencloud.api.storage-system`|
+|`OC_SYSTEM_USER_ID`<br/>`GRAPH_SYSTEM_USER_ID`| 4.0.0 |string|`ID of the OpenCloud STORAGE-SYSTEM system user. Admins need to set the ID for the STORAGE-SYSTEM system user in this config option which is then used to reference the user. Any reasonable long string is possible, preferably this would be an UUIDv4 format.`|``|
+|`OC_SYSTEM_USER_IDP`<br/>`GRAPH_SYSTEM_USER_IDP`| 4.0.0 |string|`IDP of the OpenCloud STORAGE-SYSTEM system user.`|`internal`|
+|`OC_SYSTEM_USER_API_KEY`| 4.0.0 |string|`API key for the STORAGE-SYSTEM system user.`|``|
+|`GRAPH_USER_SOFT_DELETE_RETENTION_TIME`| 4.0.0 |Duration|`The time after which a soft-deleted user is permanently deleted. If set to 0 (default), there is no soft delete retention time and users are deleted immediately after being soft-deleted. If set to a positive value, the user will be kept in the system for that duration before being permanently deleted.`|`0s`|
+|`OC_PERSISTENT_STORE_NODES`<br/>`GRAPH_STORE_NODES`| 1.0.0 |[]string|`A list of nodes to access the configured store. This has no effect when 'memory' store is configured. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details.`|`[127.0.0.1:9233]`|
+|`GRAPH_STORE_DATABASE`| 1.0.0 |string|`The database name the configured store should use.`|`graph`|
+|`OC_PERSISTENT_STORE_AUTH_USERNAME`<br/>`GRAPH_STORE_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_PERSISTENT_STORE_AUTH_PASSWORD`<br/>`GRAPH_STORE_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_PERSISTENT_STORE_ENABLE_TLS`<br/>`GRAPH_STORE_ENABLE_TLS`| next |bool|`Enable TLS for the connection to the store. Only applies when store type 'nats-js-kv' is configured.`|`false`|
+|`OC_INSECURE`<br/>`OC_PERSISTENT_STORE_TLS_INSECURE`<br/>`GRAPH_STORE_TLS_INSECURE`| next |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_PERSISTENT_STORE_TLS_ROOT_CA_CERTIFICATE`<br/>`GRAPH_STORE_TLS_ROOT_CA_CERTIFICATE`| next |string|`The root CA certificate used to validate the server's TLS certificate. If provided GRAPH_STORE_TLS_INSECURE will be seen as false.`|``|
diff --git a/versioned_docs/version-7.x/_static/env-vars/graph_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/graph_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/graph_readme.md b/versioned_docs/version-7.x/_static/env-vars/graph_readme.md
new file mode 100755
index 000000000..9b48eb186
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/graph_readme.md
@@ -0,0 +1,207 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The graph service provides the Graph API which is a RESTful web API used to access OpenCloud
+resources. It is inspired by the [Microsoft Graph API](https://learn.microsoft.com/en-us/graph/use-the-api)
+and can be used by clients or other services or extensions. Visit the [Libre Graph API](https://docs.opencloud.eu/swagger/libre-graph-api/)
+for a detailed specification of the API implemented by the graph service.
+
+
+## Table of Contents
+
+* [Sequence Diagram](#sequence-diagram)
+* [Users and Groups API](#users-and-groups-api)
+  * [LDAP Configuration](#ldap-configuration)
+    * [Read-Only Access to Existing LDAP Servers](#readonly-access-to-existing-ldap-servers)
+    * [Using a Write Enabled LDAP Server](#using-a-write-enabled-ldap-server)
+* [Query Filters Provided by the Graph API](#query-filters-provided-by-the-graph-api)
+* [Caching](#caching)
+* [Keycloak Configuration For The Personal Data Export](#keycloak-configuration-for-the-personal-data-export)
+  * [Keycloak Client Configuration](#keycloak-client-configuration)
+* [Translations](#translations)
+  * [Translation Rules](#translation-rules)
+* [Default Language](#default-language)
+* [Unified Role Management](#unified-role-management)
+
+## Sequence Diagram
+
+The following image gives an overview of the scenario when a client requests to list available spaces the user has access to. To do so, the client is directed with his request automatically via the proxy service to the graph service.
+
+<img src="https://raw.githubusercontent.com/opencloud-eu/opencloud/main/services/graph/images/mermaid-graph.svg" width="900" />
+
+## Users and Groups API
+
+The graph service provides endpoints for querying users and groups. It features two different backend implementations:
+  * `ldap`: This is currently the default backend. It queries user and group information from an
+    LDAP server. Depending on the configuration, it can also be used to manage (create, update,
+    delete) users and groups provided by an LDAP server.
+  * `cs3`: This backend queries users and groups using the CS3 identity APIs as implemented by the
+    `users` and `groups` service. This backend is currently still experimental and only implements a
+    subset of the Libre Graph API. It should not be used in production.
+
+### LDAP Configuration
+
+The LDAP backend is configured using a set of environment variables. A detailed list of all the
+available configuration options can be found in the [documentation](https://docs.opencloud.eu/docs/dev/server/services/graph/environment-variables).
+The LDAP related options are prefixed with `OC_LDAP_` (or `GRAPH_LDAP_` for settings specific to graph service).
+
+#### Read-Only Access to Existing LDAP Servers
+
+To connect the graph service to an existing LDAP server, set `OC_LDAP_SERVER_WRITE_ENABLED` to
+`false` to prevent the graph service from sending write operations to the LDAP server. Also set the
+various `OC_LDAP_*` environment variables to match the configuration of the LDAP server you are connecting
+to. A more detailed explanation can be found [here](https://docs.opencloud.eu/docs/admin/configuration/authentication-and-user-management/.
+
+#### Using a Write Enabled LDAP Server
+
+To use the graph service for managing (create, update, delete) users and groups, a write enabled LDAP
+server is required. In the default configuration, the graph service will use the simple LDAP server
+that is bundled with OpenCloud in the `idm` service which provides all the required features.
+It is also possible to setup up an external LDAP server with write access for use with OpenCloud. It is
+recommend to use OpenLDAP for this. The LDAP server needs to fulfill a couple of requirements with
+respect to the available schema:
+  * The LDAP server must provide the `inetOrgPerson` object class for users and the `groupOfNames`
+    object class for groups.
+  * The graph service maintains a few additional attributes for users and groups that are not
+    available in the standard LDAP schema. An schema file, ready to use with OpenLDAP, defining those
+    additional attributes is available [here](https://github.com/opencloud-eu/opencloud-compose/blob/main/config/ldap/schemas/10_opencloud_schema.ldif)
+
+## Query Filters Provided by the Graph API
+
+Some API endpoints provided by the graph service allow to specify query filters. The filter syntax
+is based on the [OData Specification](https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_SystemQueryOptionfilter).
+See the [Libre Graph API](https://docs.opencloud.eu/swagger/libre-graph-api/#/users/ListUsers) for examples
+on the filters supported when querying users.
+
+## Caching
+
+The `graph` service can use a configured store via `GRAPH_CACHE_STORE`. Possible stores are:
+  -   `memory`: Basic in-memory store and the default.
+  -   `redis-sentinel`: Stores data in a configured Redis Sentinel cluster.
+  -   `nats-js-kv`: Stores data using key-value-store feature of [nats jetstream](https://docs.nats.io/nats-concepts/jetstream/key-value-store)
+  -   `noop`: Stores nothing. Useful for testing. Not recommended in production environments.
+
+Other store types may work but are not supported currently.
+
+Store specific notes:
+  -   When using `redis-sentinel`, the Redis master to use is configured via e.g. `OC_CACHE_STORE_NODES` in the form of `<sentinel-host>:<sentinel-port>/<redis-master>` like `10.10.0.200:26379/mymaster`.
+  -   When using `nats-js-kv` it is recommended to set `OC_CACHE_STORE_NODES` to the same value as `OC_EVENTS_ENDPOINT`. That way the cache uses the same nats instance as the event bus.
+  -   When using the `nats-js-kv` store, it is possible to set `OC_CACHE_DISABLE_PERSISTENCE` to instruct nats to not persist cache data on disc.
+
+## Keycloak Configuration For The Personal Data Export
+
+If Keycloak is used for authentication, GDPR regulations require to add all personal identifiable information that Keycloak has about the user to the personal data export. To do this, the following environment variables must be set:
+
+*   `OC_KEYCLOAK_BASE_PATH` - The URL to the keycloak instance.
+*   `OC_KEYCLOAK_CLIENT_ID` - The client ID of the client that is used to authenticate with keycloak, this client has to be able to list users and get the credential data.
+*   `OC_KEYCLOAK_CLIENT_SECRET` - The client secret of the client that is used to authenticate with keycloak.
+*   `OC_KEYCLOAK_CLIENT_REALM` - The realm the client is defined in.
+*   `OC_KEYCLOAK_USER_REALM` - The realm the OpenCloud users are defined in.
+*   `OC_KEYCLOAK_INSECURE_SKIP_VERIFY` - If set to true, the TLS certificate of the keycloak instance is not verified.
+
+### Keycloak Client Configuration
+
+The client that is used to authenticate with keycloak has to be able to list users and get the credential data. To do this, the following  roles have to be assigned to the client and they have to be about the realm that contains the OpenCloud users:
+
+*   `view-users`
+*   `view-identity-providers`
+*   `view-realm`
+*   `view-clients`
+*   `view-events`
+*   `view-authorization`
+
+:::note
+These roles are only available to assign if the client is in the `master` realm.
+:::
+
+## Translations
+
+The `graph` service has embedded translations sourced via transifex to provide a basic set of translated languages. These embedded translations are available for all deployment scenarios. In addition, the service supports custom translations, though it is currently not possible to just add custom translations to embedded ones. If custom translations are configured, the embedded ones are not used. To configure custom translations, the `GRAPH_TRANSLATION_PATH` environment variable needs to point to a base folder that will contain the translation files. This path must be available from all instances of the graph service, a shared storage is recommended. Translation files must be of type  [.po](https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html#PO-Files) or [.mo](https://www.gnu.org/software/gettext/manual/html_node/Binaries.html). For each language, the filename needs to be `graph.po` (or `graph.mo`) and stored in a folder structure defining the language code. In general the path/name pattern for a translation file needs to be:
+
+```text
+{GRAPH_TRANSLATION_PATH}/{language-code}/LC_MESSAGES/graph.po
+```
+
+The language code pattern is composed of `language[_territory]` where  `language` is the base language and `_territory` is optional and defines a country.
+
+For example, for the language `de`, one needs to place the corresponding translation files to `{GRAPH_TRANSLATION_PATH}/de_DE/LC_MESSAGES/graph.po`.
+
+<!-- also see the notifications readme -->
+
+:::warning
+For the time being, the embedded OpenCloud Web frontend only supports the main language code but does not handle any territory. When strings are available in the language code `language_territory`, the web frontend does not see it as it only requests `language`. In consequence, any translations made must exist in the requested `language` to avoid a fallback to the default.
+:::
+
+### Translation Rules
+
+*   If a requested language code is not available, the service tries to fall back to the base language if available. For example, if the requested language-code `de_DE` is not available, the service tries to fall back to translations in the `de` folder.
+*   If the base language `de` is also not available, the service falls back to the system's default English (`en`),
+which is the source of the texts provided by the code.
+
+## Default Language
+
+The default language can be defined via the `OC_DEFAULT_LANGUAGE` environment variable. See the `settings` service for a detailed description.
+
+## Unified Role Management
+
+Unified Roles are roles granted a user for sharing and can be enabled or disabled. A CLI command is provided to list existing roles and their state among other data.
+
+:::info
+Note that a disabled role does not lose previously assigned permissions. It only means that the role is not available for new assignments.
+:::
+
+The following roles are **enabled** by default:
+
+- `UnifiedRoleViewerID`
+- `UnifiedRoleSpaceViewer`
+- `UnifiedRoleEditor`
+- `UnifiedRoleSpaceEditor`
+- `UnifiedRoleFileEditor`
+- `UnifiedRoleEditorLite`
+- `UnifiedRoleManager`
+
+The following role is **disabled** by default:
+
+- `UnifiedRoleSecureViewer`
+
+To enable disabled roles like the `UnifiedRoleSecureViewer`, you must provide the UID(s) by one of the following methods:
+
+- Using the `GRAPH_AVAILABLE_ROLES` environment variable.
+- Setting the `available_roles` configuration value.
+
+The following CLI command simplifies the process of finding out which UID belongs to which role:
+
+```bash
+opencloud graph list-unified-roles
+```
+
+The output of this command includes the following information for each role:
+
+* `UID`\
+  The unique identifier of the role.
+* `Enabled`\
+  Whether the role is enabled or not.
+* `Description`\
+  A short description of the role.
+* `Condition`
+* `Allowed resource actions`
+
+**Example output (shortned)**
+
+```bash
++--------------------------------------+----------+--------------------------------+--------------------------------+------------------------------------------+
+|                 UID                  | ENABLED  |          DESCRIPTION           |           CONDITION            |         ALLOWED RESOURCE ACTIONS         |
++--------------------------------------+----------+--------------------------------+--------------------------------+------------------------------------------+
+| a8d5fe5e-96e3-418d-825b-534dbdf22b99 | enabled  | View and download.             | exists @Resource.Root          | libre.graph/driveItem/path/read          |
+|                                      |          |                                |                                | libre.graph/driveItem/quota/read         |
+|                                      |          |                                |                                | libre.graph/driveItem/content/read       |
+|                                      |          |                                |                                | libre.graph/driveItem/permissions/read   |
+|                                      |          |                                |                                | libre.graph/driveItem/children/read      |
+|                                      |          |                                |                                | libre.graph/driveItem/deleted/read       |
+|                                      |          |                                |                                | libre.graph/driveItem/basic/read         |
++--------------------------------------+----------+--------------------------------+--------------------------------+------------------------------------------+
+```
+
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/groups.yaml b/versioned_docs/version-7.x/_static/env-vars/groups.yaml
new file mode 100644
index 000000000..8b631cff3
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/groups.yaml
@@ -0,0 +1,63 @@
+# Autogenerated
+# Filename: groups.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9161
+  token: ""
+  pprof: false
+  zpages: false
+grpc:
+  addr: 127.0.0.1:9160
+  tls: null
+  protocol: tcp
+token_manager:
+  jwt_secret: ""
+reva:
+  address: eu.opencloud.api.gateway
+  tls:
+    mode: ""
+    cacert: ""
+skip_user_groups_in_token: false
+driver: ldap
+drivers:
+  ldap:
+    uri: ldap://localhost:9236
+    ca_cert: ""
+    insecure: false
+    bind_dn: uid=reva,ou=sysusers,o=libregraph-idm
+    bind_password: ""
+    user_base_dn: ou=users,o=libregraph-idm
+    group_base_dn: ou=groups,o=libregraph-idm
+    user_scope: sub
+    group_scope: sub
+    group_substring_filter_type: any
+    user_filter: ""
+    group_filter: ""
+    user_object_class: inetOrgPerson
+    group_object_class: groupOfNames
+    idp: https://localhost:9200
+    user_schema:
+      id: openCloudUUID
+      id_is_octet_string: false
+      mail: mail
+      display_name: displayname
+      user_name: uid
+    group_schema:
+      id: openCloudUUID
+      id_is_octet_string: false
+      mail: mail
+      display_name: cn
+      group_name: cn
+      member: member
+  owncloudsql:
+    db_username: owncloud
+    db_password: ""
+    db_host: mysql
+    db_port: 3306
+    db_name: owncloud
+    idp: https://localhost:9200
+    nobody: 90
+    join_username: false
+    join_owncloud_uuid: false
+    enable_medial_search: false
diff --git a/versioned_docs/version-7.x/_static/env-vars/groups_configvars.md b/versioned_docs/version-7.x/_static/env-vars/groups_configvars.md
new file mode 100644
index 000000000..4528aa7bf
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/groups_configvars.md
@@ -0,0 +1,53 @@
+## Environment variables for the **groups** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`GROUPS_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`GROUPS_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9161`|
+|`GROUPS_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`GROUPS_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`GROUPS_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`GROUPS_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9160`|
+|`OC_GRPC_PROTOCOL`<br/>`GROUPS_GRPC_PROTOCOL`| 1.0.0 |string|`The transport protocol of the GRPC service.`|`tcp`|
+|`OC_JWT_SECRET`<br/>`GROUPS_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`The CS3 gateway endpoint.`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
+|`GROUPS_SKIP_USER_GROUPS_IN_TOKEN`| 1.0.0 |bool|`Disables the loading of user's group memberships from the reva access token.`|`false`|
+|`GROUPS_DRIVER`| 1.0.0 |string|`The driver which should be used by the groups service. Supported values are 'ldap' and 'owncloudsql'.`|`ldap`|
+|`OC_LDAP_URI`<br/>`GROUPS_LDAP_URI`| 1.0.0 |string|`URI of the LDAP Server to connect to. Supported URI schemes are 'ldaps://' and 'ldap://'`|`ldap://localhost:9236`|
+|`OC_LDAP_CACERT`<br/>`GROUPS_LDAP_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the LDAP service. If not defined, the root directory derives from $OC_BASE_DATA_PATH/idm.`|``|
+|`OC_LDAP_INSECURE`<br/>`GROUPS_LDAP_INSECURE`| 1.0.0 |bool|`Disable TLS certificate validation for the LDAP connections. Do not set this in production environments.`|`false`|
+|`OC_LDAP_BIND_DN`<br/>`GROUPS_LDAP_BIND_DN`| 1.0.0 |string|`LDAP DN to use for simple bind authentication with the target LDAP server.`|`uid=reva,ou=sysusers,o=libregraph-idm`|
+|`OC_LDAP_BIND_PASSWORD`<br/>`GROUPS_LDAP_BIND_PASSWORD`| 1.0.0 |string|`Password to use for authenticating the 'bind_dn'.`|``|
+|`OC_LDAP_USER_BASE_DN`<br/>`GROUPS_LDAP_USER_BASE_DN`| 1.0.0 |string|`Search base DN for looking up LDAP users.`|`ou=users,o=libregraph-idm`|
+|`OC_LDAP_GROUP_BASE_DN`<br/>`GROUPS_LDAP_GROUP_BASE_DN`| 1.0.0 |string|`Search base DN for looking up LDAP groups.`|`ou=groups,o=libregraph-idm`|
+|`OC_LDAP_USER_SCOPE`<br/>`GROUPS_LDAP_USER_SCOPE`| 1.0.0 |string|`LDAP search scope to use when looking up users. Supported scopes are 'base', 'one' and 'sub'.`|`sub`|
+|`OC_LDAP_GROUP_SCOPE`<br/>`GROUPS_LDAP_GROUP_SCOPE`| 1.0.0 |string|`LDAP search scope to use when looking up groups. Supported scopes are 'base', 'one' and 'sub'.`|`sub`|
+|`LDAP_GROUP_SUBSTRING_FILTER_TYPE`<br/>`GROUPS_LDAP_GROUP_SUBSTRING_FILTER_TYPE`| 1.0.0 |string|`Type of substring search filter to use for substring searches for groups. Supported values are 'initial', 'final' and 'any'. The value 'initial' is used for doing prefix only searches, 'final' for doing suffix only searches or 'any' for doing full substring searches`|`any`|
+|`OC_LDAP_USER_FILTER`<br/>`GROUPS_LDAP_USER_FILTER`| 1.0.0 |string|`LDAP filter to add to the default filters for user search like '(objectclass=openCloudUser)'.`|``|
+|`OC_LDAP_GROUP_FILTER`<br/>`GROUPS_LDAP_GROUP_FILTER`| 1.0.0 |string|`LDAP filter to add to the default filters for group searches.`|``|
+|`OC_LDAP_USER_OBJECTCLASS`<br/>`GROUPS_LDAP_USER_OBJECTCLASS`| 1.0.0 |string|`The object class to use for users in the default user search filter ('inetOrgPerson').`|`inetOrgPerson`|
+|`OC_LDAP_GROUP_OBJECTCLASS`<br/>`GROUPS_LDAP_GROUP_OBJECTCLASS`| 1.0.0 |string|`The object class to use for groups in the default group search filter ('groupOfNames').`|`groupOfNames`|
+|`OC_URL`<br/>`OC_OIDC_ISSUER`<br/>`GROUPS_IDP_URL`| 1.0.0 |string|`The identity provider value to set in the group IDs of the CS3 group objects for groups returned by this group provider.`|`https://localhost:9200`|
+|`OC_LDAP_USER_SCHEMA_ID`<br/>`GROUPS_LDAP_USER_SCHEMA_ID`| 1.0.0 |string|`LDAP Attribute to use as the unique id for users. This should be a stable globally unique id like a UUID.`|`openCloudUUID`|
+|`OC_LDAP_USER_SCHEMA_ID_IS_OCTETSTRING`<br/>`GROUPS_LDAP_USER_SCHEMA_ID_IS_OCTETSTRING`| 1.0.0 |bool|`Set this to true if the defined 'ID' attribute for users is of the 'OCTETSTRING' syntax. This is e.g. required when using the 'objectGUID' attribute of Active Directory for the user ID's.`|`false`|
+|`OC_LDAP_USER_SCHEMA_MAIL`<br/>`GROUPS_LDAP_USER_SCHEMA_MAIL`| 1.0.0 |string|`LDAP Attribute to use for the email address of users.`|`mail`|
+|`OC_LDAP_USER_SCHEMA_DISPLAYNAME`<br/>`GROUPS_LDAP_USER_SCHEMA_DISPLAYNAME`| 1.0.0 |string|`LDAP Attribute to use for the displayname of users.`|`displayname`|
+|`OC_LDAP_USER_SCHEMA_USERNAME`<br/>`GROUPS_LDAP_USER_SCHEMA_USERNAME`| 1.0.0 |string|`LDAP Attribute to use for username of users.`|`uid`|
+|`OC_LDAP_GROUP_SCHEMA_ID`<br/>`GROUPS_LDAP_GROUP_SCHEMA_ID`| 1.0.0 |string|`LDAP Attribute to use as the unique id for groups. This should be a stable globally unique ID like a UUID.`|`openCloudUUID`|
+|`OC_LDAP_GROUP_SCHEMA_ID_IS_OCTETSTRING`<br/>`GROUPS_LDAP_GROUP_SCHEMA_ID_IS_OCTETSTRING`| 1.0.0 |bool|`Set this to true if the defined 'id' attribute for groups is of the 'OCTETSTRING' syntax. This is e.g. required when using the 'objectGUID' attribute of Active Directory for the group ID's.`|`false`|
+|`OC_LDAP_GROUP_SCHEMA_MAIL`<br/>`GROUPS_LDAP_GROUP_SCHEMA_MAIL`| 1.0.0 |string|`LDAP Attribute to use for the email address of groups (can be empty).`|`mail`|
+|`OC_LDAP_GROUP_SCHEMA_DISPLAYNAME`<br/>`GROUPS_LDAP_GROUP_SCHEMA_DISPLAYNAME`| 1.0.0 |string|`LDAP Attribute to use for the displayname of groups (often the same as groupname attribute).`|`cn`|
+|`OC_LDAP_GROUP_SCHEMA_GROUPNAME`<br/>`GROUPS_LDAP_GROUP_SCHEMA_GROUPNAME`| 1.0.0 |string|`LDAP Attribute to use for the name of groups.`|`cn`|
+|`OC_LDAP_GROUP_SCHEMA_MEMBER`<br/>`GROUPS_LDAP_GROUP_SCHEMA_MEMBER`| 1.0.0 |string|`LDAP Attribute that is used for group members.`|`member`|
+|`GROUPS_OWNCLOUDSQL_DB_USERNAME`| 1.0.0 |string|`Database user to use for authenticating with the owncloud database.`|`owncloud`|
+|`GROUPS_OWNCLOUDSQL_DB_PASSWORD`| 1.0.0 |string|`Password for the database user.`|``|
+|`GROUPS_OWNCLOUDSQL_DB_HOST`| 1.0.0 |string|`Hostname of the database server.`|`mysql`|
+|`GROUPS_OWNCLOUDSQL_DB_PORT`| 1.0.0 |int|`Network port to use for the database connection.`|`3306`|
+|`GROUPS_OWNCLOUDSQL_DB_NAME`| 1.0.0 |string|`Name of the owncloud database.`|`owncloud`|
+|`GROUPS_OWNCLOUDSQL_IDP`| 1.0.0 |string|`The identity provider value to set in the userids of the CS3 user objects for users returned by this user provider.`|`https://localhost:9200`|
+|`GROUPS_OWNCLOUDSQL_NOBODY`| 1.0.0 |int64|`Fallback number if no numeric UID and GID properties are provided.`|`90`|
+|`GROUPS_OWNCLOUDSQL_JOIN_USERNAME`| 1.0.0 |bool|`Join the user properties table to read usernames.`|`false`|
+|`GROUPS_OWNCLOUDSQL_JOIN_OWNCLOUD_UUID`| 1.0.0 |bool|`Join the user properties table to read user IDs.`|`false`|
+|`GROUPS_OWNCLOUDSQL_ENABLE_MEDIAL_SEARCH`| 1.0.0 |bool|`Allow 'medial search' when searching for users instead of just doing a prefix search. This allows finding 'Alice' when searching for 'lic'.`|`false`|
diff --git a/versioned_docs/version-7.x/_static/env-vars/groups_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/groups_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/groups_readme.md b/versioned_docs/version-7.x/_static/env-vars/groups_readme.md
new file mode 100755
index 000000000..25426780e
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/groups_readme.md
@@ -0,0 +1,41 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The `groups` service provides the CS3 Groups API for OpenCloud. It is responsible for managing group information and memberships within the OpenCloud instance.
+
+This service implements the CS3 identity group provider interface, allowing other services to query and manage groups. It works as a backend provider for the `graph` service when using the CS3 backend mode.
+
+
+## Table of Contents
+
+* [Backend Integration](#backend-integration)
+* [API](#api)
+* [Usage](#usage)
+* [Scalability](#scalability)
+
+## Backend Integration
+
+The groups service can work with different storage backends:
+- LDAP integration through the graph service
+- Direct CS3 API implementation
+
+When using the `graph` service with the CS3 backend (`GRAPH_IDENTITY_BACKEND=cs3`), the graph service queries group information through this service.
+
+## API
+
+The service provides CS3 gRPC APIs for:
+- Listing groups
+- Getting group information
+- Finding groups by name or ID
+- Managing group memberships
+
+## Usage
+
+The groups service is only used internally by other OpenCloud services and not being accessed directly by clients. The `frontend` and `ocs` services translate HTTP API requests into CS3 API calls to this service.
+
+## Scalability
+
+Since the groups service queries backend systems (like LDAP through the configured identity backend), it can be scaled horizontally without additional configuration when using stateless backends.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/idm.yaml b/versioned_docs/version-7.x/_static/env-vars/idm.yaml
new file mode 100644
index 000000000..b18d35d50
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/idm.yaml
@@ -0,0 +1,23 @@
+# Autogenerated
+# Filename: idm.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9239
+  token: ""
+  pprof: false
+  zpages: false
+idm:
+  ldaps_addr: ""
+  ldapaddr: 127.0.0.1:9236
+  cert: ""
+  key: ""
+  database: /var/lib/opencloud/idm/idm.boltdb
+create_demo_users: false
+demo_users_issuer_url: https://localhost:9200
+service_user_passwords:
+  admin_password: ""
+  idm_password: ""
+  reva_password: ""
+  idp_password: ""
+admin_user_id: ""
diff --git a/versioned_docs/version-7.x/_static/env-vars/idm_configvars.md b/versioned_docs/version-7.x/_static/env-vars/idm_configvars.md
new file mode 100644
index 000000000..916708bef
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/idm_configvars.md
@@ -0,0 +1,20 @@
+## Environment variables for the **idm** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`IDM_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`IDM_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9239`|
+|`IDM_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`IDM_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`IDM_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`IDM_LDAPS_ADDR`| 1.0.0 |string|`Listen address for the LDAPS listener (ip-addr:port).`|``|
+|`IDM_LDAPS_CERT`| 1.0.0 |string|`File name of the TLS server certificate for the LDAPS listener. If not defined, the root directory derives from $OC_BASE_DATA_PATH/idm.`|``|
+|`IDM_LDAPS_KEY`| 1.0.0 |string|`File name for the TLS certificate key for the server certificate. If not defined, the root directory derives from $OC_BASE_DATA_PATH/idm.`|``|
+|`IDM_DATABASE_PATH`| 1.0.0 |string|`Full path to the IDM backend database. If not defined, the root directory derives from $OC_BASE_DATA_PATH/idm.`|`/var/lib/opencloud/idm/idm.boltdb`|
+|`IDM_CREATE_DEMO_USERS`| 1.0.0 |bool|`Flag to enable or disable the creation of the demo users.`|`false`|
+|`OC_URL`<br/>`OC_OIDC_ISSUER`| 1.0.0 |string|`The OIDC issuer URL to assign to the demo users.`|`https://localhost:9200`|
+|`IDM_ADMIN_PASSWORD`| 1.0.0 |string|`Password to set for the OpenCloud 'admin' user. Either cleartext or an argon2id hash.`|``|
+|`IDM_SVC_PASSWORD`| 1.0.0 |string|`Password to set for the 'idm' service user. Either cleartext or an argon2id hash.`|``|
+|`IDM_REVASVC_PASSWORD`| 1.0.0 |string|`Password to set for the 'reva' service user. Either cleartext or an argon2id hash.`|``|
+|`IDM_IDPSVC_PASSWORD`| 1.0.0 |string|`Password to set for the 'idp' service user. Either cleartext or an argon2id hash.`|``|
+|`OC_ADMIN_USER_ID`<br/>`IDM_ADMIN_USER_ID`| 1.0.0 |string|`ID of the user that should receive admin privileges. Consider that the UUID can be encoded in some LDAP deployment configurations like in .ldif files. These need to be decoded beforehand.`|``|
diff --git a/versioned_docs/version-7.x/_static/env-vars/idm_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/idm_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/idm_readme.md b/versioned_docs/version-7.x/_static/env-vars/idm_readme.md
new file mode 100755
index 000000000..a504c9188
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/idm_readme.md
@@ -0,0 +1,29 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The IDM service provides a minimal LDAP Service, based on [Libregraph idm](https://github.com/libregraph/idm), for OpenCloud. It is started as part of the default configuration and serves as a central place for storing user and group information.
+
+It is mainly targeted at small OpenCloud installations. For larger setups it is recommended to replace IDM with a “real” LDAP server or to switch to an external identity management solution.
+
+IDM listens on port 9235 by default. In the default configuration it only accepts TLS-protected connections (LDAPS). The BaseDN of the LDAP tree is `o=libregraph-idm`. IDM gives LDAP write permissions to a single user (DN: `uid=libregraph,ou=sysusers,o=libregraph-idm`). Any other authenticated user has read-only access. IDM stores its data in a boltdb file `idm/idm.boltdb` inside the OpenCloud base data directory.
+
+The internal LDAP certificate and key are stored as `ldap.crt` and `ldap.key` in the IDM data directory. By default, these certificates expire after 12 months. When the certificate has expired, IDM can no longer establish valid TLS connections and requests that depend on LDAP may fail with `500 Internal Server Error`.
+
+To renew the internal LDAP certificate, stop or restart the OpenCloud container after deleting the expired certificate and key:
+
+```bash
+cd .opencloud/idm
+rm ldap.crt ldap.key
+docker compose restart
+```
+
+The certificate and key are automatically regenerated when the container starts again. For more details, see [Internal LibreIDM cert expires](https://docs.opencloud.eu/docs/admin/resources/common-issues/#internal-libreidm-cert-expires).
+
+Note: IDM is limited in its functionality. It only supports a subset of the LDAP operations (namely `BIND`, `SEARCH`, `ADD`, `MODIFY`, `DELETE`). Also, IDM currently does not do any schema verification (like. structural vs. auxiliary object classes, require and option attributes, syntax checks, …). Therefore it is not meant as a general purpose LDAP server.
+
+## Table of Contents
+
+
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/idp.yaml b/versioned_docs/version-7.x/_static/env-vars/idp.yaml
new file mode 100644
index 000000000..4f2ead2c3
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/idp.yaml
@@ -0,0 +1,113 @@
+# Autogenerated
+# Filename: idp.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9134
+  token: ""
+  pprof: false
+  zpages: false
+http:
+  addr: 127.0.0.1:9130
+  root: /
+  tls_cert: /var/lib/opencloud/idp/server.crt
+  tls_key: /var/lib/opencloud/idp/server.key
+  tls: false
+reva:
+  address: eu.opencloud.api.gateway
+  tls:
+    mode: ""
+    cacert: ""
+machine_auth_api_key: ""
+asset:
+  asset: ""
+  login-background-url: ""
+idp:
+  iss: https://localhost:9200
+  identity_manager: ldap
+  uri_base_path: ""
+  sign_in_uri: ""
+  signed_out_uri: ""
+  authorization_endpoint_uri: ""
+  ldap_insecure: false
+  trusted_proxy: []
+  allow_scope: []
+  allow_client_guests: false
+  allow_dynamic_client_registration: false
+  encrypt_secret_file: /var/lib/opencloud/idp/encryption.key
+  listen: ""
+  identifierdefaultbannerlogo: ""
+  default_sign_in_page_text: ""
+  default_logo_target_uri: https://opencloud.eu
+  identifierdefaultusernamehinttext: ""
+  identifieruilocales: []
+  signing_kid: private-key
+  signing_method: PS256
+  signing_private_key_files:
+  - /var/lib/opencloud/idp/private-key.pem
+  validation_keys_path: ""
+  cookiebackenduri: ""
+  cookienames: []
+  cookiesamesite: 3
+  access_token_duration_seconds: 300
+  id_token_duration_seconds: 300
+  refresh_token_duration_seconds: 2592000
+  dynamic_client_secret_duration_seconds: 0
+clients:
+- id: web
+  name: OpenCloud Web App
+  trusted: true
+  secret: ""
+  redirect_uris:
+  - '{{OC_URL}}/'
+  - '{{OC_URL}}/oidc-callback.html'
+  - '{{OC_URL}}/oidc-silent-redirect.html'
+  post_logout_redirect_uris: []
+  origins:
+  - '{{OC_URL}}'
+  application_type: ""
+- id: OpenCloudDesktop
+  name: OpenCloud Desktop Client
+  trusted: false
+  secret: ""
+  redirect_uris:
+  - http://127.0.0.1
+  - http://localhost
+  post_logout_redirect_uris: []
+  origins: []
+  application_type: native
+- id: OpenCloudAndroid
+  name: OpenCloud Android App
+  trusted: false
+  secret: ""
+  redirect_uris:
+  - oc://android.opencloud.eu
+  post_logout_redirect_uris:
+  - oc://android.opencloud.eu
+  origins: []
+  application_type: native
+- id: OpenCloudIOS
+  name: OpenCloud iOS App
+  trusted: false
+  secret: ""
+  redirect_uris:
+  - oc://ios.opencloud.eu
+  post_logout_redirect_uris:
+  - oc://ios.opencloud.eu
+  origins: []
+  application_type: native
+ldap:
+  uri: ldap://localhost:9236
+  cacert: ""
+  bind_dn: uid=idp,ou=sysusers,o=libregraph-idm
+  bind_password: ""
+  base_dn: ou=users,o=libregraph-idm
+  scope: sub
+  login_attribute: uid
+  email_attribute: mail
+  name_attribute: displayName
+  uuid_attribute: openCloudUUID
+  uuid_attribute_type: text
+  user_enabled_attribute: openCloudUserEnabled
+  filter: ""
+  objectclass: inetOrgPerson
diff --git a/versioned_docs/version-7.x/_static/env-vars/idp_configvars.md b/versioned_docs/version-7.x/_static/env-vars/idp_configvars.md
new file mode 100644
index 000000000..546a615e0
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/idp_configvars.md
@@ -0,0 +1,55 @@
+## Environment variables for the **idp** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`IDP_PASSWORD_RESET_URI`| 1.0.0 |string|`The URI where a user can reset their password.`|``|
+|`OC_LOG_LEVEL`<br/>`IDP_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`IDP_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9134`|
+|`IDP_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`IDP_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`IDP_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`IDP_HTTP_ADDR`| 1.0.0 |string|`The bind address of the HTTP service.`|`127.0.0.1:9130`|
+|`IDP_HTTP_ROOT`| 1.0.0 |string|`Subdirectory that serves as the root for this HTTP service.`|`/`|
+|`IDP_TRANSPORT_TLS_CERT`| 1.0.0 |string|`Path/File name of the TLS server certificate (in PEM format) for the IDP service. If not defined, the root directory derives from $OC_BASE_DATA_PATH/idp.`|`/var/lib/opencloud/idp/server.crt`|
+|`IDP_TRANSPORT_TLS_KEY`| 1.0.0 |string|`Path/File name for the TLS certificate key (in PEM format) for the server certificate to use for the IDP service. If not defined, the root directory derives from $OC_BASE_DATA_PATH/idp.`|`/var/lib/opencloud/idp/server.key`|
+|`IDP_TLS`| 1.0.0 |bool|`Disable or Enable HTTPS for the communication between the Proxy service and the IDP service. If set to 'true', the key and cert files need to be configured and present.`|`false`|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`The CS3 gateway endpoint.`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
+|`OC_MACHINE_AUTH_API_KEY`<br/>`IDP_MACHINE_AUTH_API_KEY`| 1.0.0 |string|`Machine auth API key used to validate internal requests necessary for the access to resources from other services.`|``|
+|`IDP_ASSET_PATH`| 1.0.0 |string|`Serve IDP assets from a path on the filesystem instead of the builtin assets.`|``|
+|`IDP_LOGIN_BACKGROUND_URL`| 1.0.0 |string|`Configure an alternative URL to the background image for the login page.`|``|
+|`OC_URL`<br/>`OC_OIDC_ISSUER`<br/>`IDP_ISS`| 1.0.0 |string|`The OIDC issuer URL to use.`|`https://localhost:9200`|
+|`IDP_IDENTITY_MANAGER`| 1.0.0 |string|`The identity manager implementation to use. Supported identity managers are 'ldap', 'cs3', 'libregraph' and 'guest'.`|`ldap`|
+|`IDP_URI_BASE_PATH`| 1.0.0 |string|`IDP uri base path (defaults to '').`|``|
+|`IDP_SIGN_IN_URI`| 1.0.0 |string|`IDP sign-in url.`|``|
+|`IDP_SIGN_OUT_URI`| 1.0.0 |string|`IDP sign-out url.`|``|
+|`IDP_ENDPOINT_URI`| 1.0.0 |string|`URL of the IDP endpoint.`|``|
+|`OC_LDAP_INSECURE`<br/>`IDP_INSECURE`| 1.0.0 |bool|`Disable TLS certificate validation for the LDAP connections. Do not set this in production environments.`|`false`|
+|`IDP_ALLOW_CLIENT_GUESTS`| 1.0.0 |bool|`Allow guest clients to access OpenCloud.`|`false`|
+|`IDP_ALLOW_DYNAMIC_CLIENT_REGISTRATION`| 1.0.0 |bool|`Allow dynamic client registration.`|`false`|
+|`IDP_ENCRYPTION_SECRET_FILE`| 1.0.0 |string|`Path to the encryption secret file, if unset, a new certificate will be autogenerated upon each restart, thus invalidating all existing sessions. If not defined, the root directory derives from $OC_BASE_DATA_PATH/idp.`|`/var/lib/opencloud/idp/encryption.key`|
+|`IDP_DEFAULT_SIGNIN_PAGE_TEXT`| 2.0.0 |string|``|``|
+|`IDP_DEFAULT_LOGO_TARGET_URI`| 4.0.0 |string|`Default logo target URI.`|`https://opencloud.eu`|
+|`IDP_SIGNING_KID`| 1.0.0 |string|`Value of the KID (Key ID) field which is used in created tokens to uniquely identify the signing-private-key.`|`private-key`|
+|`IDP_SIGNING_METHOD`| 1.0.0 |string|`Signing method of IDP requests like 'PS256'`|`PS256`|
+|`IDP_SIGNING_PRIVATE_KEY_FILES`| 1.0.0 |[]string|`A list of private key files for signing IDP requests. If not defined, the root directory derives from $OC_BASE_DATA_PATH/idp. See the Environment Variable Types description for more details.`|`[/var/lib/opencloud/idp/private-key.pem]`|
+|`IDP_VALIDATION_KEYS_PATH`| 1.0.0 |string|`Path to validation keys for IDP requests.`|``|
+|`IDP_ACCESS_TOKEN_EXPIRATION`| 1.0.0 |uint64|`'Access token lifespan in seconds (time before an access token is expired).'`|`300`|
+|`IDP_ID_TOKEN_EXPIRATION`| 1.0.0 |uint64|`ID token lifespan in seconds (time before an ID token is expired).`|`300`|
+|`IDP_REFRESH_TOKEN_EXPIRATION`| 1.0.0 |uint64|`Refresh token lifespan in seconds (time before an refresh token is expired). This also limits the duration of an idle offline session.`|`2592000`|
+|`IDP_DYNAMIC_CLIENT_SECRET_DURATION`| 1.0.0 |uint64|`Lifespan in seconds of a dynamically registered OIDC client.`|`0`|
+|`OC_LDAP_URI`<br/>`IDP_LDAP_URI`| 1.0.0 |string|`Url of the LDAP service to use as IDP.`|`ldap://localhost:9236`|
+|`OC_LDAP_CACERT`<br/>`IDP_LDAP_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the LDAP service. If not defined, the root directory derives from $OC_BASE_DATA_PATH/idp.`|``|
+|`OC_LDAP_BIND_DN`<br/>`IDP_LDAP_BIND_DN`| 1.0.0 |string|`LDAP DN to use for simple bind authentication with the target LDAP server.`|`uid=idp,ou=sysusers,o=libregraph-idm`|
+|`OC_LDAP_BIND_PASSWORD`<br/>`IDP_LDAP_BIND_PASSWORD`| 1.0.0 |string|`Password to use for authenticating the 'bind_dn'.`|``|
+|`OC_LDAP_USER_BASE_DN`<br/>`IDP_LDAP_BASE_DN`| 1.0.0 |string|`Search base DN for looking up LDAP users.`|`ou=users,o=libregraph-idm`|
+|`OC_LDAP_USER_SCOPE`<br/>`IDP_LDAP_SCOPE`| 1.0.0 |string|`LDAP search scope to use when looking up users. Supported scopes are 'base', 'one' and 'sub'.`|`sub`|
+|`IDP_LDAP_LOGIN_ATTRIBUTE`| 1.0.0 |string|`LDAP User attribute to use for login like 'uid'.`|`uid`|
+|`OC_LDAP_USER_SCHEMA_MAIL`<br/>`IDP_LDAP_EMAIL_ATTRIBUTE`| 1.0.0 |string|`LDAP User email attribute like 'mail'.`|`mail`|
+|`OC_LDAP_USER_SCHEMA_USERNAME`<br/>`IDP_LDAP_NAME_ATTRIBUTE`| 1.0.0 |string|`LDAP User name attribute like 'displayName'.`|`displayName`|
+|`OC_LDAP_USER_SCHEMA_ID`<br/>`IDP_LDAP_UUID_ATTRIBUTE`| 1.0.0 |string|`LDAP User UUID attribute like 'uid'.`|`openCloudUUID`|
+|`IDP_LDAP_UUID_ATTRIBUTE_TYPE`| 1.0.0 |string|`LDAP User uuid attribute type like 'text'.`|`text`|
+|`OC_LDAP_USER_ENABLED_ATTRIBUTE`<br/>`IDP_USER_ENABLED_ATTRIBUTE`| 1.0.0 |string|`LDAP Attribute to use as a flag telling if the user is enabled or disabled.`|`openCloudUserEnabled`|
+|`OC_LDAP_USER_FILTER`<br/>`IDP_LDAP_FILTER`| 1.0.0 |string|`LDAP filter to add to the default filters for user search like '(objectclass=openCloudUser)'.`|``|
+|`OC_LDAP_USER_OBJECTCLASS`<br/>`IDP_LDAP_OBJECTCLASS`| 1.0.0 |string|`LDAP User ObjectClass like 'inetOrgPerson'.`|`inetOrgPerson`|
diff --git a/versioned_docs/version-7.x/_static/env-vars/idp_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/idp_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/idp_readme.md b/versioned_docs/version-7.x/_static/env-vars/idp_readme.md
new file mode 100755
index 000000000..c2d9fd6b6
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/idp_readme.md
@@ -0,0 +1,92 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+This service provides a builtin minimal OpenID Connect provider based on [LibreGraph Connect (lico)](https://github.com/libregraph/lico) for OpenCloud.
+
+It is mainly targeted at smaller installations. For larger setups it is recommended to replace IDP with an external OpenID Connect Provider.
+
+By default, it is configured to use the OpenCloud IDM service as its LDAP backend for looking up and authenticating users. Other backends like an external LDAP server can be configured via a set of [enviroment variables](https://docs.opencloud.eu/docs/dev/server/services/idp/environment-variables).
+
+Note that translations provided by the IDP service are not maintained via OpenCloud but part of the embedded  [LibreGraph Connect Identifier](https://github.com/libregraph/lico/tree/master/identifier) package.
+
+
+## Table of Contents
+
+* [Configuration](#configuration)
+  * [Custom Clients](#custom-clients)
+
+## Configuration
+
+### Custom Clients
+
+By default the `idp` service generates a OIDC client configuration suitable for
+using OpenCloud with the standard client applications (Web, Desktop, iOS and
+Android). If you need to configure additional client it is possible to inject a
+custom configuration via `yaml`. This can be done by adding a section `clients`
+to the `idp` section of the main configuration file (`opencloud.yaml`). This section
+needs to contain configuration for all clients (including the standard clients).
+
+For example if you want to add a (public) client for use with the oidc-agent you would
+need to add this snippet to the `idp` section in `opencloud.yaml`.
+
+```yaml
+clients:
+- id: web
+  name: OpenCloud Web App
+  trusted: true
+  secret: ""
+  redirect_uris:
+  - https://opencloud.k8s:9200/
+  - https://opencloud.k8s:9200/oidc-callback.html
+  - https://opencloud.k8s:9200/oidc-silent-redirect.html
+  post_logout_redirect_uris: []
+  origins:
+  - https://opencloud.k8s:9200
+  application_type: ""
+- id: OpenCloudDesktop
+  name: OpenCloud Desktop Client
+  trusted: false
+  secret: ""
+  redirect_uris:
+  - http://127.0.0.1
+  - http://localhost
+  post_logout_redirect_uris: []
+  origins: []
+  application_type: native
+- id: OpenCloudAndroid
+  name: OpenCloud Android App
+  trusted: false
+  secret: ""
+  redirect_uris:
+  - oc://android.opencloud.eu
+  post_logout_redirect_uris:
+  - oc://android.opencloud.eu
+  origins: []
+  application_type: native
+- id: OpenCloudIOS
+  name: OpenCloud iOS App
+  trusted: false
+  secret: ""
+  redirect_uris:
+  - oc://ios.opencloud.eu
+  post_logout_redirect_uris:
+  - oc://ios.opencloud.eu
+  origins: []
+  application_type: native
+- id: oidc-agent
+  name: OIDC Agent
+  trusted: false
+  secret: ""
+  redirect_uris:
+  - http://127.0.0.1
+  - http://localhost
+  post_logout_redirect_uris: []
+  origins: []
+  application_type: native
+```
+
+
+
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/invitations.yaml b/versioned_docs/version-7.x/_static/env-vars/invitations.yaml
new file mode 100644
index 000000000..5b61607dd
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/invitations.yaml
@@ -0,0 +1,31 @@
+# Autogenerated
+# Filename: invitations.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9269
+  token: ""
+  pprof: false
+  zpages: false
+http:
+  addr: 127.0.0.1:9265
+  root: /graph/v1.0
+  cors:
+    allow_origins:
+    - https://localhost:9200
+    allow_methods: []
+    allow_headers: []
+    allow_credentials: false
+  tls:
+    enabled: false
+    cert: ""
+    key: ""
+keycloak:
+  base_path: ""
+  client_id: ""
+  client_secret: ""
+  client_realm: ""
+  user_realm: ""
+  insecure_skip_verify: false
+token_manager:
+  jwt_secret: ""
diff --git a/versioned_docs/version-7.x/_static/env-vars/invitations_configvars.md b/versioned_docs/version-7.x/_static/env-vars/invitations_configvars.md
new file mode 100644
index 000000000..62db49b8c
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/invitations_configvars.md
@@ -0,0 +1,25 @@
+## Environment variables for the **invitations** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`INVITATIONS_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`INVITATIONS_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9269`|
+|`INVITATIONS_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`INVITATIONS_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`INVITATIONS_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`INVITATIONS_HTTP_ADDR`| 1.0.0 |string|`The bind address of the HTTP service.`|`127.0.0.1:9265`|
+|`INVITATIONS_HTTP_ROOT`| 1.0.0 |string|`Subdirectory that serves as the root for this HTTP service.`|`/graph/v1.0`|
+|`OC_CORS_ALLOW_ORIGINS`<br/>`INVITATIONS_CORS_ALLOW_ORIGINS`| 1.0.0 |[]string|`A list of allowed CORS origins. See following chapter for more details: *Access-Control-Allow-Origin* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin. See the Environment Variable Types description for more details.`|`[https://localhost:9200]`|
+|`OC_CORS_ALLOW_METHODS`<br/>`INVITATIONS_CORS_ALLOW_METHODS`| 1.0.0 |[]string|`A list of allowed CORS methods. See following chapter for more details: *Access-Control-Request-Method* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Method. See the Environment Variable Types description for more details.`|`[]`|
+|`OC_CORS_ALLOW_HEADERS`<br/>`INVITATIONS_CORS_ALLOW_HEADERS`| 1.0.0 |[]string|`A list of allowed CORS headers. See following chapter for more details: *Access-Control-Request-Headers* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Headers. See the Environment Variable Types description for more details.`|`[]`|
+|`OC_CORS_ALLOW_CREDENTIALS`<br/>`INVITATIONS_CORS_ALLOW_CREDENTIALS`| 1.0.0 |bool|`Allow credentials for CORS.See following chapter for more details: *Access-Control-Allow-Credentials* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Credentials.`|`false`|
+|`OC_HTTP_TLS_ENABLED`| 1.0.0 |bool|`Activates TLS for the http based services using the server certifcate and key configured via OC_HTTP_TLS_CERTIFICATE and OC_HTTP_TLS_KEY. If OC_HTTP_TLS_CERTIFICATE is not set a temporary server certificate is generated - to be used with PROXY_INSECURE_BACKEND=true.`|`false`|
+|`OC_HTTP_TLS_CERTIFICATE`| 1.0.0 |string|`Path/File name of the TLS server certificate (in PEM format) for the http services.`|``|
+|`OC_HTTP_TLS_KEY`| 1.0.0 |string|`Path/File name for the TLS certificate key (in PEM format) for the server certificate to use for the http services.`|``|
+|`OC_KEYCLOAK_BASE_PATH`<br/>`INVITATIONS_KEYCLOAK_BASE_PATH`| 1.0.0 |string|`The URL to access keycloak.`|``|
+|`OC_KEYCLOAK_CLIENT_ID`<br/>`INVITATIONS_KEYCLOAK_CLIENT_ID`| 1.0.0 |string|`The client ID to authenticate with keycloak.`|``|
+|`OC_KEYCLOAK_CLIENT_SECRET`<br/>`INVITATIONS_KEYCLOAK_CLIENT_SECRET`| 1.0.0 |string|`The client secret to use in authentication.`|``|
+|`OC_KEYCLOAK_CLIENT_REALM`<br/>`INVITATIONS_KEYCLOAK_CLIENT_REALM`| 1.0.0 |string|`The realm the client is defined in.`|``|
+|`OC_KEYCLOAK_USER_REALM`<br/>`INVITATIONS_KEYCLOAK_USER_REALM`| 1.0.0 |string|`The realm users are defined.`|``|
+|`OC_KEYCLOAK_INSECURE_SKIP_VERIFY`<br/>`INVITATIONS_KEYCLOAK_INSECURE_SKIP_VERIFY`| 1.0.0 |bool|`Disable TLS certificate validation for Keycloak connections. Do not set this in production environments.`|`false`|
+|`OC_JWT_SECRET`<br/>`INVITATIONS_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
diff --git a/versioned_docs/version-7.x/_static/env-vars/invitations_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/invitations_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/invitations_readme.md b/versioned_docs/version-7.x/_static/env-vars/invitations_readme.md
new file mode 100755
index 000000000..92cb10047
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/invitations_readme.md
@@ -0,0 +1,58 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The invitations service provides an [Invitation Manager](https://learn.microsoft.com/en-us/graph/api/invitation-post?view=graph-rest-1.0&tabs=http) that can be used to invite external users, aka guests, to an organization.
+
+*   Users invited via the Invitation Manager (via the libre graph API) will have the `userType="Guest"`.
+*   Users belonging to the organization have the `userType="Member"`.
+
+The corresponding CS3 API [user types](https://cs3org.github.io/cs3apis/#cs3.identity.user.v1beta1.UserType) used to reperesent this are: `USER_TYPE_GUEST` and `USER_TYPE_PRIMARY`.
+
+
+## Table of Contents
+
+* [Provisioning Backends](#provisioning-backends)
+  * [Keycloak](#keycloak)
+    * [Keycloak Realm Configuration](#keycloak-realm-configuration)
+* [Backend Configuration](#backend-configuration)
+* [Bridging Provisioning Delay](#bridging-provisioning-delay)
+
+## Provisioning Backends
+
+When OpenCloud is used via the IDM service for the user management, users are created using the `/graph/v1.0/users` endpoint via the libre graph API. For larger deployments, the Keycloak admin API can be used to provision users. In a future step, the endpoint, credentials and body might be made configurable using templates.
+
+### Keycloak
+
+The default and currently only available backend used to handle invitations is [Keycloak](https://www.keycloak.org/). Keycloak is an open source identity and access management (IAM) system which is also integrated by other OpenCloud services as an authentication and authorization backend.
+
+#### Keycloak Realm Configuration
+
+<!--- Note that the link below must be an absolute URL and not a relative file path --->
+
+See the [example configuration json file](https://github.com/opencloud-eu/opencloud/blob/main/services/invitations/md-sources/example-realm.json) of a Keycloak realm the backend will work with. This file includes the `invitations` client, which is relevant for this service.
+
+To use the example json, set the `INVITATIONS_KEYCLOAK_CLIENT_ID` setting to `invitations`, though any other client ID can be configured. 
+
+Importing this example into Keycloak will give you a realm that federates with an LDAP server, has the right
+clients configured and all mappers correctly set. Be sure to set all the credentials after the import,
+as they will be disabled.
+
+The most relevant bits are the mappers for the `OPENCLOUD_ID` and `OPENCLOUD_USER_TYPE` user properties.
+
+## Backend Configuration
+
+After Keycloak has been configured, the invitation service needs to be configured with the following environment variables:
+
+* `INVITATIONS_KEYCLOAK_BASE_PATH`: The URL to access Keycloak.
+* `INVITATIONS_KEYCLOAK_CLIENT_ID`: The client ID of the client to use. In the above example, `invitations` is used.
+* `INVITATIONS_KEYCLOAK_CLIENT_SECRET`: The client secret used to authenticate. This can be found in the Keycloak UI.
+* `INVITATIONS_KEYCLOAK_CLIENT_REALM`: The realm where the client was added. In the example above, `opencloud` is used.
+* `INVITATIONS_KEYCLOAK_USER_REALM`: The realm where to add the users. In the example above, `opencloud` is used.
+* `INVITATIONS_KEYCLOAK_INSECURE_SKIP_VERIFY`: If set to true, the verification of the Keycloak HTTPS certificate is skipped. This is not recommended in production environments.
+
+## Bridging Provisioning Delay
+
+Consider that when a guest account has to be provisioned in an external user management, there might be a delay between creating the user and the user being available in the local OpenCloud system.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/nats.yaml b/versioned_docs/version-7.x/_static/env-vars/nats.yaml
new file mode 100644
index 000000000..919f81a74
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/nats.yaml
@@ -0,0 +1,18 @@
+# Autogenerated
+# Filename: nats.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9234
+  token: ""
+  pprof: false
+  zpages: false
+nats:
+  host: 127.0.0.1
+  port: 9233
+  clusterid: opencloud-cluster
+  store_dir: /var/lib/opencloud/nats
+  tls_cert: /var/lib/opencloud/nats/tls.crt
+  tls_key: /var/lib/opencloud/nats/tls.key
+  tls_skip_verify_client_cert: false
+  enable_tls: false
diff --git a/versioned_docs/version-7.x/_static/env-vars/nats_configvars.md b/versioned_docs/version-7.x/_static/env-vars/nats_configvars.md
new file mode 100644
index 000000000..e8deae91f
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/nats_configvars.md
@@ -0,0 +1,17 @@
+## Environment variables for the **nats** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`NATS_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`NATS_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9234`|
+|`NATS_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`NATS_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`NATS_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`NATS_NATS_HOST`| 1.0.0 |string|`Bind address.`|`127.0.0.1`|
+|`NATS_NATS_PORT`| 1.0.0 |int|`Bind port.`|`9233`|
+|`NATS_NATS_CLUSTER_ID`| 1.0.0 |string|`ID of the NATS cluster.`|`opencloud-cluster`|
+|`NATS_NATS_STORE_DIR`| 1.0.0 |string|`The directory where the filesystem storage will store NATS JetStream data. If not defined, the root directory derives from $OC_BASE_DATA_PATH/nats.`|`/var/lib/opencloud/nats`|
+|`NATS_TLS_CERT`| 1.0.0 |string|`Path/File name of the TLS server certificate (in PEM format) for the NATS listener. If not defined, the root directory derives from $OC_BASE_DATA_PATH/nats.`|`/var/lib/opencloud/nats/tls.crt`|
+|`NATS_TLS_KEY`| 1.0.0 |string|`Path/File name for the TLS certificate key (in PEM format) for the NATS listener. If not defined, the root directory derives from $OC_BASE_DATA_PATH/nats.`|`/var/lib/opencloud/nats/tls.key`|
+|`OC_INSECURE`<br/>`NATS_TLS_SKIP_VERIFY_CLIENT_CERT`| 1.0.0 |bool|`Whether the NATS server should skip the client certificate verification during the TLS handshake.`|`false`|
+|`OC_EVENTS_ENABLE_TLS`<br/>`NATS_EVENTS_ENABLE_TLS`| 1.0.0 |bool|`Enable TLS for the connection to the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|`false`|
diff --git a/versioned_docs/version-7.x/_static/env-vars/nats_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/nats_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/nats_readme.md b/versioned_docs/version-7.x/_static/env-vars/nats_readme.md
new file mode 100755
index 000000000..9f232cea0
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/nats_readme.md
@@ -0,0 +1,37 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The nats service is the event broker of the system. It distributes events among all other services and enables other services to communicate asynchronous.
+
+Services can `Publish` events to the nats service and nats will store these events on disk and distribute these events to other services eventually. Services can `Consume` events from the nats service by registering to a `ConsumerGroup`. Each `ConsumerGroup` is guaranteed to get each event exactly once. In most cases, each service will register its own `ConsumerGroup`. When there are multiple instances of a service, those instances will usually use that `ConsumerGroup` as common resource.
+
+
+## Table of Contents
+
+* [Underlying Technology](#underlying-technology)
+* [Default Registry](#default-registry)
+* [Persistance](#persistance)
+* [TLS Encryption](#tls-encryption)
+
+## Underlying Technology
+
+As the service name suggests, this service is based on [NATS](https://nats.io/) specifically on [NATS Jetstream](https://docs.nats.io/nats-concepts/jetstream) to enable persistence.
+
+## Default Registry
+
+By default, `nats-js-kv` is configured as embedded default registry via the `MICRO_REGISTRY` environment variable. If you do not want using the build-in nats registry, set `MICRO_REGISTRY_ADDRESS` to the address of the nats-js cluster, which is the same value as `OC_EVENTS_ENDPOINT`. Optionally use `MICRO_REGISTRY_AUTH_USERNAME` and `MICRO_REGISTRY_AUTH_PASSWORD` to authenticate with the external nats cluster.
+
+## Persistance
+
+To be able to deliver events even after a system or service restart, nats will store events in a folder on the local filesystem. This folder can be specified by setting the `NATS_NATS_STORE_DIR` enviroment variable. If not set, the service will fall back to `$OC_BASE_DATA_PATH/nats`.
+
+## TLS Encryption
+
+Connections to the nats service (`Publisher`/`Consumer` see above) can be TLS encrypted by setting the corresponding env vars `NATS_TLS_CERT`, `NATS_TLS_KEY` to the cert and key files and `ENABLE_TLS` to true. Checking the certificate of incoming request can be disabled with the `NATS_EVENTS_ENABLE_TLS` environment variable.
+
+Certificate files can also be set via global variables starting with `OC_`, for details see the environment variable list.
+
+Note that using TLS is highly recommended for productive environments, especially when using container orchestration with Kubernetes.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/notifications.yaml b/versioned_docs/version-7.x/_static/env-vars/notifications.yaml
new file mode 100644
index 000000000..0c49b9ae4
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/notifications.yaml
@@ -0,0 +1,51 @@
+# Autogenerated
+# Filename: notifications.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9174
+  token: ""
+  pprof: false
+  zpages: false
+opencloud_url: https://localhost:9200
+notifications:
+  SMTP:
+    smtp_host: ""
+    smtp_port: 0
+    smtp_sender: ""
+    smtp_username: ""
+    smtp_password: ""
+    insecure: false
+    smtp_authentication: ""
+    smtp_encryption: none
+  events:
+    endpoint: 127.0.0.1:9233
+    cluster: opencloud-cluster
+    tls_insecure: false
+    tls_root_ca_certificate: ""
+    enable_tls: false
+    username: ""
+    password: ""
+  email_template_path: ""
+  translation_path: ""
+  default_language: ""
+  reva_gateway: eu.opencloud.api.gateway
+  grpc_client_tls: null
+grpc_client_tls:
+  mode: ""
+  cacert: ""
+service_account:
+  service_account_id: ""
+  service_account_secret: ""
+store:
+  store: nats-js-kv
+  nodes:
+  - 127.0.0.1:9233
+  database: notifications
+  table: ""
+  ttl: 336h0m0s
+  username: ""
+  password: ""
+  enable_tls: false
+  tls_insecure: false
+  tls_root_ca_certificate: ""
diff --git a/versioned_docs/version-7.x/_static/env-vars/notifications_configvars.md b/versioned_docs/version-7.x/_static/env-vars/notifications_configvars.md
new file mode 100644
index 000000000..3e8a1c13c
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/notifications_configvars.md
@@ -0,0 +1,43 @@
+## Environment variables for the **notifications** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`NOTIFICATIONS_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`NOTIFICATIONS_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9174`|
+|`NOTIFICATIONS_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`NOTIFICATIONS_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`NOTIFICATIONS_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`OC_URL`<br/>`NOTIFICATIONS_WEB_UI_URL`| 1.0.0 |string|`The public facing URL of the OpenCloud Web UI, used e.g. when sending notification eMails`|`https://localhost:9200`|
+|`NOTIFICATIONS_SMTP_HOST`| 1.0.0 |string|`SMTP host to connect to.`|``|
+|`NOTIFICATIONS_SMTP_PORT`| 1.0.0 |int|`Port of the SMTP host to connect to.`|`0`|
+|`NOTIFICATIONS_SMTP_SENDER`| 1.0.0 |string|`Sender address of emails that will be sent (e.g. 'OpenCloud <noreply@example.com>'.`|``|
+|`NOTIFICATIONS_SMTP_USERNAME`| 1.0.0 |string|`Username for the SMTP host to connect to.`|``|
+|`NOTIFICATIONS_SMTP_PASSWORD`| 1.0.0 |string|`Password for the SMTP host to connect to.`|``|
+|`NOTIFICATIONS_SMTP_INSECURE`| 1.0.0 |bool|`Allow insecure connections to the SMTP server.`|`false`|
+|`NOTIFICATIONS_SMTP_AUTHENTICATION`| 1.0.0 |string|`Authentication method for the SMTP communication. Possible values are 'login', 'plain', 'crammd5', 'none' or 'auto'. If set to 'auto' or unset, the authentication method is automatically negotiated with the server.`|``|
+|`NOTIFICATIONS_SMTP_ENCRYPTION`| 1.0.0 |string|`Encryption method for the SMTP communication. Possible values are 'starttls', 'ssltls' and 'none'.`|`none`|
+|`OC_EVENTS_ENDPOINT`<br/>`NOTIFICATIONS_EVENTS_ENDPOINT`| 1.0.0 |string|`The address of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture.`|`127.0.0.1:9233`|
+|`OC_EVENTS_CLUSTER`<br/>`NOTIFICATIONS_EVENTS_CLUSTER`| 1.0.0 |string|`The clusterID of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture. Mandatory when using NATS as event system.`|`opencloud-cluster`|
+|`OC_INSECURE`<br/>`OC_EVENTS_TLS_INSECURE`<br/>`NOTIFICATIONS_EVENTS_TLS_INSECURE`| 1.0.0 |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_EVENTS_TLS_ROOT_CA_CERTIFICATE`<br/>`NOTIFICATIONS_EVENTS_TLS_ROOT_CA_CERTIFICATE`| 1.0.0 |string|`The root CA certificate used to validate the server's TLS certificate. If provided NOTIFICATIONS_EVENTS_TLS_INSECURE will be seen as false.`|``|
+|`OC_EVENTS_ENABLE_TLS`<br/>`NOTIFICATIONS_EVENTS_ENABLE_TLS`| 1.0.0 |bool|`Enable TLS for the connection to the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|`false`|
+|`OC_EVENTS_AUTH_USERNAME`<br/>`NOTIFICATIONS_EVENTS_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_EVENTS_AUTH_PASSWORD`<br/>`NOTIFICATIONS_EVENTS_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_EMAIL_TEMPLATE_PATH`<br/>`NOTIFICATIONS_EMAIL_TEMPLATE_PATH`| 1.0.0 |string|`Path to Email notification templates overriding embedded ones.`|``|
+|`OC_TRANSLATION_PATH`<br/>`NOTIFICATIONS_TRANSLATION_PATH`| 1.0.0 |string|`(optional) Set this to a path with custom translations to overwrite the builtin translations. Note that file and folder naming rules apply, see the documentation for more details.`|``|
+|`OC_DEFAULT_LANGUAGE`| 1.0.0 |string|`The default language used by services and the WebUI. If not defined, English will be used as default. See the documentation for more details.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`CS3 gateway used to look up user metadata`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
+|`OC_SERVICE_ACCOUNT_ID`<br/>`NOTIFICATIONS_SERVICE_ACCOUNT_ID`| 1.0.0 |string|`The ID of the service account the service should use. See the 'auth-service' service description for more details.`|``|
+|`OC_SERVICE_ACCOUNT_SECRET`<br/>`NOTIFICATIONS_SERVICE_ACCOUNT_SECRET`| 1.0.0 |string|`The service account secret.`|``|
+|`OC_PERSISTENT_STORE`<br/>`NOTIFICATIONS_STORE`| 1.0.0 |string|`The type of the store. Supported values are: 'memory', 'nats-js-kv', 'redis-sentinel', 'noop'. See the text description for details.`|`nats-js-kv`|
+|`OC_PERSISTENT_STORE_NODES`<br/>`NOTIFICATIONS_STORE_NODES`| 1.0.0 |[]string|`A list of nodes to access the configured store. This has no effect when 'memory' store is configured. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details.`|`[127.0.0.1:9233]`|
+|`NOTIFICATIONS_STORE_DATABASE`| 1.0.0 |string|`The database name the configured store should use.`|`notifications`|
+|`NOTIFICATIONS_STORE_TABLE`| 1.0.0 |string|`The database table the store should use.`|``|
+|`OC_PERSISTENT_STORE_TTL`<br/>`NOTIFICATIONS_STORE_TTL`| 1.0.0 |Duration|`Time to live for notifications in the store. Defaults to '336h' (2 weeks). See the Environment Variable Types description for more details.`|`336h0m0s`|
+|`OC_PERSISTENT_STORE_AUTH_USERNAME`<br/>`NOTIFICATIONS_STORE_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_PERSISTENT_STORE_AUTH_PASSWORD`<br/>`NOTIFICATIONS_STORE_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_PERSISTENT_STORE_ENABLE_TLS`<br/>`NOTIFICATIONS_STORE_ENABLE_TLS`| next |bool|`Enable TLS for the connection to the store. Only applies when store type 'nats-js-kv' is configured.`|`false`|
+|`OC_INSECURE`<br/>`OC_PERSISTENT_STORE_TLS_INSECURE`<br/>`NOTIFICATIONS_STORE_TLS_INSECURE`| next |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_PERSISTENT_STORE_TLS_ROOT_CA_CERTIFICATE`<br/>`NOTIFICATIONS_STORE_TLS_ROOT_CA_CERTIFICATE`| next |string|`The root CA certificate used to validate the server's TLS certificate. If provided NOTIFICATIONS_STORE_TLS_INSECURE will be seen as false.`|``|
diff --git a/versioned_docs/version-7.x/_static/env-vars/notifications_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/notifications_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/notifications_readme.md b/versioned_docs/version-7.x/_static/env-vars/notifications_readme.md
new file mode 100755
index 000000000..ab986e6de
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/notifications_readme.md
@@ -0,0 +1,120 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The notification service is responsible for sending emails to users informing them about events that happened. To do this, it hooks into the event system and listens for certain events that the users need to be informed about.
+
+
+## Table of Contents
+
+* [Email Notification Templates](#email-notification-templates)
+  * [Templates subfolder hierarchy](#templates-subfolder-hierarchy)
+* [Sending Grouped Emails](#sending-grouped-emails)
+  * [Storing](#storing)
+* [Translations](#translations)
+  * [Translation Rules](#translation-rules)
+* [Default Language](#default-language)
+
+## Email Notification Templates
+
+The `notifications` service has embedded email text and html body templates.
+
+Email templates can use the placeholders `{{ .Greeting }}`, `{{ .MessageBody }}` and `{{ .CallToAction }}` which are replaced with translations when sent, see the [Translations](#translations) section for more details. Though the email subject is also part of translations, it has no placeholder as it is a mandatory email component.
+
+Depending on the email purpose, placeholders will contain different strings. An individual translatable string is available for each purpose, finally resolved by the placeholder. The embedded templates are available for all deployment scenarios.
+
+```text
+template
+  placeholders
+    translated strings <-- source strings <-- purpose
+final output
+```
+
+In addition, the notifications service supports custom templates. Custom email templates take precedence over the embedded ones. If a custom email template exists, the embedded templates are not used. To configure custom email templates, the `NOTIFICATIONS_EMAIL_TEMPLATE_PATH` environment variable needs to point to a base folder that will contain the email templates and follow the [templates subfolder hierarchy](#templates-subfolder-hierarchy).This path must be available from all instances of the notifications service, a shared storage is recommended.
+```text
+{NOTIFICATIONS_EMAIL_TEMPLATE_PATH}/templates/text/email.text.tmpl
+{NOTIFICATIONS_EMAIL_TEMPLATE_PATH}/templates/html/email.html.tmpl
+{NOTIFICATIONS_EMAIL_TEMPLATE_PATH}/templates/html/img/
+```
+The source templates provided by OpenCloud you can derive from are located in the following base folder [https://github.com/opencloud-eu/opencloud/tree/main/services/notifications/pkg/email/templates](https://github.com/opencloud-eu/opencloud/tree/main/services/notifications/pkg/email/templates) with subfolders `templates/text` and `templates/html`.
+
+-   [text/email.text.tmpl](https://github.com/opencloud-eu/opencloud/blob/main/services/notifications/pkg/email/templates/text/email.text.tmpl)
+-   [html/email.html.tmpl](https://github.com/opencloud-eu/opencloud/blob/main/services/notifications/pkg/email/templates/html/email.html.tmpl)
+
+### Templates subfolder hierarchy
+```text
+templates
+│
+└───html
+│   │   email.html.tmpl
+│   │
+│   └───img
+│       │   logo-mail.gif
+│
+└───text
+    │   email.text.tmpl
+```
+
+Custom email templates referenced via `NOTIFICATIONS_EMAIL_TEMPLATE_PATH` must also be located in subfolder `templates/text` and `templates/html` and must have the same names as the embedded templates. It is important that the names of these files and folders match the embedded ones.
+The `templates/html` subfolder contains a default HTML template provided by OpenCloud. When using a custom HTML template, hosted images can either be linked with standard HTML code like ```<img src="https://raw.githubusercontent.com/opencloud-eu/opencloud/master/opencloud/img/logo-mail.gif" alt="logo-mail"/>``` or embedded as a CID source ```<img src="cid:logo-mail.gif" alt="logo-mail"/>```. In the latter case, image files must be located in the `templates/html/img` subfolder. Supported embedded image types are png, jpeg, and gif.
+Consider that embedding images via a CID resource may not be fully supported in all email web clients.
+
+## Sending Grouped Emails
+
+The `notification` service can initiate sending emails based on events stored in the configured store that are grouped into a `daily` or `weekly` bucket. These groups contain events that get populated e.g. when the user configures `daily` or `weekly` email notifications in his personal settings in the web UI. If a user does not define any of the named groups for notification events, no event is stored.
+
+Grouped events are stored for the TTL defined in `OC_PERSISTENT_STORE_TTL`. This TTL can either be configured globally or individually for the notification service via the `NOTIFICATIONS_STORE_TTL` envvar.
+
+Grouped events that have passed the TTL are removed automatically without further notice or sending!
+
+To initiate sending grouped emails like via a cron job, use the `opencloud notifications send-email` command. Note that the command mandatory requires at least one option which is `--daily` or `--weekly`. Note that both options can be used together.
+
+### Storing
+
+The `notifications` service persists information via the configured store in `NOTIFICATIONS_STORE`. Possible stores are:
+-   `memory`: Basic in-memory store. Will not survive a restart. This is not recommended for this service.
+-   `redis-sentinel`: Stores data in a configured Redis Sentinel cluster.
+-   `nats-js-kv`: Stores data using key-value-store feature of [nats jetstream](https://docs.nats.io/nats-concepts/jetstream/key-value-store). This is the default value.
+-   `noop`: Stores nothing. Useful for testing. Not recommended in production environments.
+
+Other store types may work but are not supported currently.
+
+Note: The service can only be scaled if not using `memory` store and the stores are configured identically over all instances!
+
+Note that if you have used one of the deprecated stores, you should reconfigure to one of the supported ones as the deprecated stores will be removed in a later version.
+
+Store specific notes:
+-   When using `redis-sentinel`, the Redis master to use is configured via e.g. `OC_CACHE_STORE_NODES` in the form of `<sentinel-host>:<sentinel-port>/<redis-master>` like `10.10.0.200:26379/mymaster`.
+-   When using `nats-js-kv` it is recommended to set `OC_CACHE_STORE_NODES` to the same value as `OC_EVENTS_ENDPOINT`. That way the cache uses the same nats instance as the event bus.
+-   When using the `nats-js-kv` store, it is possible to set `OC_CACHE_DISABLE_PERSISTENCE` to instruct nats to not persist cache data on disc.
+
+## Translations
+
+The `notifications` service has embedded translations sourced via transifex to provide a basic set of translated languages. These embedded translations are available for all deployment scenarios.
+
+In addition, the service supports custom translations, though it is currently not possible to just add custom translations to embedded ones. If custom translations are configured, the embedded ones are not used. To configure custom translations,
+the `NOTIFICATIONS_TRANSLATION_PATH` environment variable needs to point to a base folder that will contain the translation files. This path must be available from all instances of the notifications service, a shared storage is recommended. Translation files must be of type  [.po](https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html#PO-Files) or [.mo](https://www.gnu.org/software/gettext/manual/html_node/Binaries.html). For each language, the filename needs to be `notifications.po` (or `notifications.mo`) and stored in a folder structure defining the language code. In general the path/name pattern for a translation file needs to be:
+
+```text
+{NOTIFICATIONS_TRANSLATION_PATH}/{language-code}/LC_MESSAGES/notifications.po
+```
+
+The language code pattern is composed of `language[_territory]` where  `language` is the base language and `_territory` is optional and defines a country.
+
+For example, for the language `de`, one needs to place the corresponding translation files to `{NOTIFICATIONS_TRANSLATION_PATH}/de/LC_MESSAGES/notifications.po`.
+
+<!-- also see the userlog readme -->
+
+Important: For the time being, the embedded OpenCloud Web frontend only supports the main language code but does not handle any territory. When strings are available in the language code `language_territory`, the web frontend does not see it as it only requests `language`. In consequence, any translations made must exist in the requested `language` to avoid a fallback to the default.
+
+### Translation Rules
+
+*   If a requested language code is not available, the service tries to fall back to the base language if available. For example, if the requested language-code `de_DE` is not available, the service tries to fall back to translations in the `de` folder.
+*   If the base language `de` is also not available, the service falls back to the system's default English (`en`),
+which is the source of the texts provided by the code.
+
+## Default Language
+
+The default language can be defined via the `OC_DEFAULT_LANGUAGE` environment variable. See the `settings` service for a detailed description.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/ocm.yaml b/versioned_docs/version-7.x/_static/env-vars/ocm.yaml
new file mode 100644
index 000000000..89b9d4b89
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/ocm.yaml
@@ -0,0 +1,110 @@
+# Autogenerated
+# Filename: ocm.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9281
+  token: ""
+  pprof: false
+  zpages: false
+http:
+  addr: 127.0.0.1:9280
+  protocol: tcp
+  prefix: ""
+  cors:
+    allow_origins:
+    - https://localhost:9200
+    allow_methods:
+    - OPTIONS
+    - HEAD
+    - GET
+    - PUT
+    - POST
+    - DELETE
+    - MKCOL
+    - PROPFIND
+    - PROPPATCH
+    - MOVE
+    - COPY
+    - REPORT
+    - SEARCH
+    allow_headers:
+    - Origin
+    - Accept
+    - Content-Type
+    - Depth
+    - Authorization
+    - Ocs-Apirequest
+    - If-None-Match
+    - If-Match
+    - Destination
+    - Overwrite
+    - X-Request-Id
+    - X-Requested-With
+    - Tus-Resumable
+    - Tus-Checksum-Algorithm
+    - Upload-Concat
+    - Upload-Length
+    - Upload-Metadata
+    - Upload-Defer-Length
+    - Upload-Expires
+    - Upload-Checksum
+    - Upload-Offset
+    - X-HTTP-Method-Override
+    - Cache-Control
+    allow_credentials: false
+middleware:
+  auth:
+    credentials_by_user_agent: {}
+grpc:
+  addr: 127.0.0.1:9282
+  tls: null
+  protocol: ""
+grpc_client_tls: null
+service_account:
+  service_account_id: ""
+  service_account_secret: ""
+token_manager:
+  jwt_secret: ""
+reva:
+  address: eu.opencloud.api.gateway
+  tls:
+    mode: ""
+    cacert: ""
+ocmd:
+  prefix: ocm
+  expose_recipient_display_name: false
+sciencemesh:
+  prefix: sciencemesh
+  science_mesh_directory_url: ""
+  directory_service_urls: ""
+  invite_accept_dialog: /open-cloud-mesh/accept-invite
+  ocm_client_insecure: false
+ocm_invite_manager:
+  driver: json
+  drivers:
+    json:
+      file: /var/lib/opencloud/storage/ocm/ocminvites.json
+  token_expiration: 24h0m0s
+  timeout: 30s
+  insecure: false
+ocm_provider_authorizer_driver: json
+ocm_provider_authorizer_drivers:
+  json:
+    providers: /etc/opencloud/ocmproviders.json
+ocm_share_provider:
+  driver: json
+  drivers:
+    json:
+      file: /var/lib/opencloud/storage/ocm/ocmshares.json
+  insecure: false
+  webapp_template: ""
+ocm_core:
+  driver: json
+  drivers:
+    json:
+      file: /var/lib/opencloud/storage/ocm/ocmshares.json
+ocm_storage_provider:
+  insecure: false
+  storage_root: /var/lib/opencloud/storage/ocm
+  data_server_url: http://localhost:9280/data
diff --git a/versioned_docs/version-7.x/_static/env-vars/ocm_configvars.md b/versioned_docs/version-7.x/_static/env-vars/ocm_configvars.md
new file mode 100644
index 000000000..700dceaa6
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/ocm_configvars.md
@@ -0,0 +1,54 @@
+## Environment variables for the **ocm** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`OCM_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`OCM_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9281`|
+|`OCM_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`OCM_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`OCM_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`OCM_HTTP_ADDR`| 1.0.0 |string|`The bind address of the HTTP service.`|`127.0.0.1:9280`|
+|`OCM_HTTP_PROTOCOL`| 1.0.0 |string|`The transport protocol of the HTTP service.`|`tcp`|
+|`OCM_HTTP_PREFIX`| 1.0.0 |string|`The path prefix where OCM can be accessed (defaults to /).`|``|
+|`OC_CORS_ALLOW_ORIGINS`<br/>`OCM_CORS_ALLOW_ORIGINS`| 1.0.0 |[]string|`A list of allowed CORS origins. See following chapter for more details: *Access-Control-Allow-Origin* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin. See the Environment Variable Types description for more details.`|`[https://localhost:9200]`|
+|`OC_CORS_ALLOW_METHODS`<br/>`OCM_CORS_ALLOW_METHODS`| 1.0.0 |[]string|`A list of allowed CORS methods. See following chapter for more details: *Access-Control-Request-Method* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Method. See the Environment Variable Types description for more details.`|`[OPTIONS HEAD GET PUT POST DELETE MKCOL PROPFIND PROPPATCH MOVE COPY REPORT SEARCH]`|
+|`OC_CORS_ALLOW_HEADERS`<br/>`OCM_CORS_ALLOW_HEADERS`| 1.0.0 |[]string|`A list of allowed CORS headers. See following chapter for more details: *Access-Control-Request-Headers* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Headers. See the Environment Variable Types description for more details.`|`[Origin Accept Content-Type Depth Authorization Ocs-Apirequest If-None-Match If-Match Destination Overwrite X-Request-Id X-Requested-With Tus-Resumable Tus-Checksum-Algorithm Upload-Concat Upload-Length Upload-Metadata Upload-Defer-Length Upload-Expires Upload-Checksum Upload-Offset X-HTTP-Method-Override Cache-Control]`|
+|`OC_CORS_ALLOW_CREDENTIALS`<br/>`OCM_CORS_ALLOW_CREDENTIALS`| 1.0.0 |bool|`Allow credentials for CORS.See following chapter for more details: *Access-Control-Allow-Credentials* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Credentials.`|`false`|
+|`OCM_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9282`|
+|`OC_GRPC_PROTOCOL`<br/>`OCM_GRPC_PROTOCOL`| 1.0.0 |string|`The transport protocol of the GRPC service.`|``|
+|`OC_SERVICE_ACCOUNT_ID`<br/>`OCM_SERVICE_ACCOUNT_ID`| 1.0.0 |string|`The ID of the service account the service should use. See the 'auth-service' service description for more details.`|``|
+|`OC_SERVICE_ACCOUNT_SECRET`<br/>`OCM_SERVICE_ACCOUNT_SECRET`| 1.0.0 |string|`The service account secret.`|``|
+|`OC_EVENTS_ENDPOINT`<br/>`OCM_EVENTS_ENDPOINT`| 1.0.0 |string|`The address of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture.`|`127.0.0.1:9233`|
+|`OC_EVENTS_CLUSTER`<br/>`OCM_EVENTS_CLUSTER`| 1.0.0 |string|`The clusterID of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture. Mandatory when using NATS as event system.`|`opencloud-cluster`|
+|`OC_INSECURE`<br/>`OC_EVENTS_TLS_INSECURE`<br/>`OCM_EVENTS_TLS_INSECURE`| 1.0.0 |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_EVENTS_TLS_ROOT_CA_CERTIFICATE`<br/>`OCM_EVENTS_TLS_ROOT_CA_CERTIFICATE`| 1.0.0 |string|`The root CA certificate used to validate the server's TLS certificate. If provided OCM_EVENTS_TLS_INSECURE will be seen as false.`|``|
+|`OC_EVENTS_ENABLE_TLS`<br/>`OCM_EVENTS_ENABLE_TLS`| 1.0.0 |bool|`Enable TLS for the connection to the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|`false`|
+|`OC_EVENTS_AUTH_USERNAME`<br/>`OCM_EVENTS_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_EVENTS_AUTH_PASSWORD`<br/>`OCM_EVENTS_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_JWT_SECRET`<br/>`OCM_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`The CS3 gateway endpoint.`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
+|`OCM_OCMD_PREFIX`| 1.0.0 |string|`URL path prefix for the OCMD service. Note that the string must not start with '/'.`|`ocm`|
+|`OCM_OCMD_EXPOSE_RECIPIENT_DISPLAY_NAME`| 1.0.0 |bool|`Expose the display name of OCM share recipients.`|`false`|
+|`OCM_SCIENCEMESH_PREFIX`| 1.0.0 |string|`URL path prefix for the ScienceMesh service. Note that the string must not start with '/'.`|`sciencemesh`|
+|`OCM_MESH_DIRECTORY_URL`| 1.0.0 |string|`URL of the mesh directory service.`|``|
+|`OCM_DIRECTORY_SERVICE_URLS`| 3.5.0 |string|`Space delimited URLs of the directory services.`|``|
+|`OCM_INVITE_ACCEPT_DIALOG`| 3.5.0 |string|`/open-cloud-mesh/accept-invite;The frontend URL where to land when receiving an invitation`|`/open-cloud-mesh/accept-invite`|
+|`OC_INSECURE`<br/>`OCM_CLIENT_INSECURE`| 6.0.0 |bool|`Dev-only. Disable TLS verification for the OCM discovery client (directory fetch and provider discovery). Does not affect OCM invite manager, storage provider, or share provider. Do not set in production.`|`false`|
+|`OCM_OCM_INVITE_MANAGER_DRIVER`| 1.0.0 |string|`Driver to be used to persist OCM invites. Supported value is only 'json'.`|`json`|
+|`OCM_OCM_INVITE_MANAGER_JSON_FILE`| 1.0.0 |string|`Path to the JSON file where OCM invite data will be stored. This file is maintained by the instance and must not be changed manually. If not defined, the root directory derives from $OC_BASE_DATA_PATH/storage/ocm.`|`/var/lib/opencloud/storage/ocm/ocminvites.json`|
+|`OCM_OCM_INVITE_MANAGER_TOKEN_EXPIRATION`| 1.0.0 |Duration|`Expiry duration for invite tokens.`|`24h0m0s`|
+|`OCM_OCM_INVITE_MANAGER_TIMEOUT`| 1.0.0 |Duration|`Timeout specifies a time limit for requests made to OCM endpoints.`|`30s`|
+|`OCM_OCM_INVITE_MANAGER_INSECURE`| 1.0.0 |bool|`Disable TLS certificate validation for the OCM connections. Do not set this in production environments.`|`false`|
+|`SHARING_OCM_PROVIDER_AUTHORIZER_DRIVER`| 1.0.0 |string|`Driver to be used to persist ocm invites. Supported value is only 'json'.`|`json`|
+|`OCM_OCM_PROVIDER_AUTHORIZER_PROVIDERS_FILE`| 1.0.0 |string|`Path to the JSON file where ocm invite data will be stored. Defaults to $OC_CONFIG_DIR/ocmproviders.json.`|`/etc/opencloud/ocmproviders.json`|
+|`OCM_OCM_SHARE_PROVIDER_DRIVER`| 1.0.0 |string|`Driver to be used for the OCM share provider. Supported value is only 'json'.`|`json`|
+|`OCM_OCM_SHAREPROVIDER_JSON_FILE`| 1.0.0 |string|`Path to the JSON file where OCM share data will be stored. If not defined, the root directory derives from $OC_BASE_DATA_PATH/storage.`|`/var/lib/opencloud/storage/ocm/ocmshares.json`|
+|`OCM_OCM_SHARE_PROVIDER_INSECURE`| 1.0.0 |bool|`Disable TLS certificate validation for the OCM connections. Do not set this in production environments.`|`false`|
+|`OCM_WEBAPP_TEMPLATE`| 1.0.0 |string|`Template for the webapp url.`|``|
+|`OCM_OCM_CORE_DRIVER`| 1.0.0 |string|`Driver to be used for the OCM core. Supported value is only 'json'.`|`json`|
+|`OCM_OCM_CORE_JSON_FILE`| 1.0.0 |string|`Path to the JSON file where OCM share data will be stored. If not defined, the root directory derives from $OC_BASE_DATA_PATH/storage.`|`/var/lib/opencloud/storage/ocm/ocmshares.json`|
+|`OCM_OCM_STORAGE_PROVIDER_INSECURE`| 1.0.0 |bool|`Disable TLS certificate validation for the OCM connections. Do not set this in production environments.`|`false`|
+|`OCM_OCM_STORAGE_PROVIDER_STORAGE_ROOT`| 1.0.0 |string|`Directory where the ocm storage provider persists its data like tus upload info files.`|`/var/lib/opencloud/storage/ocm`|
+|`OCM_OCM_STORAGE_DATA_SERVER_URL`| 1.0.0 |string|`URL of the data server, needs to be reachable by the data gateway provided by the frontend service or the user if directly exposed.`|`http://localhost:9280/data`|
diff --git a/versioned_docs/version-7.x/_static/env-vars/ocm_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/ocm_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/ocm_readme.md b/versioned_docs/version-7.x/_static/env-vars/ocm_readme.md
new file mode 100755
index 000000000..f98eb9bd8
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/ocm_readme.md
@@ -0,0 +1,144 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The `ocm` service provides federated sharing functionality based on the [sciencemesh](https://sciencemesh.io/) and [ocm](https://github.com/cs3org/OCM-API) HTTP APIs. Internally the `ocm` service consists of the following services and endpoints:
+
+External HTTP APIs:
+* sciencemesh: serves the API for the invitation workflow
+* ocmd: serves the API for managing federated shares
+
+Internal GRPC APIs:
+* ocmproviderauthorizer: manages the list of trusted providers and verifies requests
+* ocminvitemanager: manages the list and state of invite tokens
+* ocmshareprovider: manages ocm shares on the sharer
+* ocmcore: used for creating federated shares on the receiver side
+* authprovider: authenticates webdav requests using the ocm share tokens
+
+
+## Table of Contents
+
+* [Enable OCM](#enable-ocm)
+* [Trust Between Instances](#trust-between-instances)
+* [Invitation Workflow](#invitation-workflow)
+* [Creating Shares](#creating-shares)
+
+## Enable OCM
+
+To enable OpenCloudMesh, you have to set the following environment variable.
+
+```console
+OC_ENABLE_OCM=true
+```
+
+## Trust Between Instances
+
+The `ocm` services implements an invitation workflow which needs to be followed before creating federated shares. Invitations are limited to trusted instances, however.
+
+The list of trusted instances is managed by the `ocmproviderauthorizer` service. The only supported backend currently is `json` which stores the list in a json file on disk. Note that the `ocmproviders.json` file, which holds that configuration, is expected to be located in the root of the OpenCloud config directory if not otherwise defined. See the `OCM_OCM_PROVIDER_AUTHORIZER_PROVIDERS_FILE` envvar for more details.
+
+When all instances of a federation should trust each other, an `ocmproviders.json` file like this can be used for all instances:
+```json
+[
+    {
+        "name": "OpenCloud Test 1",
+        "full_name": "OpenCloud Test provider 1",
+        "organization": "OpenCloud One",
+        "domain": "cloud1.opencloud.test",
+        "homepage": "https://cloud1.opencloud.test",
+        "description": "First OpenCloud Example cloud storage",
+        "services": [
+            {
+                "endpoint": {
+                    "type": {
+                        "name": "OCM",
+                        "description": "cloud1.opencloud.test Open Cloud Mesh API"
+                    },
+                    "name": "cloud1.opencloud.test - OCM API",
+                    "path": "https://cloud1.opencloud.test/ocm/",
+                    "is_monitored": true
+                },
+                "api_version": "0.0.1",
+                "host": "http://cloud1.opencloud.test"
+            },
+            {
+                "endpoint": {
+                    "type": {
+                        "name": "Webdav",
+                        "description": "cloud1.opencloud.test Webdav API"
+                    },
+                    "name": "cloud1.opencloud.test Example - Webdav API",
+                    "path": "https://cloud1.opencloud.test/dav/",
+                    "is_monitored": true
+                },
+                "api_version": "0.0.1",
+                "host": "https://cloud1.opencloud.test/"
+            }
+        ]
+    },
+    {
+        "name": "OpenCloud Test 2",
+        "full_name": "OpenCloud Test provider 2",
+        "organization": "OpenCloud Two",
+        "domain": "cloud2.opencloud.test",
+        "homepage": "https://cloud2.opencloud.test",
+        "description": "Second OpenCloud Example cloud storage",
+        "services": [
+            {
+                "endpoint": {
+                    "type": {
+                        "name": "OCM",
+                        "description": "cloud2.opencloud.test Open Cloud Mesh API"
+                    },
+                    "name": "cloud2.opencloud.test - OCM API",
+                    "path": "https://cloud2.opencloud.test/ocm/",
+                    "is_monitored": true
+                },
+                "api_version": "0.0.1",
+                "host": "http://cloud2.opencloud.test"
+            },
+            {
+                "endpoint": {
+                    "type": {
+                        "name": "Webdav",
+                        "description": "cloud2.opencloud.test Webdav API"
+                    },
+                    "name": "cloud2.opencloud.test Example - Webdav API",
+                    "path": "https://cloud2.opencloud.test/dav/",
+                    "is_monitored": true
+                },
+                "api_version": "0.0.1",
+                "host": "https://cloud2.opencloud.test/"
+            }
+        ]
+    }
+]
+```
+
+:::info
+Note: the `domain` must not contain the protocol as it has to match the [GOCDB site object domain](https://developer.sciencemesh.io/docs/technical-documentation/central-database/#site-object).
+:::
+
+The above federation consists of two instances: `cloud1.opencloud.test` and `cloud2.opencloud.test` that can use the Invitation workflow described below to generate, send and accept invitations.
+
+## Invitation Workflow
+
+Before sharing a resource with a remote user this user has to be invited by the sharer.
+
+In order to do so a POST request is sent to the `generate-invite` endpoint of the sciencemesh API. The generated token is passed on to the receiver, who will then use the `accept-invite` endpoint to accept the invitation. As a result remote users will be added to the `ocminvitemanager` on both sides. See [invitation flow](invitation-flow) for the according sequence diagram.
+
+The data backend of the `ocminvitemanager` is configurable. The only supported backend currently is `json` which stores the data in a json file on disk.
+
+## Creating Shares
+
+:::info
+The below info is outdated as we allow creating federated shares using the graph API. Clients can now discover the available sharing roles and invite federated users using the graph API.
+:::
+
+OCM Shares are currently created using the ocs API, just like regular shares. The difference is the share type, which is 6 (ShareTypeFederatedCloudShare) in this case, and a few additional parameters required for identifying the remote user.
+
+See [Create share flow](create-share-flow) for the according sequence diagram.
+
+The data backends of the `ocmshareprovider` and `ocmcore` services are configurable. The only supported backend currently is `json` which stores the data in a json file on disk.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/ocs.yaml b/versioned_docs/version-7.x/_static/env-vars/ocs.yaml
new file mode 100644
index 000000000..7bcc86906
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/ocs.yaml
@@ -0,0 +1,48 @@
+# Autogenerated
+# Filename: ocs.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9114
+  token: ""
+  pprof: false
+  zpages: false
+http:
+  addr: 127.0.0.1:9110
+  root: /ocs
+  cors:
+    allow_origins:
+    - '*'
+    allow_methods:
+    - GET
+    - POST
+    - PUT
+    - PATCH
+    - DELETE
+    - OPTIONS
+    allow_headers:
+    - Authorization
+    - Origin
+    - Content-Type
+    - Accept
+    - X-Requested-With
+    - X-Request-Id
+    - Cache-Control
+    allow_credentials: true
+  tls:
+    enabled: false
+    cert: ""
+    key: ""
+grpc_client_tls: null
+signing_keys:
+  store: nats-js-kv
+  addresses:
+  - 127.0.0.1:9233
+  ttl: 24h0m0s
+  username: ""
+  password: ""
+  enable_tls: false
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+token_manager:
+  jwt_secret: ""
diff --git a/versioned_docs/version-7.x/_static/env-vars/ocs_configvars.md b/versioned_docs/version-7.x/_static/env-vars/ocs_configvars.md
new file mode 100644
index 000000000..b7f82885a
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/ocs_configvars.md
@@ -0,0 +1,27 @@
+## Environment variables for the **ocs** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`OCS_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`OCS_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9114`|
+|`OCS_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`OCS_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`OCS_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`OCS_HTTP_ADDR`| 1.0.0 |string|`The bind address of the HTTP service.`|`127.0.0.1:9110`|
+|`OCS_HTTP_ROOT`| 1.0.0 |string|`Subdirectory that serves as the root for this HTTP service.`|`/ocs`|
+|`OC_CORS_ALLOW_ORIGINS`<br/>`OCS_CORS_ALLOW_ORIGINS`| 1.0.0 |[]string|`A list of allowed CORS origins. See following chapter for more details: *Access-Control-Allow-Origin* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin. See the Environment Variable Types description for more details.`|`[*]`|
+|`OC_CORS_ALLOW_METHODS`<br/>`OCS_CORS_ALLOW_METHODS`| 1.0.0 |[]string|`A list of allowed CORS methods. See following chapter for more details: *Access-Control-Request-Method* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Method. See the Environment Variable Types description for more details.`|`[GET POST PUT PATCH DELETE OPTIONS]`|
+|`OC_CORS_ALLOW_HEADERS`<br/>`OCS_CORS_ALLOW_HEADERS`| 1.0.0 |[]string|`A list of allowed CORS headers. See following chapter for more details: *Access-Control-Request-Headers* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Headers. See the Environment Variable Types description for more details.`|`[Authorization Origin Content-Type Accept X-Requested-With X-Request-Id Cache-Control]`|
+|`OC_CORS_ALLOW_CREDENTIALS`<br/>`OCS_CORS_ALLOW_CREDENTIALS`| 1.0.0 |bool|`Allow credentials for CORS.See following chapter for more details: *Access-Control-Allow-Credentials* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Credentials.`|`true`|
+|`OC_HTTP_TLS_ENABLED`| 1.0.0 |bool|`Activates TLS for the http based services using the server certifcate and key configured via OC_HTTP_TLS_CERTIFICATE and OC_HTTP_TLS_KEY. If OC_HTTP_TLS_CERTIFICATE is not set a temporary server certificate is generated - to be used with PROXY_INSECURE_BACKEND=true.`|`false`|
+|`OC_HTTP_TLS_CERTIFICATE`| 1.0.0 |string|`Path/File name of the TLS server certificate (in PEM format) for the http services.`|``|
+|`OC_HTTP_TLS_KEY`| 1.0.0 |string|`Path/File name for the TLS certificate key (in PEM format) for the server certificate to use for the http services.`|``|
+|`OC_CACHE_STORE`<br/>`OCS_PRESIGNEDURL_SIGNING_KEYS_STORE`| 1.0.0 |string|`The type of the signing key store. Supported values are: 'redis-sentinel' and 'nats-js-kv'. See the text description for details.`|`nats-js-kv`|
+|`OC_CACHE_STORE_NODES`<br/>`OCS_PRESIGNEDURL_SIGNING_KEYS_STORE_NODES`| 1.0.0 |[]string|`A list of nodes to access the configured store. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details.`|`[127.0.0.1:9233]`|
+|`OC_CACHE_TTL`<br/>`OCS_PRESIGNEDURL_SIGNING_KEYS_STORE_TTL`| 1.0.0 |Duration|`Default time to live for signing keys. See the Environment Variable Types description for more details.`|`24h0m0s`|
+|`OC_CACHE_AUTH_USERNAME`<br/>`OCS_PRESIGNEDURL_SIGNING_KEYS_STORE_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_CACHE_AUTH_PASSWORD`<br/>`OCS_PRESIGNEDURL_SIGNING_KEYS_STORE_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_CACHE_ENABLE_TLS`<br/>`OCS_PRESIGNEDURL_SIGNING_KEYS_STORE_ENABLE_TLS`| next |bool|`Enable TLS for the connection to file metadata cache.`|`false`|
+|`OC_INSECURE`<br/>`OC_CACHE_TLS_INSECURE`<br/>`OCS_PRESIGNEDURL_SIGNING_KEYS_STORE_TLS_INSECURE`| next |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_CACHE_TLS_ROOT_CA_CERTIFICATE`<br/>`OCS_PRESIGNEDURL_SIGNING_KEYS_STORE_TLS_ROOT_CA_CERTIFICATE`| next |string|`The root CA certificate used to validate the server's TLS certificate. If provided OCS_PRESIGNEDURL_SIGNING_KEYS_STORE_TLS_INSECURE will be seen as false.`|``|
+|`OC_JWT_SECRET`<br/>`OCS_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
diff --git a/versioned_docs/version-7.x/_static/env-vars/ocs_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/ocs_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/ocs_readme.md b/versioned_docs/version-7.x/_static/env-vars/ocs_readme.md
new file mode 100755
index 000000000..48a0f02ce
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/ocs_readme.md
@@ -0,0 +1,34 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The `ocs` service (open collaboration services) serves one purpose: it has an endpoint for signing keys which the web frontend accesses when uploading data.
+
+
+## Table of Contents
+
+* [Signing-Keys Endpoint](#signingkeys-endpoint)
+* [Signing-Keys Store](#signingkeys-store)
+
+## Signing-Keys Endpoint
+
+The `ocs` service contains an endpoint `/cloud/user/signing-key` on which a user can GET a signing key. Note, this functionality might be deprecated or moved in the future.
+
+## Signing-Keys Store
+
+To authenticate presigned URLs the proxy service needs to read the signing keys from a store that is populated by the ocs service.
+Possible stores that can be configured via `OCS_PRESIGNEDURL_SIGNING_KEYS_STORE` are:
+  -   `nats-js-kv`: Stores data using key-value-store feature of [nats jetstream](https://docs.nats.io/nats-concepts/jetstream/key-value-store)
+  -   `redis-sentinel`: Stores data in a configured Redis Sentinel cluster.
+  -   `opencloudstoreservice`:  Stores data in the legacy OpenCloud store service. Requires setting `OCS_PRESIGNEDURL_SIGNING_KEYS_STORE_NODES` to `eu.opencloud.api.store`.
+
+The `memory` store cannot be used as it does not share the memory from the ocs service signing key memory store, even in a single process.
+
+Make sure to configure the same store in the proxy service.
+
+Store specific notes:
+  -   When using `redis-sentinel`, the Redis master to use is configured via e.g. `OCS_PRESIGNEDURL_SIGNING_KEYS_STORE_NODES` in the form of `<sentinel-host>:<sentinel-port>/<redis-master>` like `10.10.0.200:26379/mymaster`.
+  -   When using `nats-js-kv` it is recommended to set `PROXY_PRESIGNEDURL_SIGNING_KEYS_STORE_NODES` to the same value as `OCS_PRESIGNEDURL_SIGNING_KEYS_STORE_NODES`. That way the proxy uses the same nats instance as the ocs service.
+  -   When using `opencloudstoreservice` the `OCS_PRESIGNEDURL_SIGNING_KEYS_STORE_NODES` must be set to the service name `eu.opencloud.api.store`. It does not support TTL and stores the presigning keys indefinitely. Also, the store service needs to be started.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/policies.yaml b/versioned_docs/version-7.x/_static/env-vars/policies.yaml
new file mode 100644
index 000000000..3f29546c6
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/policies.yaml
@@ -0,0 +1,27 @@
+# Autogenerated
+# Filename: policies.yaml
+
+grpc:
+  addr: 127.0.0.1:9125
+  tls: null
+debug:
+  addr: 127.0.0.1:9129
+  token: ""
+  pprof: false
+  zpages: false
+events:
+  endpoint: 127.0.0.1:9233
+  cluster: opencloud-cluster
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+  enable_tls: false
+  username: ""
+  password: ""
+grpc_client_tls: null
+loglevel: error
+engine:
+  timeout: 10s
+  policies: []
+  mimes: ""
+postprocessing:
+  query: ""
diff --git a/versioned_docs/version-7.x/_static/env-vars/policies_configvars.md b/versioned_docs/version-7.x/_static/env-vars/policies_configvars.md
new file mode 100644
index 000000000..07fa62d8b
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/policies_configvars.md
@@ -0,0 +1,20 @@
+## Environment variables for the **policies** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`POLICIES_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9125`|
+|`POLICIES_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9129`|
+|`POLICIES_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`POLICIES_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`POLICIES_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`OC_EVENTS_ENDPOINT`<br/>`POLICIES_EVENTS_ENDPOINT`| 1.0.0 |string|`The address of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture.`|`127.0.0.1:9233`|
+|`OC_EVENTS_CLUSTER`<br/>`POLICIES_EVENTS_CLUSTER`| 1.0.0 |string|`The clusterID of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture. Mandatory when using NATS as event system.`|`opencloud-cluster`|
+|`OC_INSECURE`<br/>`OC_EVENTS_TLS_INSECURE`<br/>`POLICIES_EVENTS_TLS_INSECURE`| 1.0.0 |bool|`Whether the server should skip the client certificate verification during the TLS handshake.`|`false`|
+|`OC_EVENTS_TLS_ROOT_CA_CERTIFICATE`<br/>`POLICIES_EVENTS_TLS_ROOT_CA_CERTIFICATE`| 1.0.0 |string|`The root CA certificate used to validate the server's TLS certificate. If provided POLICIES_EVENTS_TLS_INSECURE will be seen as false.`|``|
+|`OC_EVENTS_ENABLE_TLS`<br/>`POLICIES_EVENTS_ENABLE_TLS`| 1.0.0 |bool|`Enable TLS for the connection to the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|`false`|
+|`OC_EVENTS_AUTH_USERNAME`<br/>`POLICIES_EVENTS_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_EVENTS_AUTH_PASSWORD`<br/>`POLICIES_EVENTS_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_LOG_LEVEL`<br/>`POLICIES_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`POLICIES_ENGINE_TIMEOUT`| 1.0.0 |Duration|`Sets the timeout the rego expression evaluation can take. Rules default to deny if the timeout was reached. See the Environment Variable Types description for more details.`|`10s`|
+|`POLICIES_ENGINE_MIMES`| 1.0.0 |string|`Sets the mimes file path which maps mimetypes to associated file extensions. See the text description for details.`|``|
+|`POLICIES_POSTPROCESSING_QUERY`| 1.0.0 |string|`Defines the 'Complete Rules' variable defined in the rego rule set this step uses for its evaluation. Defaults to deny if the variable was not found.`|``|
diff --git a/versioned_docs/version-7.x/_static/env-vars/policies_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/policies_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/policies_readme.md b/versioned_docs/version-7.x/_static/env-vars/policies_readme.md
new file mode 100755
index 000000000..65da04385
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/policies_readme.md
@@ -0,0 +1,187 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The policies service provides a new gRPC API which can be used to check whether a requested operation is allowed or not. To do so, Open Policy Agent (OPA) is used to define the set of rules of what is permitted and what is not.
+
+Policies are written in the [rego query language](https://www.openpolicyagent.org/docs/latest/policy-language/). The location of the rego files can be configured via yaml, a configuration via environment variables is not possible.
+
+
+## Table of Contents
+
+* [General Information](#general-information)
+* [Modules](#modules)
+  * [gRPC API](#grpc-api)
+  * [Proxy Middleware](#proxy-middleware)
+  * [Event Service (Postprocessing)](#event-service-postprocessing)
+* [Defining Policies to Evaluate](#defining-policies-to-evaluate)
+* [Setting the Query Configuration](#setting-the-query-configuration)
+  * [Proxy](#proxy)
+  * [Postprocessing](#postprocessing)
+* [Rego Key Match](#rego-key-match)
+* [Extend Mimetype File Extension Mapping](#extend-mimetype-file-extension-mapping)
+* [Example Policies](#example-policies)
+
+## General Information
+
+The policies service consists of the following modules:
+
+*   Proxy authorization (middleware)
+*   Event authorization (async post-processing)
+*   gRPC API (can be used by other services)
+
+To configure the policies service, three environment variables need to be defined:
+
+*   `POLICIES_ENGINE_TIMEOUT`
+*   `POLICIES_POSTPROCESSING_QUERY`
+*   `PROXY_POLICIES_QUERY`
+
+Note that each query setting defines the [Complete Rules](https://www.openpolicyagent.org/docs/latest/#complete-rules) variable defined in the rego rule set the corresponding step uses for the evaluation. If the variable is mistyped or not found, the evaluation defaults to deny. Individual query definitions can be defined for each module.
+
+To activate the policies service for a module, it must be started with a yaml configuration that points to one or more rego files. Note that if the service is scaled horizontally, each instance should have access to the same rego files to avoid unpredictable results. If a file path has been configured but the file is not present or accessible, the evaluation defaults to deny.
+
+When using async post-processing which is done via the postprocessing service, the value `policies` must be added to the `POSTPROCESSING_STEPS` configuration in postprocessing service in the order where the evaluation should take place.
+
+variable defined in the Rego rule set the corresponding step uses for the evaluation. If the variable is mistyped or not found, the evaluation defaults to deny. Individual query definitions can be defined for each module.
+
+To activate the policies service for a module, it must be started with a yaml configuration that points to at least one Rego file that contains the complete rule variable to be queried. Note that if the service is scaled horizontally, each instance should have access to the same Rego files to avoid unpredictable results. If a file path has been configured but the file it is not present or accessible, the evaluation defaults to deny.
+
+When using async post-processing via the postprocessing service, the value `policies` must be added to the `POSTPROCESSING_STEPS` configuration in the order in which the evaluation should take place. Example: First check if a file contains questionable content via policies. If it looks okay, continue to check for viruses.
+
+For configuration examples, the [Example Policies](#example-policies) from below are used.
+
+## Modules
+
+### gRPC API
+
+The gRPC API can be used by any other internal service. It can also be used for example by third parties to find out if an action is allowed or not. This layer is already used by the proxy middleware. There is no configuration necessary, because the query setting (complete rule variable) must be part of the request.
+
+### Proxy Middleware
+
+The proxy service already includes a middleware which uses the internal [gRPC API](#grpc-api) to evaluate the policies. Since the proxy is in heavy use and every HTTP request is processed here, only simple and quick decisions should be evaluated. More complex queries such as file content evaluation are _strongly_ discouraged.
+
+If the evaluation in the proxy results in a "denied" outcome, the response will return a `403 Permission Denied` with the following response body
+
+```json
+{
+    "error":
+    {
+        "code": "deniedByPolicy",
+        "message": "Operation denied due to security policies",
+        "innererror":
+        {
+            "date": "2023-09-19T13:22:20Z",
+            "filename": "File",
+            "method": "POST",
+            "path": "/dav/spaces/some-space-id/Folder/",
+            "request-id": "9CFCE925-F9D9-4F26-AB3B-2C1C40A9CD0C"
+        }
+    }
+}
+```
+
+### Event Service (Postprocessing)
+
+This layer is event-based and part of the postprocessing service. Since processing at this point is asynchronous, the operations can also take longer and be more expensive, like evaluating the contents of a file.
+
+## Defining Policies to Evaluate
+
+Each module can have as many policy files as needed for evaluation. Files can also include other files if necessary. To use policies, they have to be saved to a location that is accessible to the policies service. As a good starting point, take the config directory and use a subdirectory collecting all the `.rego` files, though any other directory can be defined. The config directory is already accessible by all services and usually is included in a xref:maintenance/b-r/backup.adoc[backup] plan.
+
+If this is done, it's required to configure the policies service to use these files:
+
+NOTE: It is important that *all* necessary files are added to the list of files the policies service uses.
+
+```yaml
+policies:
+  engine:
+    policies:
+      - your_path_to_policies/proxy.rego
+      - your_path_to_policies/postprocessing.rego
+      - your_path_to_policies/util.rego
+```
+
+Once the references to policy files are configured correctly, the `_QUERY`  configuration needs to be defined for the proxy middleware and for the events service.
+
+## Setting the Query Configuration
+
+To define a value for the query evaluation, the following scheme is necessary:
+
+`data.<package-name>.<complete-rule-variable-name>`
+
+* The keyword `data` is mandatory and must be present.
+* The `package-name` is defined in one .rego file like `package postprocessing`. It is not related to the filename. For more details, see the [packages](https://www.openpolicyagent.org/docs/latest/policy-language/#packages) documentation.
+* The `complete-rule-variable-name` is the variable providing the result of the evaluation.
+* Exact one of the defined files, which is responsible for returning the evaluation result, must contain the combination of `<package-name>` and `<complete-rule-variable-name>`.
+
+### Proxy
+
+Note that this setting has to be part of the proxy configuration.
+
+```yaml
+proxy:
+  policies_middleware:
+    query: data.proxy.granted
+```
+
+The same can be achieved by setting the following environment variable:
+
+```shell
+export PROXY_POLICIES_QUERY=data.proxy.granted
+```
+
+### Postprocessing
+
+```yaml
+policies:
+  postprocessing:
+    query: data.postprocessing.granted
+```
+
+The same can be achieved by setting the following environment variable:
+
+```shell
+export POLICIES_POSTPROCESSING_QUERY=data.postprocessing.granted
+```
+
+As soon as that query is configured, the postprocessing service must be informed to use the policies step by setting the environment variable:
+
+```shell
+export POSTPROCESSING_STEPS=policies
+```
+
+Note that additional steps can be configured and their position in the list defines the order of processing. For details see the postprocessing service documentation.
+
+## Rego Key Match
+
+To identify available keys for OPA, you need to look at [engine.go](https://github.com/opencloud-eu/opencloud/blob/main/services/policies/pkg/engine/engine.go) and the [policies.swagger.json](https://github.com/opencloud-eu/opencloud/blob/master/protogen/gen/opencloud/services/policies/v0/policies.swagger.json) file. Note that which keys are available depends on from which module it is used.
+
+## Extend Mimetype File Extension Mapping
+
+In the extended set of the rego query language, it is possible to get a list of associated file extensions based on a mimetype, for example `opencloud.mimetype.extensions("application/pdf")`.
+
+The list of mappings is restricted by default and is provided by the host system OpenCloud is installed on.
+
+In order to extend this list, OpenCloud must be provided with the path to a custom `mime.types` file that maps mimetypes to extensions.
+The location for the file must be accessible by all instances of the policy service. As a rule of thumb, use the directory where the OpenCloud configuration files are stored.
+Note that existing mappings from the host are extended by the definitions from the mime types file, but not replaced.
+
+The path to that file can be provided via a yaml configuration or an environment variable. Note to replace the `OC_CONFIG_DIR` string by an existing path.
+
+```shell
+export POLICIES_ENGINE_MIMES=OC_CONFIG_DIR/mime.types
+```
+
+```yaml
+policies:
+  engine:
+    mimes: OC_CONFIG_DIR/mime.types
+```
+
+A good example of how such a file should be formatted can be found in the [Apache svn repository](https://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/conf/mime.types).
+
+## Example Policies
+
+The policies service contains a set of preconfigured example policies. See the [devtools policie](https://github.com/opencloud-eu/opencloud/tree/main/devtools/deployments/service_policies/policies/) directory for details. The contained policies disallow OpenCloud to create certain file types, both via the proxy middleware and the events service via postprocessing.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/postprocessing.yaml b/versioned_docs/version-7.x/_static/env-vars/postprocessing.yaml
new file mode 100644
index 000000000..74de6abe3
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/postprocessing.yaml
@@ -0,0 +1,37 @@
+# Autogenerated
+# Filename: postprocessing.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9255
+  token: ""
+  pprof: false
+  zpages: false
+store:
+  store: nats-js-kv
+  nodes:
+  - 127.0.0.1:9233
+  database: postprocessing
+  table: ""
+  ttl: 168h0m0s
+  username: ""
+  password: ""
+  enable_tls: false
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+postprocessing:
+  events:
+    endpoint: 127.0.0.1:9233
+    cluster: opencloud-cluster
+    tls_insecure: false
+    tls_root_ca_certificate: ""
+    enable_tls: false
+    username: ""
+    password: ""
+    max_ack_pending: 10000
+    ack_wait: 1m0s
+  workers: 3
+  steps: []
+  delayprocessing: 0s
+  retry_backoff_duration: 5s
+  max_retries: 14
diff --git a/versioned_docs/version-7.x/_static/env-vars/postprocessing_configvars.md b/versioned_docs/version-7.x/_static/env-vars/postprocessing_configvars.md
new file mode 100644
index 000000000..0a30165ff
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/postprocessing_configvars.md
@@ -0,0 +1,33 @@
+## Environment variables for the **postprocessing** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`POSTPROCESSING_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`POSTPROCESSING_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9255`|
+|`POSTPROCESSING_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`POSTPROCESSING_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`POSTPROCESSING_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`OC_PERSISTENT_STORE`<br/>`POSTPROCESSING_STORE`| 1.0.0 |string|`The type of the store. Supported values are: 'memory', 'redis-sentinel', 'nats-js-kv', 'noop'. See the text description for details.`|`nats-js-kv`|
+|`OC_PERSISTENT_STORE_NODES`<br/>`POSTPROCESSING_STORE_NODES`| 1.0.0 |[]string|`A list of nodes to access the configured store. This has no effect when 'memory' store is configured. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details.`|`[127.0.0.1:9233]`|
+|`POSTPROCESSING_STORE_DATABASE`| 1.0.0 |string|`The database name the configured store should use.`|`postprocessing`|
+|`POSTPROCESSING_STORE_TABLE`| 1.0.0 |string|`The database table the store should use.`|``|
+|`OC_PERSISTENT_STORE_TTL`<br/>`POSTPROCESSING_STORE_TTL`| 1.0.0 |Duration|`Time to live for events in the store. See the Environment Variable Types description for more details.`|`168h0m0s`|
+|`OC_PERSISTENT_STORE_AUTH_USERNAME`<br/>`POSTPROCESSING_STORE_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_PERSISTENT_STORE_AUTH_PASSWORD`<br/>`POSTPROCESSING_STORE_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_PERSISTENT_STORE_ENABLE_TLS`<br/>`POSTPROCESSING_STORE_ENABLE_TLS`| next |bool|`Enable TLS for the connection to the store. Only applies when store type 'nats-js-kv' is configured.`|`false`|
+|`OC_INSECURE`<br/>`OC_PERSISTENT_STORE_TLS_INSECURE`<br/>`POSTPROCESSING_STORE_TLS_INSECURE`| next |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_PERSISTENT_STORE_TLS_ROOT_CA_CERTIFICATE`<br/>`POSTPROCESSING_STORE_TLS_ROOT_CA_CERTIFICATE`| next |string|`The root CA certificate used to validate the server's TLS certificate. If provided POSTPROCESSING_STORE_TLS_INSECURE will be seen as false.`|``|
+|`OC_EVENTS_ENDPOINT`<br/>`POSTPROCESSING_EVENTS_ENDPOINT`| 1.0.0 |string|`The address of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture.`|`127.0.0.1:9233`|
+|`OC_EVENTS_CLUSTER`<br/>`POSTPROCESSING_EVENTS_CLUSTER`| 1.0.0 |string|`The clusterID of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture. Mandatory when using NATS as event system.`|`opencloud-cluster`|
+|`OC_INSECURE`<br/>`OC_EVENTS_TLS_INSECURE`<br/>`POSTPROCESSING_EVENTS_TLS_INSECURE`| 1.0.0 |bool|`Whether the OpenCloud server should skip the client certificate verification during the TLS handshake.`|`false`|
+|`OC_EVENTS_TLS_ROOT_CA_CERTIFICATE`<br/>`POSTPROCESSING_EVENTS_TLS_ROOT_CA_CERTIFICATE`| 1.0.0 |string|`The root CA certificate used to validate the server's TLS certificate. If provided POSTPROCESSING_EVENTS_TLS_INSECURE will be seen as false.`|``|
+|`OC_EVENTS_ENABLE_TLS`<br/>`POSTPROCESSING_EVENTS_ENABLE_TLS`| 1.0.0 |bool|`Enable TLS for the connection to the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|`false`|
+|`OC_EVENTS_AUTH_USERNAME`<br/>`POSTPROCESSING_EVENTS_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_EVENTS_AUTH_PASSWORD`<br/>`POSTPROCESSING_EVENTS_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`SEARCH_EVENTS_MAX_ACK_PENDING`| 4.0.0 |int|`The maximum number of unacknowledged messages. This is used to limit the number of messages that can be in flight at the same time.`|`10000`|
+|`SEARCH_EVENTS_ACK_WAIT`| 4.0.0 |Duration|`The time to wait for an ack before the message is redelivered. This is used to ensure that messages are not lost if the consumer crashes.`|`1m0s`|
+|`POSTPROCESSING_WORKERS`| 1.0.0 |int|`The number of concurrent go routines that fetch events from the event queue.`|`3`|
+|`POSTPROCESSING_STEPS`| 1.0.0 |[]string|`A list of postprocessing steps processed in order of their appearance. Currently supported values by the system are: 'virusscan', 'policies' and 'delay'. Custom steps are allowed. See the documentation for instructions. See the Environment Variable Types description for more details.`|`[]`|
+|`POSTPROCESSING_DELAY`| 1.0.0 |Duration|`After uploading a file but before making it available for download, a delay step can be added. Intended for developing purposes only. If a duration is set but the keyword 'delay' is not explicitely added to 'POSTPROCESSING_STEPS', the delay step will be processed as last step. In such a case, a log entry will be written on service startup to remind the admin about that situation. See the Environment Variable Types description for more details.`|`0s`|
+|`POSTPROCESSING_RETRY_BACKOFF_DURATION`| 1.0.0 |Duration|`The base for the exponential backoff duration before retrying a failed postprocessing step. See the Environment Variable Types description for more details.`|`5s`|
+|`POSTPROCESSING_MAX_RETRIES`| 1.0.0 |int|`The maximum number of retries for a failed postprocessing step.`|`14`|
diff --git a/versioned_docs/version-7.x/_static/env-vars/postprocessing_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/postprocessing_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/postprocessing_readme.md b/versioned_docs/version-7.x/_static/env-vars/postprocessing_readme.md
new file mode 100755
index 000000000..7ef4047a4
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/postprocessing_readme.md
@@ -0,0 +1,156 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The `postprocessing` service handles the coordination of asynchronous postprocessing steps.
+
+
+## Table of Contents
+
+* [General Prerequisites](#general-prerequisites)
+* [Postprocessing Functionality](#postprocessing-functionality)
+* [Storing Postprocessing Data](#storing-postprocessing-data)
+* [Additional Prerequisites for the Postprocessing Service](#additional-prerequisites-for-the-postprocessing-service)
+* [Postprocessing Steps](#postprocessing-steps)
+  * [Virus Scanning](#virus-scanning)
+  * [Delay](#delay)
+  * [Custom Postprocessing Steps](#custom-postprocessing-steps)
+    * [Prerequisites](#prerequisites)
+    * [Workflow](#workflow)
+* [CLI Commands](#cli-commands)
+  * [Resume Postprocessing](#resume-postprocessing)
+* [Metrics](#metrics)
+
+## General Prerequisites
+
+To use the postprocessing service, an event system needs to be configured for all services. By default, `OpenCloud` ships with a preconfigured `nats` service.
+
+## Postprocessing Functionality
+
+The storageprovider service (`storage-users`) can be configured to initiate asynchronous postprocessing by setting the `OC_ASYNC_UPLOADS` environment variable to `true`. If this is the case, postprocessing will get initiated *after* uploading a file and all bytes have been received.
+
+The `postprocessing` service will then coordinate configured postprocessing steps like scanning the file for viruses. During postprocessing, the file will be in a `processing state` where only a limited set of actions are available. Note that this processing state excludes file accessibility by users.
+
+When all postprocessing steps have completed successfully, the file will be made accessible for users.
+
+## Storing Postprocessing Data
+
+The `postprocessing` service needs to store some metadata about uploads to be able to orchestrate post-processing. When running in single binary mode, the default in-memory implementation will be just fine. In distributed deployments it is recommended to use a persistent store, see below for more details.
+
+The `postprocessing` service stores its metadata via the configured store in `POSTPROCESSING_STORE`. Possible stores are:
+  -   `memory`: Basic in-memory store and the default.
+  -   `redis-sentinel`: Stores data in a configured Redis Sentinel cluster.
+  -   `nats-js-kv`: Stores data using key-value-store feature of [nats jetstream](https://docs.nats.io/nats-concepts/jetstream/key-value-store)
+  -   `noop`: Stores nothing. Useful for testing. Not recommended in production environments.
+
+Other store types may work but are not supported currently.
+
+Note: The service can only be scaled if not using `memory` store and the stores are configured identically over all instances!
+
+Note that if you have used one of the deprecated stores, you should reconfigure to one of the supported ones as the deprecated stores will be removed in a later version.
+
+Store specific notes:
+  -   When using `redis-sentinel`, the Redis master to use is configured via e.g. `OC_CACHE_STORE_NODES` in the form of `<sentinel-host>:<sentinel-port>/<redis-master>` like `10.10.0.200:26379/mymaster`.
+  -   When using `nats-js-kv` it is recommended to set `OC_CACHE_STORE_NODES` to the same value as `OC_EVENTS_ENDPOINT`. That way the cache uses the same nats instance as the event bus.
+  -   When using the `nats-js-kv` store, it is possible to set `OC_CACHE_DISABLE_PERSISTENCE` to instruct nats to not persist cache data on disc.
+
+## Additional Prerequisites for the Postprocessing Service
+
+When postprocessing has been enabled, configuring any postprocessing step will require the requested services to be enabled and pre-configured. For example, to use the `virusscan` step, one needs to have an enabled and configured `antivirus` service.
+
+## Postprocessing Steps
+
+The postporcessing service is individually configurable. This is achieved by allowing a list of postprocessing steps that are processed in order of their appearance in the `POSTPROCESSING_STEPS` envvar. This envvar expects a comma separated list of steps that will be executed. Currently known steps to the system are `virusscan` and `delay`. Custom steps can be added but need an existing target for processing.
+
+### Virus Scanning
+
+To enable virus scanning as a postprocessing step after uploading a file, the environment variable `POSTPROCESSING_STEPS` needs to contain the word `virusscan` at one location in the list of steps. As a result, each uploaded file gets virus scanned as part of the postprocessing steps. Note that the `antivirus` service is required to be enabled and configured for this to work.
+
+### Delay
+
+Though this is for development purposes only and NOT RECOMMENDED on production systems, setting the environment variable `POSTPROCESSING_DELAY` to a duration not equal to zero will add a delay step with the configured amount of time. OpenCloud will continue postprocessing the file after the configured delay. Use the environment variable `POSTPROCESSING_STEPS` and the keyword `delay` if you have multiple postprocessing steps and want to define their order. If `POSTPROCESSING_DELAY` is set but the keyword `delay` is not contained in `POSTPROCESSING_STEPS`, it will be processed as last postprocessing step without being listed there. In this case, a log entry will be written on service startup to notify the admin about that situation. That log entry can be avoided by adding the keyword `delay` to `POSTPROCESSING_STEPS`.
+
+### Custom Postprocessing Steps
+By using the envvar `POSTPROCESSING_STEPS`, custom postprocessing steps can be added. Any word can be used as step name but be careful not to conflict with exising keywords like `virusscan` and `delay`. In addition, if a keyword is misspelled or the corresponding service does either not exist or does not follow the necessary event communication, the postprocessing service will wait forever getting the required response to proceed and does not continue any other processing.
+
+#### Prerequisites
+For using custom postprocessing steps you need a custom service listening to the configured event system (see `General Prerequisites`)
+
+#### Workflow
+When defining a custom postprocessing step (eg. `"customstep"`), the postprocessing service will eventually send an event during postprocessing. The event will be of type `StartPostprocessingStep` with its field `StepToStart` set to `"customstep"`. When the service defined as custom step receives this event, it can safely execute its actions. The postprocessing service will wait until it has finished its work. The event contains further information (filename, executing user, size, ...) and also requires tokens and URLs to download the file in case byte inspection is necessary.
+
+Once the service defined as custom step has finished its work, it should send an event of type `PostprocessingFinished` via the configured events system back to the postprocessing service. This event needs to contain a `FinishedStep` field set to `"customstep"`. It also must contain the outcome of the step, which can be one of the following:
+
+-   `delete`: Abort postprocessing, delete the file.
+-   `abort`: Abort postprocessing, keep the file.
+-   `retry`: There was a problem that was most likely temporary and may be solved by trying again after some backoff duration. Retry runs automatically and is defined by the backoff behavior as described below.
+-   `continue`: Continue postprocessing, this is the success case.
+
+The backoff behavior as mentioned in the `retry` outcome can be configured using the `POSTPROCESSING_RETRY_BACKOFF_DURATION` and `POSTPROCESSING_MAX_RETRIES` environment variables. The backoff duration is calculated using the following formula after each failure: `backoff_duration = POSTPROCESSING_RETRY_BACKOFF_DURATION * 2^(number of failures - 1)`. This means that the time between the next round grows exponentially limited by the number of retries. Steps that still don't succeed after the maximum number of retries will be automatically moved to the `abort` state.
+
+See the [cs3 org](https://github.com/cs3org/reva/blob/edge/pkg/events/postprocessing.go) for up-to-date information of reserved step names and event definitions.
+
+## CLI Commands
+
+### Resume Postprocessing
+
+**IMPORTANT**
+> If not noted otherwise, commands with the `restart` option can also use the `resume` option. This changes behaviour slightly.
+>
+> * `restart`\
+> When restarting an upload, all steps for open items will be restarted, except if otherwise defined.
+> * `resume`\
+> When resuming an upload, processing will continue unfinished items from their last completed step.
+
+If post-processing fails in one step due to an unforeseen error, current uploads will not be resumed automatically. A system administrator can instead run CLI commands to resume the failed upload manually which is at minimum a two step process.
+
+For details on the `storage-users` command see the **Manage Unfinished Uploads** documentation in the `storage-users` service documentation.
+
+Depending if you want to restart/resume all or defined failed uploads, different commands are used.
+
+-   First, list ongoing upload sessions to identify possibly failed ones.\
+    Note that there never can be a clear identification of a failed upload session due to various reasons causing them. You need to apply more critera like free space on disk, a failed service like antivirus etc. to declare an upload as failed.
+
+    ```bash
+    opencloud storage-users uploads sessions
+    ```
+
+-   **All failed uploads**\
+    If you want to restart/resume all failed uploads, just rerun the command with the relevant flag. Note that this is the preferred command to handle failed processing steps:
+    ```bash
+    opencloud storage-users uploads sessions --resume
+    ```
+
+-   **Particular failed uploads**\
+    Use the `postprocessing` command to resume defined failed uploads. For postprocessing steps, the default is to resume . Note that at the moment, `resume` is an alias for `restart` to keep old functionality. `restart` is subject of change and will most likely be removed in a later version.
+
+    - **Defined by ID**\
+      If you want to resume only a specific upload, use the postprocessing resume command with the ID selected:
+      ```bash
+      opencloud postprocessing resume -u <uploadID>
+      ```
+
+    - **Defined by step**\
+      Alternatively, instead of restarting one specific upload, a system admin can also resume all uploads that are currently in a specific step.\
+      Examples:\
+      ```bash
+      opencloud postprocessing resume                # Resumes all uploads where postprocessing is finished, but upload is not finished
+      opencloud postprocessing resume -s "finished"  # Equivalent to the above
+      opencloud postprocessing resume -s "virusscan" # Resume all uploads currently in virusscan step
+      ```
+
+## Metrics
+
+The postprocessing service exposes the following prometheus metrics at `<debug_endpoint>/metrics` (as configured using the `POSTPROCESSING_DEBUG_ADDR` env var):
+
+| Metric Name | Type | Description | Labels |
+| --- | --- | --- | --- |
+| `opencloud_postprocessing_build_info` | Gauge | Build information | `version` |
+| `opencloud_postprocessing_events_outstanding_acks` | Gauge | Number of outstanding acks for events | |
+| `opencloud_postprocessing_events_unprocessed` | Gauge | Number of unprocessed events | |
+| `opencloud_postprocessing_events_redelivered` | Gauge | Number of redelivered events | |
+| `opencloud_postprocessing_in_progress` | Gauge | Number of postprocessing events in progress | |
+| `opencloud_postprocessing_finished` | Counter | Number of finished postprocessing events | `status` |
+| `opencloud_postprocessing_duration_seconds` | Histogram | Duration of postprocessing operations in seconds | `status` |
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/proxy.yaml b/versioned_docs/version-7.x/_static/env-vars/proxy.yaml
new file mode 100644
index 000000000..afcf227b8
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/proxy.yaml
@@ -0,0 +1,258 @@
+# Autogenerated
+# Filename: proxy.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9205
+  token: ""
+  pprof: false
+  zpages: false
+http:
+  addr: 0.0.0.0:9200
+  root: /
+  tls_cert: /var/lib/opencloud/proxy/server.crt
+  tls_key: /var/lib/opencloud/proxy/server.key
+  tls: true
+reva:
+  address: eu.opencloud.api.gateway
+  tls:
+    mode: ""
+    cacert: ""
+grpc_client_tls: null
+role_quotas: {}
+policies:
+- name: default
+  routes:
+  - endpoint: /
+    service: eu.opencloud.web.web
+    unprotected: true
+    skip_x_access_token: false
+  - endpoint: /.well-known/ocm
+    service: eu.opencloud.web.ocm
+    unprotected: true
+    skip_x_access_token: false
+  - endpoint: /.well-known/webfinger
+    service: eu.opencloud.web.webfinger
+    unprotected: true
+    skip_x_access_token: false
+  - endpoint: /.well-known/openid-configuration
+    service: eu.opencloud.web.idp
+    unprotected: true
+    skip_x_access_token: false
+  - endpoint: /branding/logo
+    service: eu.opencloud.web.web
+    skip_x_access_token: false
+  - endpoint: /konnect/
+    service: eu.opencloud.web.idp
+    unprotected: true
+    skip_x_access_token: false
+  - endpoint: /signin/
+    service: eu.opencloud.web.idp
+    unprotected: true
+    skip_x_access_token: false
+  - endpoint: /archiver
+    service: eu.opencloud.web.frontend
+    skip_x_access_token: false
+  - endpoint: /ocs/v2.php/apps/notifications/api/v1/notifications/sse
+    service: eu.opencloud.sse.sse
+    skip_x_access_token: false
+  - endpoint: /ocs/v2.php/apps/notifications/api/v1/notifications
+    service: eu.opencloud.web.userlog
+    skip_x_access_token: false
+  - type: regex
+    endpoint: /ocs/v[12].php/cloud/user/signing-key
+    service: eu.opencloud.web.ocs
+    skip_x_access_token: false
+  - type: regex
+    endpoint: /ocs/v[12].php/config
+    service: eu.opencloud.web.frontend
+    unprotected: true
+    skip_x_access_token: false
+  - endpoint: /sciencemesh/federations
+    service: eu.opencloud.web.ocm
+    unprotected: true
+    skip_x_access_token: false
+  - endpoint: /sciencemesh/discover
+    service: eu.opencloud.web.ocm
+    unprotected: true
+    skip_x_access_token: false
+  - endpoint: /sciencemesh/
+    service: eu.opencloud.web.ocm
+    skip_x_access_token: false
+  - endpoint: /ocm/
+    service: eu.opencloud.web.ocm
+    skip_x_access_token: false
+  - endpoint: /ocs/
+    service: eu.opencloud.web.frontend
+    skip_x_access_token: false
+  - type: query
+    endpoint: /remote.php/?preview=1
+    service: eu.opencloud.web.webdav
+    skip_x_access_token: false
+  - type: regex
+    method: REPORT
+    endpoint: (/remote.php)?/(web)?dav
+    service: eu.opencloud.web.webdav
+    skip_x_access_token: false
+  - type: query
+    endpoint: /dav/?preview=1
+    service: eu.opencloud.web.webdav
+    skip_x_access_token: false
+  - type: query
+    endpoint: /webdav/?preview=1
+    service: eu.opencloud.web.webdav
+    skip_x_access_token: false
+  - endpoint: /remote.php/
+    service: eu.opencloud.web.frontend
+    skip_x_access_token: false
+  - endpoint: /dav/
+    service: eu.opencloud.web.frontend
+    skip_x_access_token: false
+  - endpoint: /webdav/
+    service: eu.opencloud.web.frontend
+    skip_x_access_token: false
+  - endpoint: /status
+    service: eu.opencloud.web.frontend
+    unprotected: true
+    skip_x_access_token: false
+  - endpoint: /status.php
+    service: eu.opencloud.web.frontend
+    unprotected: true
+    skip_x_access_token: false
+  - endpoint: /index.php/
+    service: eu.opencloud.web.frontend
+    skip_x_access_token: false
+  - endpoint: /apps/
+    service: eu.opencloud.web.frontend
+    skip_x_access_token: false
+  - endpoint: /data
+    service: eu.opencloud.web.frontend
+    unprotected: true
+    skip_x_access_token: false
+  - endpoint: /app/list
+    service: eu.opencloud.web.frontend
+    unprotected: true
+    skip_x_access_token: false
+  - endpoint: /app/
+    service: eu.opencloud.web.frontend
+    skip_x_access_token: false
+  - endpoint: /graph/v1beta1/extensions/org.libregraph/activities
+    service: eu.opencloud.web.activitylog
+    skip_x_access_token: false
+  - endpoint: /graph/v1.0/invitations
+    service: eu.opencloud.web.invitations
+    skip_x_access_token: false
+  - endpoint: /graph/
+    service: eu.opencloud.web.graph
+    skip_x_access_token: false
+  - endpoint: /api/v0/settings
+    service: eu.opencloud.web.settings
+    skip_x_access_token: false
+  - endpoint: /auth-app/tokens
+    service: eu.opencloud.web.auth-app
+    skip_x_access_token: false
+  - endpoint: /wopi
+    service: eu.opencloud.web.collaboration
+    unprotected: true
+    skip_x_access_token: true
+  - endpoint: /collaboration/fonts/manage
+    service: eu.opencloud.web.collaboration
+    skip_x_access_token: false
+  - endpoint: /collaboration/notify
+    service: eu.opencloud.web.collaboration
+    skip_x_access_token: false
+  - endpoint: /collaboration
+    service: eu.opencloud.web.collaboration
+    unprotected: true
+    skip_x_access_token: false
+additional_policies: []
+oidc:
+  issuer: https://localhost:9200
+  insecure: false
+  access_token_verify_method: jwt
+  skip_user_info: false
+  user_info_cache:
+    store: memory
+    addresses:
+    - 127.0.0.1:9233
+    database: cache-userinfo
+    table: ""
+    ttl: 10s
+    disable_persistence: false
+    username: ""
+    password: ""
+    enable_tls: false
+    tls_insecure: false
+    tls_root_ca_certificate: ""
+  jwks:
+    refresh_interval: 60
+    refresh_timeout: 10
+    refresh_limit: 60
+    refresh_unknown_kid: true
+  rewrite_well_known: false
+service_account:
+  service_account_id: ""
+  service_account_secret: ""
+role_assignment:
+  driver: default
+  oidc_role_mapper:
+    role_claim: roles
+    role_mapping:
+    - role_name: admin
+      claim_value: opencloudAdmin
+    - role_name: spaceadmin
+      claim_value: opencloudSpaceAdmin
+    - role_name: user
+      claim_value: opencloudUser
+    - role_name: user-light
+      claim_value: opencloudGuest
+policy_selector:
+  static:
+    policy: default
+  claims: null
+  regex: null
+pre_signed_url:
+  allowed_http_methods:
+  - GET
+  enabled: true
+  signing_keys:
+    store: nats-js-kv
+    addresses:
+    - 127.0.0.1:9233
+    ttl: 12h0m0s
+    disable_persistence: true
+    username: ""
+    password: ""
+    enable_tls: false
+    tls_insecure: false
+    tls_root_ca_certificate: ""
+account_backend: cs3
+user_oidc_claim: preferred_username
+user_cs3_claim: username
+tenant_oidc_claim: ""
+tenant_id_mapping_enabled: false
+machine_auth_api_key: ""
+auto_provision_accounts: false
+auto_provision_claims:
+  username: preferred_username
+  email: email
+  display_name: name
+  groups: groups
+enable_basic_auth: false
+insecure_backends: false
+backend_https_cacert: ""
+auth_middleware:
+  credentials_by_user_agent: {}
+  allow_app_auth: true
+policies_middleware:
+  query: ""
+csp_config_file_location: ""
+csp_config_file_override_location: ""
+events:
+  endpoint: 127.0.0.1:9233
+  cluster: opencloud-cluster
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+  enable_tls: false
+  username: ""
+  password: ""
diff --git a/versioned_docs/version-7.x/_static/env-vars/proxy_configvars.md b/versioned_docs/version-7.x/_static/env-vars/proxy_configvars.md
new file mode 100644
index 000000000..91ab670d1
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/proxy_configvars.md
@@ -0,0 +1,76 @@
+## Environment variables for the **proxy** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`PROXY_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`PROXY_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9205`|
+|`PROXY_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`PROXY_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`PROXY_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`PROXY_HTTP_ADDR`| 1.0.0 |string|`The bind address of the HTTP service.`|`0.0.0.0:9200`|
+|`PROXY_HTTP_ROOT`| 1.0.0 |string|`Subdirectory that serves as the root for this HTTP service.`|`/`|
+|`PROXY_TRANSPORT_TLS_CERT`| 1.0.0 |string|`Path/File name of the TLS server certificate (in PEM format) for the external http services. If not defined, the root directory derives from $OC_BASE_DATA_PATH/proxy.`|`/var/lib/opencloud/proxy/server.crt`|
+|`PROXY_TRANSPORT_TLS_KEY`| 1.0.0 |string|`Path/File name for the TLS certificate key (in PEM format) for the server certificate to use for the external http services. If not defined, the root directory derives from $OC_BASE_DATA_PATH/proxy.`|`/var/lib/opencloud/proxy/server.key`|
+|`PROXY_TLS`| 1.0.0 |bool|`Enable/Disable HTTPS for external HTTP services. Must be set to 'true' if the built-in IDP service and no reverse proxy is used. See the text description for details.`|`true`|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`The CS3 gateway endpoint.`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
+|`OC_URL`<br/>`OC_OIDC_ISSUER`<br/>`PROXY_OIDC_ISSUER`| 1.0.0 |string|`URL of the OIDC issuer. It defaults to URL of the builtin IDP.`|`https://localhost:9200`|
+|`OC_INSECURE`<br/>`PROXY_OIDC_INSECURE`| 1.0.0 |bool|`Disable TLS certificate validation for connections to the IDP. Note that this is not recommended for production environments.`|`false`|
+|`PROXY_OIDC_ACCESS_TOKEN_VERIFY_METHOD`| 1.0.0 |string|`Sets how OIDC access tokens should be verified. Possible values are 'none' and 'jwt'. When using 'none', no special validation apart from using it for accessing the IDP's userinfo endpoint will be done. When using 'jwt', it tries to parse the access token as a jwt token and verifies the signature using the keys published on the IDP's 'jwks_uri'.`|`jwt`|
+|`PROXY_OIDC_SKIP_USER_INFO`| 1.0.0 |bool|`Do not look up user claims at the userinfo endpoint and directly read them from the access token. Incompatible with 'PROXY_OIDC_ACCESS_TOKEN_VERIFY_METHOD=none'.`|`false`|
+|`OC_CACHE_STORE`<br/>`PROXY_OIDC_USERINFO_CACHE_STORE`| 1.0.0 |string|`The type of the cache store. Supported values are: 'memory', 'redis-sentinel', 'nats-js-kv', 'noop'. See the text description for details.`|`memory`|
+|`OC_CACHE_STORE_NODES`<br/>`PROXY_OIDC_USERINFO_CACHE_STORE_NODES`| 1.0.0 |[]string|`A list of nodes to access the configured store. This has no effect when 'memory' store is configured. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details.`|`[127.0.0.1:9233]`|
+|`OC_CACHE_DATABASE`| 1.0.0 |string|`The database name the configured store should use.`|`cache-userinfo`|
+|`PROXY_OIDC_USERINFO_CACHE_TABLE`| 1.0.0 |string|`The database table the store should use.`|``|
+|`OC_CACHE_TTL`<br/>`PROXY_OIDC_USERINFO_CACHE_TTL`| 1.0.0 |Duration|`Default time to live for user info in the user info cache. Only applied when access tokens has no expiration. See the Environment Variable Types description for more details.`|`10s`|
+|`OC_CACHE_DISABLE_PERSISTENCE`<br/>`PROXY_OIDC_USERINFO_CACHE_DISABLE_PERSISTENCE`| 1.0.0 |bool|`Disables persistence of the cache. Only applies when store type 'nats-js-kv' is configured. Defaults to false.`|`false`|
+|`OC_CACHE_AUTH_USERNAME`<br/>`PROXY_OIDC_USERINFO_CACHE_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the cache. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_CACHE_AUTH_PASSWORD`<br/>`PROXY_OIDC_USERINFO_CACHE_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the cache. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_CACHE_ENABLE_TLS`<br/>`PROXY_OIDC_USERINFO_CACHE_ENABLE_TLS`| next |bool|`Enable TLS for the connection to file metadata cache.`|`false`|
+|`OC_INSECURE`<br/>`OC_CACHE_TLS_INSECURE`<br/>`PROXY_OIDC_USERINFO_CACHE_TLS_INSECURE`| next |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_CACHE_TLS_ROOT_CA_CERTIFICATE`<br/>`PROXY_OIDC_USERINFO_CACHE_TLS_ROOT_CA_CERTIFICATE`| next |string|`The root CA certificate used to validate the server's TLS certificate. If provided PROXY_OIDC_USERINFO_CACHE_TLS_INSECURE will be seen as false.`|``|
+|`PROXY_OIDC_JWKS_REFRESH_INTERVAL`| 1.0.0 |uint64|`The interval for refreshing the JWKS (JSON Web Key Set) in minutes in the background via a new HTTP request to the IDP.`|`60`|
+|`PROXY_OIDC_JWKS_REFRESH_TIMEOUT`| 1.0.0 |uint64|`The timeout in seconds for an outgoing JWKS request.`|`10`|
+|`PROXY_OIDC_JWKS_REFRESH_RATE_LIMIT`| 1.0.0 |uint64|`Limits the rate in seconds at which refresh requests are performed for unknown keys. This is used to prevent malicious clients from imposing high network load on the IDP via OpenCloud.`|`60`|
+|`PROXY_OIDC_JWKS_REFRESH_UNKNOWN_KID`| 1.0.0 |bool|`If set to 'true', the JWKS refresh request will occur every time an unknown KEY ID (KID) is seen. Always set a 'refresh_limit' when enabling this.`|`true`|
+|`PROXY_OIDC_REWRITE_WELLKNOWN`| 1.0.0 |bool|`Enables rewriting the /.well-known/openid-configuration to the configured OIDC issuer. Needed by the Desktop Client, Android Client and iOS Client to discover the OIDC provider.`|`false`|
+|`OC_SERVICE_ACCOUNT_ID`<br/>`PROXY_SERVICE_ACCOUNT_ID`| 1.0.0 |string|`The ID of the service account the service should use. See the 'auth-service' service description for more details.`|``|
+|`OC_SERVICE_ACCOUNT_SECRET`<br/>`PROXY_SERVICE_ACCOUNT_SECRET`| 1.0.0 |string|`The service account secret.`|``|
+|`PROXY_ROLE_ASSIGNMENT_DRIVER`| 1.0.0 |string|`The mechanism that should be used to assign roles to user upon login. Supported values: 'default' or 'oidc'. 'default' will assign the role 'user' to users which don't have a role assigned at the time they login. 'oidc' will assign the role based on the value of a claim (configured via PROXY_ROLE_ASSIGNMENT_OIDC_CLAIM) from the users OIDC claims.`|`default`|
+|`PROXY_ROLE_ASSIGNMENT_OIDC_CLAIM`| 1.0.0 |string|`The OIDC claim used to create the users role assignment.`|`roles`|
+|`PROXY_ENABLE_PRESIGNEDURLS`| 1.0.0 |bool|`Allow OCS to get a signing key to sign requests.`|`true`|
+|`OC_CACHE_STORE`<br/>`PROXY_PRESIGNEDURL_SIGNING_KEYS_STORE`| 1.0.0 |string|`The type of the signing key store. Supported values are: 'redis-sentinel', 'nats-js-kv' and 'opencloudstoreservice' (deprecated). See the text description for details.`|`nats-js-kv`|
+|`OC_CACHE_STORE_NODES`<br/>`PROXY_PRESIGNEDURL_SIGNING_KEYS_STORE_NODES`| 1.0.0 |[]string|`A list of nodes to access the configured store. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details.`|`[127.0.0.1:9233]`|
+|`OC_CACHE_TTL`<br/>`PROXY_PRESIGNEDURL_SIGNING_KEYS_STORE_TTL`| 1.0.0 |Duration|`Default time to live for signing keys. See the Environment Variable Types description for more details.`|`12h0m0s`|
+|`OC_CACHE_DISABLE_PERSISTENCE`<br/>`PROXY_PRESIGNEDURL_SIGNING_KEYS_STORE_DISABLE_PERSISTENCE`| 1.0.0 |bool|`Disables persistence of the store. Only applies when store type 'nats-js-kv' is configured. Defaults to true.`|`true`|
+|`OC_CACHE_AUTH_USERNAME`<br/>`PROXY_PRESIGNEDURL_SIGNING_KEYS_STORE_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_CACHE_AUTH_PASSWORD`<br/>`PROXY_PRESIGNEDURL_SIGNING_KEYS_STORE_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_CACHE_ENABLE_TLS`<br/>`PROXY_PRESIGNEDURL_SIGNING_KEYS_STORE_ENABLE_TLS`| next |bool|`Enable TLS for the connection to file metadata cache.`|`false`|
+|`OC_INSECURE`<br/>`OC_CACHE_TLS_INSECURE`<br/>`PROXY_PRESIGNEDURL_SIGNING_KEYS_STORE_TLS_INSECURE`| next |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_CACHE_TLS_ROOT_CA_CERTIFICATE`<br/>`PROXY_PRESIGNEDURL_SIGNING_KEYS_STORE_TLS_ROOT_CA_CERTIFICATE`| next |string|`The root CA certificate used to validate the server's TLS certificate. If provided PROXY_PRESIGNEDURL_SIGNING_KEYS_STORE_TLS_INSECURE will be seen as false.`|``|
+|`PROXY_ACCOUNT_BACKEND_TYPE`| 1.0.0 |string|`Account backend the PROXY service should use. Currently only 'cs3' is possible here.`|`cs3`|
+|`PROXY_USER_OIDC_CLAIM`| 1.0.0 |string|`The name of an OpenID Connect claim that is used for resolving users with the account backend. The value of the claim must hold a per user unique, stable and non re-assignable identifier. The availability of claims depends on your Identity Provider. There are common claims available for most Identity providers like 'email' or 'preferred_username' but you can also add your own claim.`|`preferred_username`|
+|`PROXY_USER_CS3_CLAIM`| 1.0.0 |string|`The name of a CS3 user attribute (claim) that should be mapped to the 'user_oidc_claim'. Supported values are 'username', 'mail' and 'userid'.`|`username`|
+|`PROXY_TENANT_OIDC_CLAIM`| 6.1.0 |string|`JMESPath expression to extract the tenant ID from the OIDC token claims. When set, the extracted value is verified against the tenant ID returned by the user backend, rejecting requests where they do not match. Only relevant when multi-tenancy is enabled.`|``|
+|`PROXY_TENANT_ID_MAPPING_ENABLED`| 6.1.0 |bool|`When set to 'true', the proxy will resolve the internal tenant ID from the external tenant ID provided in the OIDC claims by calling the TenantAPI before verifying the tenant. Use this when the external tenant ID in the OIDC token differs from the internal tenant ID stored on the user. Requires 'tenant_oidc_claim' to be set. Only relevant when multi-tenancy is enabled.`|`false`|
+|`OC_MACHINE_AUTH_API_KEY`<br/>`PROXY_MACHINE_AUTH_API_KEY`| 1.0.0 |string|`Machine auth API key used to validate internal requests necessary to access resources from other services.`|``|
+|`PROXY_AUTOPROVISION_ACCOUNTS`| 1.0.0 |bool|`Set this to 'true' to automatically provision users that do not yet exist in the users service on-demand upon first sign-in. To use this a write-enabled libregraph user backend needs to be setup an running.`|`false`|
+|`PROXY_AUTOPROVISION_CLAIM_USERNAME`| 1.0.0 |string|`The name of the OIDC claim that holds the username.`|`preferred_username`|
+|`PROXY_AUTOPROVISION_CLAIM_EMAIL`| 1.0.0 |string|`The name of the OIDC claim that holds the email.`|`email`|
+|`PROXY_AUTOPROVISION_CLAIM_DISPLAYNAME`| 1.0.0 |string|`The name of the OIDC claim that holds the display name.`|`name`|
+|`PROXY_AUTOPROVISION_CLAIM_GROUPS`| 1.0.0 |string|`The name of the OIDC claim that holds the groups.`|`groups`|
+|`PROXY_ENABLE_BASIC_AUTH`| 1.0.0 |bool|`Set this to true to enable 'basic authentication' (username/password).`|`false`|
+|`PROXY_INSECURE_BACKENDS`| 1.0.0 |bool|`Disable TLS certificate validation for all HTTP backend connections.`|`false`|
+|`PROXY_HTTPS_CACERT`| 1.0.0 |string|`Path/File for the root CA certificate used to validate the server’s TLS certificate for https enabled backend services.`|``|
+|`PROXY_ENABLE_APP_AUTH`| 1.0.0 |bool|`Allow app authentication. This can be used to authenticate 3rd party applications. Note that auth-app service must be running for this feature to work.`|`true`|
+|`PROXY_POLICIES_QUERY`| 1.0.0 |string|`Defines the 'Complete Rules' variable defined in the rego rule set this step uses for its evaluation. Rules default to deny if the variable was not found.`|``|
+|`PROXY_CSP_CONFIG_FILE_LOCATION`| 1.0.0 |string|`The location of the CSP configuration file.`|``|
+|`PROXY_CSP_CONFIG_FILE_OVERRIDE_LOCATION`| 4.0.0 |string|`The location of the CSP configuration file override.`|``|
+|`OC_EVENTS_ENDPOINT`<br/>`PROXY_EVENTS_ENDPOINT`| 1.0.0 |string|`The address of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture. Set to a empty string to disable emitting events.`|`127.0.0.1:9233`|
+|`OC_EVENTS_CLUSTER`<br/>`PROXY_EVENTS_CLUSTER`| 1.0.0 |string|`The clusterID of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture.`|`opencloud-cluster`|
+|`OC_INSECURE`<br/>`OC_EVENTS_TLS_INSECURE`<br/>`PROXY_EVENTS_TLS_INSECURE`| 1.0.0 |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_EVENTS_TLS_ROOT_CA_CERTIFICATE`<br/>`PROXY_EVENTS_TLS_ROOT_CA_CERTIFICATE`| 1.0.0 |string|`The root CA certificate used to validate the server's TLS certificate. If provided PROXY_EVENTS_TLS_INSECURE will be seen as false.`|``|
+|`OC_EVENTS_ENABLE_TLS`<br/>`PROXY_EVENTS_ENABLE_TLS`| 1.0.0 |bool|`Enable TLS for the connection to the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|`false`|
+|`OC_EVENTS_AUTH_USERNAME`<br/>`PROXY_EVENTS_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_EVENTS_AUTH_PASSWORD`<br/>`PROXY_EVENTS_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
diff --git a/versioned_docs/version-7.x/_static/env-vars/proxy_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/proxy_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/proxy_readme.md b/versioned_docs/version-7.x/_static/env-vars/proxy_readme.md
new file mode 100755
index 000000000..8673b8ea0
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/proxy_readme.md
@@ -0,0 +1,348 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The proxy service is an API-Gateway for the OpenCloud microservices. Every HTTP request goes through this service. Authentication, logging and other preprocessing of requests also happens here. Mechanisms like request rate limiting or intrusion prevention are **not** included in the proxy service and must be setup in front like with an external reverse proxy.
+
+The proxy service is the only service communicating to the outside and needs therefore usual protections against DDOS, Slow Loris or other attack vectors. All other services are not exposed to the outside, but also need protective measures when it comes to distributed setups like when using container orchestration over various physical servers.
+
+
+## Table of Contents
+
+* [Authentication](#authentication)
+* [Configuring Routes](#configuring-routes)
+* [Automatic User and Group Provisioning](#automatic-user-and-group-provisioning)
+  * [Prequisites](#prequisites)
+  * [Configuration](#configuration)
+  * [How it Works](#how-it-works)
+  * [Claim Updates](#claim-updates)
+    * [Impacts](#impacts)
+* [Automatic Quota Assignments](#automatic-quota-assignments)
+* [Automatic Role Assignments](#automatic-role-assignments)
+* [Recommendations for Production Deployments](#recommendations-for-production-deployments)
+  * [Content Security Policy](#content-security-policy)
+* [Caching](#caching)
+* [Presigned Urls](#presigned-urls)
+* [Special Settings](#special-settings)
+* [Metrics](#metrics)
+  * [1) Single Process Mode](#1-single-process-mode)
+  * [2) Standalone Mode](#2-standalone-mode)
+  * [Available Metrics](#available-metrics)
+  * [Prometheus Configuration](#prometheus-configuration)
+
+## Authentication
+
+The following request authentication schemes are implemented:
+
+-   Basic Auth (Only use in development, **never in production** setups!)
+-   OpenID Connect
+-   Signed URL
+-   Public Share Token
+
+## Configuring Routes
+
+The proxy handles routing to all endpoints that OpenCloud offers. The currently availabe default routes can be found [in the code](https://github.com/opencloud-eu/opencloud/blob/main/services/proxy/pkg/config/defaults/defaultconfig.go). Changing or adding routes can be necessary when writing own OpenCloud extensions.
+
+Due to the complexity when defining routes, these can only be defined in the yaml file but not via environment variables.
+
+For _overwriting_ default routes, use the following yaml example:
+
+```yaml
+policies:
+  - name: opencloud
+    routes:
+      - endpoint: /
+        service: eu.opencloud.web.web
+      - endpoint: /dav/
+        service: eu.opencloud.web.frontend
+```
+
+For adding _additional_ routes to the default routes use:
+
+```yaml
+additional_policies:
+  - name: opencloud
+    routes:
+      - endpoint: /custom/endpoint
+        service: eu.opencloud.custom.custom
+```
+
+A route has the following configurable parameters:
+
+```yaml
+endpoint: ""       # the url that should be routed
+service: ""        # the service the url should be routed to
+unprotected: false # with false (default), calling the endpoint requires authorization.
+                   # with true, anyone can call the endpoint without authorisation.
+```
+
+## Automatic User and Group Provisioning
+
+When using an external OpenID Connect IDP, the proxy can be configured to automatically provision
+users upon their first login.
+
+### Prequisites
+
+A number of prerequisites must be met for automatic user provisioning to work:
+
+* OpenCloud must be configured to use an external OpenID Connect IDP
+* The `graph` service must be configured to allow updating users and groups
+  (`GRAPH_LDAP_SERVER_WRITE_ENABLED`).
+* One of the claim values returned by the IDP as part of the userinfo response
+  or the access token must be unique and stable for the user. I.e. the value
+  must not change for the whole lifetime of the user. This claim is configured
+  via the `PROXY_USER_OIDC_CLAIM` environment variable (see below). A natural
+  choice would e.g. be the `sub` claim which is guaranteed to be unique and
+  stable per IDP. If a claim like `email` or `preferred_username` is used, you
+  have to ensure that the user's email address or username never changes.
+
+### Configuration
+
+To enable automatic user provisioning, the following environment variables must
+be set for the proxy service:
+
+* `PROXY_AUTOPROVISION_ACCOUNTS`\
+Set to `true` to enable automatic user provisioning.
+* `PROXY_AUTOPROVISION_CLAIM_USERNAME`\
+The name of an OIDC claim whose value should be used as the username for the
+autoprovsioned user in OpenCloud. Defaults to `preferred_username`.
+Can also be set to e.g. `sub` to guarantee a unique and stable username.
+* `PROXY_AUTOPROVISION_CLAIM_EMAIL`\
+The name of an OIDC claim whose value should be used for the `mail` attribute
+of the autoprovisioned user in OpenCloud. Defaults to `email`.
+* `PROXY_AUTOPROVISION_CLAIM_DISPLAYNAME`\
+The name of an OIDC claim whose value should be used for the `displayname`
+attribute of the autoprovisioned user in OpenCloud. Defaults to `name`.
+* `PROXY_AUTOPROVISION_CLAIM_GROUPS`\
+The name of an OIDC claim whose value should be used to maintain a user's group
+membership. The claim value should contain a list of group names the user should
+be a member of. Defaults to `groups`.
+* `PROXY_USER_OIDC_CLAIM`\
+When resolving and authenticated OIDC user, the value of this claims is used to
+lookup the user in the users service. For auto provisioning setups this usually is the
+same claims as set via `PROXY_AUTOPROVISION_CLAIM_USERNAME`.
+* `PROXY_USER_CS3_CLAIM`\
+This is the name of the user attribute in OpenCloud that is used to lookup the user by the
+value of the `PROXY_USER_OIDC_CLAIM`. For auto provisioning setups this usually
+needs to be set to `username`.
+
+### How it Works
+
+When a user logs into OpenCloud for the first time, the proxy
+checks if that user already exists. This is done by querying the `users` service for users,
+where the attribute set in `PROXY_USER_CS3_CLAIM` matches the value of the OIDC
+claim configured in `PROXY_USER_OIDC_CLAIM`.
+
+If the users does not exist, the proxy will create a new user via the `graph`
+service using the claim values configured in
+`PROXY_AUTOPROVISION_CLAIM_USERNAME`, `PROXY_AUTOPROVISION_CLAIM_EMAIL` and
+`PROXY_AUTOPROVISION_CLAIM_DISPLAYNAME`.
+
+If the user does already exist, the proxy checks if the displayname has changed
+and updates that accordingly via `graph` service.
+
+Unless the claim configured via `PROXY_AUTOPROVISION_CLAIM_EMAIL` is the same
+as the one set via `PROXY_USER_OIDC_CLAIM` the proxy will also check if the
+email address has changed and update that as well.
+
+Next, the proxy will check if the user is a member of the groups configured in
+`PROXY_AUTOPROVISION_CLAIM_GROUPS`. It will add the user to the groups listed
+via the OIDC claim that holds the groups defined in the envvar and removes it from
+all other groups that he is currently a member of.
+Groups that do not exist in the external IDP yet will be created. Note: This can be a
+somewhat costly operation, especially if the user is a member of a large number of
+groups. If the group memberships of a user are changed in the IDP after the
+first login, it can take up to 5 minutes until the changes are reflected in OpenCloud.
+
+### Claim Updates
+
+OpenID Connect (OIDC) scopes are used by an application during authentication to authorize access to a user's detail, like name, email or picture information. A scope can also contain among other things groups, roles, and permissions data. Each scope returns a set of attributes, which are called claims. The scopes an application requests, depends on which  attributes the application needs. Once the user authorizes the requested scopes, the claims are returned in a token.
+
+These issued JWT tokens are immutable and integrity-protected. Which means, any change in the source requires issuing a new token containing updated claims. On the other hand side, there is no active synchronisation process between the identity provider (IDP) who issues the token and OpenCloud. The earliest possible time that OpenCloud will notice changes is, when the current access token has expired and a new access token is issued by the IDP, or the user logs out and relogs in.
+
+**NOTES**
+
+* For resource optimisation, OpenCloud skips any checks and updates on groupmemberships, if the last update happened less than 5min ago.
+
+* OpenCloud can't differentiate between a group being renamed in the IDP and users being reassigned to a different group.
+
+* OpenCloud does not get aware when a group is being deleted in the IDP, a new claim will not hold any information from the deleted group. OpenCloud does not track a claim history to compare.
+
+#### Impacts
+
+For shares or space memberships based on groups, a renamed or deleted group will impact accessing the resource:
+
+* There is no user notification about the inability accessing the resource.
+* The user will only experience rejected access.
+* This also applies for connected apps like the Desktop, iOS or Android app!
+
+To give access for rejected users on a resource, one with rights to share must update the group information.
+
+## Automatic Quota Assignments
+
+It is possible to automatically assign a specific quota to new users depending on their role.
+To do this, you need to configure a mapping between roles defined by their ID and the quota in bytes.
+The assignment can only be done via a `yaml` configuration and not via environment variables.
+See the following `proxy.yaml` config snippet for a configuration example.
+
+```yaml
+role_quotas:
+    <role ID1>: <quota1>
+    <role ID2>: <quota2>
+```
+
+## Automatic Role Assignments
+
+When users login, they do automatically get a role assigned. The automatic role assignment can be
+configured in different ways. The `PROXY_ROLE_ASSIGNMENT_DRIVER` environment variable (or the `driver`
+setting in the `role_assignment` section of the configuration file select which mechanism to use for
+the automatic role assignment.
+
+When set to `default`, all users which do not have a role assigned at the time for the first login will
+get the role 'user' assigned. (This is also the default behavior if `PROXY_ROLE_ASSIGNMENT_DRIVER`
+is unset.
+
+When `PROXY_ROLE_ASSIGNMENT_DRIVER` is set to `oidc` the role assignment for a user will happen
+based on the values of an OpenID Connect Claim of that user. The name of the OpenID Connect Claim to
+be used for the role assignment can be configured via the `PROXY_ROLE_ASSIGNMENT_OIDC_CLAIM`
+environment variable. It is also possible to define a mapping of claim values to role names defined
+in OpenCloud via a `yaml` configuration. See the following `proxy.yaml` snippet for an example.
+
+```yaml
+role_assignment:
+    driver: oidc
+    oidc_role_mapper:
+        role_claim: opencloudRoles
+        role_mapping:
+            - role_name: admin
+              claim_value: myAdminRole
+            - role_name: spaceadmin
+              claim_value: mySpaceAdminRole
+            - role_name: user
+              claim_value: myUserRole
+            - role_name: user-light
+              claim_value: myGuestRole
+```
+
+This would assign the role `admin` to users with the value `myAdminRole` in the claim `opencloudRoles`.
+The role `user` to users with the values `myUserRole` in the claims `opencloudRoles` and so on.
+
+Claim values that are not mapped to a specific OpenCloud role will be ignored.
+
+Note: An OpenCloud user can only have a single role assigned. If the configured
+`role_mapping` and a user's claim values result in multiple possible roles for a user, the order in
+which the role mappings are defined in the configuration is important. The first role in the
+`role_mappings` where the `claim_value` matches a value from the user's roles claim will be assigned
+to the user. So if e.g. a user's `opencloudRoles` claim has the values `myUserRole` and
+`mySpaceAdminRole` that user will get the OpenCloud role `spaceadmin` assigned (because `spaceadmin`
+appears before `user` in the above sample configuration).
+
+If a user's claim values don't match any of the configured role mappings an error will be logged and
+the user will not be able to login.
+
+The default `role_claim` (or `PROXY_ROLE_ASSIGNMENT_OIDC_CLAIM`) is `roles`. The default `role_mapping` is:
+
+```yaml
+- role_name: admin
+  claim_value: opencloudAdmin
+- role_name: spaceadmin
+  claim_value: opencloudSpaceAdmin
+- role_name: user
+  claim_value: opencloudUser
+- role_name: user-light
+  claim_value: opencloudcloudGuest
+```
+
+## Recommendations for Production Deployments
+
+In a production deployment, you want to have basic authentication (`PROXY_ENABLE_BASIC_AUTH`) disabled which is the default state. You also want to setup a firewall to only allow requests to the proxy service or the reverse proxy if you have one. Requests to the other services should be blocked by the firewall.
+
+### Content Security Policy
+
+For OpenCloud, external resources like an IDP (e.g. Keycloak) or when using web office documents or web apps, require defining a CSP. If not defined, the referenced services will not work.
+
+To create a Content Security Policy (CSP), you need to create a yaml file containing the CSP definitions. To activate the settings, reference the file as value in the `PROXY_CSP_CONFIG_FILE_LOCATION` environment variable. For each change, a restart of the OpenCloud deployment or the proxy service is required.
+
+A working example for a CSP can be found in a sub path of the `config` directory of the [opencloud-compose](https://github.com/opencloud-eu/opencloud-compose/tree/main/config) deployment example.
+
+See the [Content Security Policy (CSP) Quick Reference Guide](https://content-security-policy.com) for a description of directives.
+
+## Caching
+
+The `proxy` service can use a configured store via `PROXY_OIDC_USERINFO_CACHE_STORE`. Possible stores are:
+  -   `memory`: Basic in-memory store and the default.
+  -   `redis-sentinel`: Stores data in a configured Redis Sentinel cluster.
+  -   `nats-js-kv`: Stores data using key-value-store feature of [nats jetstream](https://docs.nats.io/nats-concepts/jetstream/key-value-store)
+  -   `noop`: Stores nothing. Useful for testing. Not recommended in production environments.
+
+Other store types may work but are not supported currently.
+
+Note: The service can only be scaled if not using `memory` store and the stores are configured identically over all instances!
+
+Note that if you have used one of the deprecated stores, you should reconfigure to one of the supported ones as the deprecated stores will be removed in a later version.
+
+Store specific notes:
+  -   When using `redis-sentinel`, the Redis master to use is configured via e.g. `OC_CACHE_STORE_NODES` in the form of `<sentinel-host>:<sentinel-port>/<redis-master>` like `10.10.0.200:26379/mymaster`.
+  -   When using `nats-js-kv` it is recommended to set `OC_CACHE_STORE_NODES` to the same value as `OC_EVENTS_ENDPOINT`. That way the cache uses the same nats instance as the event bus.
+  -   When using the `nats-js-kv` store, it is possible to set `OC_CACHE_DISABLE_PERSISTENCE` to instruct nats to not persist cache data on disc.
+
+
+## Presigned Urls
+
+To authenticate presigned URLs the proxy service needs to read signing keys from a store that is populated by the ocs service. Possible stores are:
+  -   `nats-js-kv`: Stores data using key-value-store feature of [nats jetstream](https://docs.nats.io/nats-concepts/jetstream/key-value-store)
+  -   `redis-sentinel`: Stores data in a configured Redis Sentinel cluster.
+  -   `opencloudstoreservice`:  Stores data in the legacy OpenCloud store service. Requires setting `PROXY_PRESIGNEDURL_SIGNING_KEYS_STORE_NODES` to `eu.opencloud.api.store`.
+
+The `memory` store cannot be used as it does not share the memory from the ocs service signing key memory store, even in a single process.
+
+Make sure to configure the same store in the ocs service.
+
+Store specific notes:
+  -   When using `redis-sentinel`, the Redis master to use is configured via e.g. `OC_CACHE_STORE_NODES` in the form of `<sentinel-host>:<sentinel-port>/<redis-master>` like `10.10.0.200:26379/mymaster`.
+  -   When using `nats-js-kv` it is recommended to set `OCS_PRESIGNEDURL_SIGNING_KEYS_STORE_NODES` to the same value as `PROXY_PRESIGNEDURL_SIGNING_KEYS_STORE_NODES`. That way the ocs uses the same nats instance as the proxy service.
+  -   When using the `nats-js-kv` store, it is possible to set `PROXY_PRESIGNEDURL_SIGNING_KEYS_STORE_DISABLE_PERSISTENCE` to instruct nats to not persist signing key data on disc.
+  -   When using `opencloudstoreservice` the `PROXY_PRESIGNEDURL_SIGNING_KEYS_STORE_NODES` must be set to the service name `eu.opencloud.api.store`. It does not support TTL and stores the presigning keys indefinitely. Also, the store service needs to be started.
+
+
+## Special Settings
+
+When using the OpenCloud IDP service instead of an external IDP:
+
+-   Use the environment variable `OC_URL` to define how OpenCloud can be accessed, mandatory use `https` as protocol for the URL.
+-   If no reverse proxy is set up, the `PROXY_TLS` environment variable **must** be set to `true` because the embedded `libreConnect` shipped with the IDP service has a hard check if the connection is on TLS and uses the HTTPS protocol. If this mismatches, an error will be logged and no connection from the client can be established.
+-   `PROXY_TLS` **can** be set to `false` if a reverse proxy is used and the https connection is terminated at the reverse proxy. When setting to `false`, the communication between the reverse proxy and OpenCloud is not secured. If set to `true`, you must provide certificates.
+
+## Metrics
+
+The proxy service in OpenCloud has the ability to expose metrics in the prometheus format. The metrics are exposed on the `/metrics` endpoint. There are two ways to run the OpenCloud proxy service which has an impact on the number of metrics exposed.
+
+### 1) Single Process Mode
+In the single process mode, all OpenCloud services are running inside a single process. This is the default mode when using the `opencloud server` command to start the services. In this mode, the proxy service exposes metrics about the proxy service itself and about the OpenCloud services it is proxying. This is due to the nature of the prometheus registry which is a singleton. The metrics exposed by the proxy service itself are prefixed with `opencloud_proxy_` and the metrics exposed by other opencloud services are prefixed with `opencloud_<service-name>_`.
+
+### 2) Standalone Mode
+In this mode, the proxy service only exposes its own metrics. The metrics of the other OpenCloud services are exposed on their own metrics endpoints.
+
+### Available Metrics
+The following metrics are exposed by the proxy service:
+
+| Metric Name                      | Description                                                                                                                                                                                                                   | Labels                                |
+|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|
+| `opencloud_proxy_requests_total`      | [Counter](https://prometheus.io/docs/tutorials/understanding_metric_types/#counter) metric which reports the total number of HTTP requests.                                                                                   | `method`: HTTP method of the request  |
+| `opencloud_proxy_errors_total`        | [Counter](https://prometheus.io/docs/tutorials/understanding_metric_types/#counter) metric which reports the total number of HTTP requests which have failed. That counts all response codes >= 500                           | `method`: HTTP method of the request  |
+| `opencloud_proxy_duration_seconds`    | [Histogram](https://prometheus.io/docs/tutorials/understanding_metric_types/#histogram) of the time (in seconds) each request took. A histogram metric uses buckets to count the number of events that fall into each bucket. | `method`: HTTP method of the request  |
+| `opencloud_proxy_build_info{version}` | A metric with a constant `1` value labeled by version, exposing the version of the OpenCloud proxy service.                                                                                                                        | `version`: Build version of the proxy |
+
+### Prometheus Configuration
+The following is an example prometheus configuration for the single process mode. It assumes that the proxy debug address is configured to bind on all interfaces `PROXY_DEBUG_ADDR=0.0.0.0:9205` and that the proxy is available via the `opencloud` service name (typically in docker-compose). The prometheus service detects the `/metrics` endpoint automatically and scrapes it every 15 seconds.
+
+```yaml
+global:
+  scrape_interval: 15s
+scrape_configs:
+  - job_name: opencloud_proxy
+    static_configs:
+    - targets: ["opencloud:9205"]
+```
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/search.yaml b/versioned_docs/version-7.x/_static/env-vars/search.yaml
new file mode 100644
index 000000000..8e6e5ab97
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/search.yaml
@@ -0,0 +1,69 @@
+# Autogenerated
+# Filename: search.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9224
+  token: ""
+  pprof: false
+  zpages: false
+grpc:
+  disabled: false
+  addr: 127.0.0.1:9220
+  tls: null
+token_manager:
+  jwt_secret: ""
+reva:
+  address: eu.opencloud.api.gateway
+  tls:
+    mode: ""
+    cacert: ""
+grpc_client_tls: null
+events:
+  disabled: false
+  endpoint: 127.0.0.1:9233
+  cluster: opencloud-cluster
+  async_uploads: true
+  num_consumers: 1
+  debounce_duration: 1000
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+  enable_tls: false
+  username: ""
+  password: ""
+  max_ack_pending: 1000
+  ack_wait: 1m0s
+engine:
+  type: bleve
+  bleve:
+    data_path: /var/lib/opencloud/search
+  open_search:
+    client:
+      addresses: []
+      username: ""
+      password: ""
+      header: {}
+      ca_cert: ""
+      retry_on_status: []
+      disable_retry: false
+      enable_retry_on_timeout: false
+      max_retries: 0
+      compress_request_body: false
+      discover_nodes_on_start: false
+      discover_nodes_interval: 0s
+      enable_metrics: false
+      enable_debug_logger: false
+      insecure: false
+    resource_index:
+      name: opencloud-resource
+extractor:
+  type: basic
+  cs3_allow_insecure: false
+  tika:
+    tika_url: http://127.0.0.1:9998
+    clean_stop_words: false
+content_extraction_size_limit: 20971520
+batch_size: 50
+service_account:
+  service_account_id: ""
+  service_account_secret: ""
diff --git a/versioned_docs/version-7.x/_static/env-vars/search_configvars.md b/versioned_docs/version-7.x/_static/env-vars/search_configvars.md
new file mode 100644
index 000000000..a26d53da5
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/search_configvars.md
@@ -0,0 +1,54 @@
+## Environment variables for the **search** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`SEARCH_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`SEARCH_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9224`|
+|`SEARCH_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`SEARCH_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`SEARCH_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`SEARCH_GRPC_DISABLED`| 4.0.0 |bool|`Disables the GRPC service. Set this to true if the service should only handle events.`|`false`|
+|`SEARCH_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9220`|
+|`OC_JWT_SECRET`<br/>`SEARCH_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`The CS3 gateway endpoint.`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
+|`SEARCH_EVENTS_DISABLED`| 4.0.0 |bool|`Disables listening for events. Set this to true if the service should only handle GRPC requests.`|`false`|
+|`OC_EVENTS_ENDPOINT`<br/>`SEARCH_EVENTS_ENDPOINT`| 1.0.0 |string|`The address of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture.`|`127.0.0.1:9233`|
+|`OC_EVENTS_CLUSTER`<br/>`SEARCH_EVENTS_CLUSTER`| 1.0.0 |string|`The clusterID of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture. Mandatory when using NATS as event system.`|`opencloud-cluster`|
+|`OC_ASYNC_UPLOADS`<br/>`SEARCH_EVENTS_ASYNC_UPLOADS`| 1.0.0 |bool|`Enable asynchronous file uploads.`|`true`|
+|`SEARCH_EVENTS_NUM_CONSUMERS`| 1.0.0 |int|`The amount of concurrent event consumers to start. Event consumers are used for searching files. Multiple consumers increase parallelisation, but will also increase CPU and memory demands.`|`1`|
+|`SEARCH_EVENTS_REINDEX_DEBOUNCE_DURATION`| 1.0.0 |int|`The duration in milliseconds the reindex debouncer waits before triggering a reindex of a space that was modified.`|`1000`|
+|`OC_INSECURE`<br/>`OC_EVENTS_TLS_INSECURE`<br/>`SEARCH_EVENTS_TLS_INSECURE`| 1.0.0 |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_EVENTS_TLS_ROOT_CA_CERTIFICATE`<br/>`SEARCH_EVENTS_TLS_ROOT_CA_CERTIFICATE`| 1.0.0 |string|`The root CA certificate used to validate the server's TLS certificate. If provided SEARCH_EVENTS_TLS_INSECURE will be seen as false.`|``|
+|`OC_EVENTS_ENABLE_TLS`<br/>`SEARCH_EVENTS_ENABLE_TLS`| 1.0.0 |bool|`Enable TLS for the connection to the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|`false`|
+|`OC_EVENTS_AUTH_USERNAME`<br/>`SEARCH_EVENTS_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_EVENTS_AUTH_PASSWORD`<br/>`SEARCH_EVENTS_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`SEARCH_EVENTS_MAX_ACK_PENDING`| 4.0.0 |int|`The maximum number of unacknowledged messages. This is used to limit the number of messages that can be in flight at the same time.`|`1000`|
+|`SEARCH_EVENTS_ACK_WAIT`| 4.0.0 |Duration|`The time to wait for an ack before the message is redelivered. This is used to ensure that messages are not lost if the consumer crashes.`|`1m0s`|
+|`SEARCH_ENGINE_TYPE`| 1.0.0 |string|`Defines which search engine to use. Defaults to 'bleve'. Supported values are: 'bleve'.`|`bleve`|
+|`SEARCH_ENGINE_BLEVE_DATA_PATH`| 1.0.0 |string|`The directory where the filesystem will store search data. If not defined, the root directory derives from $OC_BASE_DATA_PATH/search.`|`/var/lib/opencloud/search`|
+|`SEARCH_ENGINE_OPEN_SEARCH_CLIENT_ADDRESSES`| 4.0.0 |[]string|`The addresses of the OpenSearch nodes..`|`[]`|
+|`SEARCH_ENGINE_OPEN_SEARCH_CLIENT_USERNAME`| 4.0.0 |string|`Username for HTTP Basic Authentication.`|``|
+|`SEARCH_ENGINE_OPEN_SEARCH_CLIENT_PASSWORD`| 4.0.0 |string|`Password for HTTP Basic Authentication.`|``|
+|`SEARCH_ENGINE_OPEN_SEARCH_CLIENT_HEADER`| 4.0.0 |Header|`HTTP headers to include in requests.`|`map[]`|
+|`SEARCH_ENGINE_OPEN_SEARCH_CLIENT_CA_CERT`| 4.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the opensearch server.`|``|
+|`SEARCH_ENGINE_OPEN_SEARCH_CLIENT_RETRY_ON_STATUS`| 4.0.0 |[]int|`HTTP status codes that trigger a retry.`|`[]`|
+|`SEARCH_ENGINE_OPEN_SEARCH_CLIENT_DISABLE_RETRY`| 4.0.0 |bool|`Disable retries on errors.`|`false`|
+|`SEARCH_ENGINE_OPEN_SEARCH_CLIENT_ENABLE_RETRY_ON_TIMEOUT`| 4.0.0 |bool|`Enable retries on timeout.`|`false`|
+|`SEARCH_ENGINE_OPEN_SEARCH_CLIENT_MAX_RETRIES`| 4.0.0 |int|`Maximum number of retries for requests.`|`0`|
+|`SEARCH_ENGINE_OPEN_SEARCH_CLIENT_COMPRESS_REQUEST_BODY`| 4.0.0 |bool|`Compress request bodies.`|`false`|
+|`SEARCH_ENGINE_OPEN_SEARCH_CLIENT_DISCOVER_NODES_ON_START`| 4.0.0 |bool|`Discover nodes on service start.`|`false`|
+|`SEARCH_ENGINE_OPEN_SEARCH_CLIENT_DISCOVER_NODES_INTERVAL`| 4.0.0 |Duration|`Interval for discovering nodes.`|`0s`|
+|`SEARCH_ENGINE_OPEN_SEARCH_CLIENT_ENABLE_METRICS`| 4.0.0 |bool|`Enable metrics collection.`|`false`|
+|`SEARCH_ENGINE_OPEN_SEARCH_CLIENT_ENABLE_DEBUG_LOGGER`| 4.0.0 |bool|`Enable debug logging.`|`false`|
+|`SEARCH_ENGINE_OPEN_SEARCH_CLIENT_INSECURE`| 4.0.0 |bool|`Skip TLS certificate verification.`|`false`|
+|`SEARCH_ENGINE_OPEN_SEARCH_RESOURCE_INDEX_NAME`| 4.0.0 |string|`The name of the OpenSearch index for resources.`|`opencloud-resource`|
+|`SEARCH_EXTRACTOR_TYPE`| 1.0.0 |string|`Defines the content extraction engine. Defaults to 'basic'. Supported values are: 'basic' and 'tika'.`|`basic`|
+|`OC_INSECURE`<br/>`SEARCH_EXTRACTOR_CS3SOURCE_INSECURE`| 1.0.0 |bool|`Ignore untrusted SSL certificates when connecting to the CS3 source.`|`false`|
+|`SEARCH_EXTRACTOR_TIKA_TIKA_URL`| 1.0.0 |string|`URL of the tika server.`|`http://127.0.0.1:9998`|
+|`SEARCH_EXTRACTOR_TIKA_CLEAN_STOP_WORDS`| 1.0.0 |bool|`Defines if stop words should be cleaned or not. See the documentation for more details.`|`false`|
+|`SEARCH_CONTENT_EXTRACTION_SIZE_LIMIT`| 1.0.0 |uint64|`Maximum file size in bytes that is allowed for content extraction.`|`20971520`|
+|`SEARCH_BATCH_SIZE`| 1.0.0 |int|`The number of documents to process in a single batch. Defaults to 500.`|`50`|
+|`OC_SERVICE_ACCOUNT_ID`<br/>`SEARCH_SERVICE_ACCOUNT_ID`| 1.0.0 |string|`The ID of the service account the service should use. See the 'auth-service' service description for more details.`|``|
+|`OC_SERVICE_ACCOUNT_SECRET`<br/>`SEARCH_SERVICE_ACCOUNT_SECRET`| 1.0.0 |string|`The service account secret.`|``|
diff --git a/versioned_docs/version-7.x/_static/env-vars/search_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/search_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/search_readme.md b/versioned_docs/version-7.x/_static/env-vars/search_readme.md
new file mode 100755
index 000000000..20231c7da
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/search_readme.md
@@ -0,0 +1,156 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The search service is responsible for metadata and content extraction,
+the retrieved data is indexed and made searchable.
+
+The search service runs out of the box with the shipped default `basic` configuration.
+No further configuration is needed.
+
+Note that as of now, the search service cannot be scaled.
+Consider using dedicated hardware for this service in case more resources are needed.
+
+
+## Table of Contents
+
+* [Search backends](#search-backends)
+  * [Bleve](#bleve)
+  * [OpenSearch](#opensearch)
+* [Query language](#query-language)
+* [Content analysis / Extraction](#content-analysis--extraction)
+  * [Basic](#basic)
+  * [Tika](#tika)
+* [Manually Trigger Re-Indexing a Space](#manually-trigger-reindexing-a-space)
+* [Metrics](#metrics)
+
+## Search backends
+
+To store and query the indexed data, a search backend is needed.
+
+As of now, the search service supports the following backends:
+
+- [bleve](https://github.com/blevesearch/bleve) (default)
+- [opensearch](https://opensearch.org/)
+
+### Bleve
+
+Bleve is a lightweight, embedded full-text search engine written in Go and is the default search backend.
+It is straightforward to set up and requires no additional services to run.
+
+The following optional settings can be set:
+
+*   `SEARCH_ENGINE_BLEVE_DATA_PATH=/path/to/bleve/index` (default: `$OC_BASE_DATA_PATH/search`): Path to store the bleve index.
+
+### OpenSearch
+
+OpenSearch is a distributed, RESTful search and analytics engine capable of addressing a growing number of use cases.
+Additionally, it provides advanced features like clustering, replication, and sharding.
+
+To enable OpenSearch as a backend, the following settings must be set:
+
+*   `SEARCH_ENGINE_TYPE=open-search`
+*   `SEARCH_ENGINE_OPEN_SEARCH_CLIENT_ADDRESSES=http://YOUR-OPENSEARCH.URL:9200` (comma-separated list of OpenSearch addresses)
+
+Additionally, the following optional settings can be set:
+
+*   `SEARCH_ENGINE_OPEN_SEARCH_RESOURCE_INDEX_NAME=val` (default: `opencloud-resource`): Name of the OpenSearch index
+*   `SEARCH_ENGINE_OPEN_SEARCH_CLIENT_USERNAME=val`: Username for HTTP Basic Authentication.
+*   `SEARCH_ENGINE_OPEN_SEARCH_CLIENT_PASSWORD=val`: Password for HTTP Basic Authentication.
+*   `SEARCH_ENGINE_OPEN_SEARCH_CLIENT_HEADER=val`: HTTP headers to include in requests.
+*   `SEARCH_ENGINE_OPEN_SEARCH_CLIENT_CA_CERT=val` CA certificate for TLS connections.
+*   `SEARCH_ENGINE_OPEN_SEARCH_CLIENT_RETRY_ON_STATUS=val` HTTP status codes that trigger a retry.
+*   `SEARCH_ENGINE_OPEN_SEARCH_CLIENT_DISABLE_RETRY=val` Disable retries on errors.
+*   `SEARCH_ENGINE_OPEN_SEARCH_CLIENT_ENABLE_RETRY_ON_TIMEOUT=val`: Enable retries on timeout.
+*   `SEARCH_ENGINE_OPEN_SEARCH_CLIENT_MAX_RETRIES=val`: Maximum number of retries for requests.
+*   `SEARCH_ENGINE_OPEN_SEARCH_CLIENT_COMPRESS_REQUEST_BODY=val`: Compress request bodies.
+*   `SEARCH_ENGINE_OPEN_SEARCH_CLIENT_DISCOVER_NODES_ON_START=val`: Discover nodes on service start.
+*   `SEARCH_ENGINE_OPEN_SEARCH_CLIENT_DISCOVER_NODES_INTERVAL=val`: Interval for discovering nodes.
+*   `SEARCH_ENGINE_OPEN_SEARCH_CLIENT_ENABLE_METRICS=val`: Enable metrics collection.
+*   `SEARCH_ENGINE_OPEN_SEARCH_CLIENT_ENABLE_DEBUG_LOGGER=val`: Enable debug logging.
+*   `SEARCH_ENGINE_OPEN_SEARCH_CLIENT_INSECURE=val`: Skip TLS certificate verification.
+
+## Query language
+
+By default, [KQL](https://learn.microsoft.com/en-us/sharepoint/dev/general-development/keyword-query-language-kql-syntax-reference) is used as the query language.
+For an overview of how to write kql queries, please read the [microsoft documentation](https://learn.microsoft.com/en-us/sharepoint/dev/general-development/keyword-query-language-kql-syntax-reference).
+
+Not all parts are supported, the following list gives an overview of parts that are not implemented yet:
+
+*   Synonym operators
+*   Inclusion and exclusion operators
+*   Dynamic ranking operator
+*   ONEAR operator
+*   NEAR operator
+*   Date intervals
+
+In [this ADR](https://github.com/owncloud/ocis/blob/docs/ocis/adr/0020-file-search-query-language.md) you can read why KQL was chosen.
+
+## Content analysis / Extraction
+
+The search service supports the following content extraction methods:
+
+*   `Basic`: enabled by default, only provides metadata extraction.
+*   `Tika`: needs to be installed and configured separately, provides content extraction for many file types.
+
+Note that the file content has to be transferred to the search service internally for content extraction,
+which is resource-intensive and can lead to delays with larger documents.
+
+### Basic
+
+This extractor is the simplest one and just uses the resource information provided by OpenCloud.
+It does not do any further content analysis.
+
+### Tika
+
+The main difference is that this extractor is able to analyze and extract data from more advanced file types like PDF, DOCX, PPTX, etc.
+However, [Apache Tika](https://tika.apache.org/) is required for this task.
+Read the [Getting Started with Apache Tika](https://tika.apache.org/2.6.0/gettingstarted.html) guide on how to install and run Tika or use a ready to run [Tika container](https://hub.docker.com/r/apache/tika).
+See the [Tika container usage document](https://github.com/apache/tika-docker#usage) for a quickstart.
+
+As soon as Tika is installed and configured, the search service needs to be told to use it.
+
+The following settings must be set:
+
+*   `SEARCH_EXTRACTOR_TYPE=tika`
+*   `SEARCH_EXTRACTOR_TIKA_TIKA_URL=http://YOUR-TIKA.URL`
+
+Additionally, the following optional settings can be set:
+
+*   `SEARCH_EXTRACTOR_TIKA_CLEAN_STOP_WORDS=true` (default: `true`): ignore stop words like `I`, `you`, `the` during content extraction.
+
+## Manually Trigger Re-Indexing a Space
+
+The service includes a command-line interface to trigger re-indexing a space:
+
+```shell
+opencloud search index --space $SPACE_ID
+```
+
+It can also be used to re-index all spaces:
+
+```shell
+opencloud search index --all-spaces
+```
+
+Please note that a reindex only picks up new or changed files. Files that have already been indexed are not scanned again, even if the configuration or the whole extractor has been changed. To force a full rescan (re-running the extractor on every file) you need to use the `force-rescan` flag:
+
+
+```shell
+opencloud search index --all-spaces --force-rescan
+```
+
+## Metrics
+
+The search service exposes the following prometheus metrics at `<debug_endpoint>/metrics` (as configured using the `SEARCH_DEBUG_ADDR` env var):
+
+| Metric Name | Type | Description | Labels |
+| --- | --- | --- | --- |
+| `opencloud_search_build_info` | Gauge | Build information | `version` |
+| `opencloud_search_events_outstanding_acks` | Gauge | Number of outstanding acks for events | |
+| `opencloud_search_events_unprocessed` | Gauge | Number of unprocessed events | |
+| `opencloud_search_events_redelivered` | Gauge | Number of redelivered events | |
+| `opencloud_search_search_duration_seconds` | Histogram | Duration of search operations in seconds | `status` |
+| `opencloud_search_index_duration_seconds` | Histogram | Duration of indexing operations in seconds | `status` |
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/settings.yaml b/versioned_docs/version-7.x/_static/env-vars/settings.yaml
new file mode 100644
index 000000000..e53233d2d
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/settings.yaml
@@ -0,0 +1,67 @@
+# Autogenerated
+# Filename: settings.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9194
+  token: ""
+  pprof: false
+  zpages: false
+http:
+  addr: 127.0.0.1:9190
+  tls:
+    enabled: false
+    cert: ""
+    key: ""
+  root: /
+  cors:
+    allow_origins:
+    - '*'
+    allow_methods:
+    - GET
+    - POST
+    - PUT
+    - PATCH
+    - DELETE
+    - OPTIONS
+    allow_headers:
+    - Authorization
+    - Origin
+    - Content-Type
+    - Accept
+    - X-Requested-With
+    - X-Request-Id
+    allow_credentials: true
+grpc:
+  addr: 127.0.0.1:9191
+  tls: null
+grpc_client_tls: null
+metadata_config:
+  gateway_addr: eu.opencloud.api.storage-system
+  storage_addr: eu.opencloud.api.storage-system
+  system_user_id: ""
+  system_user_idp: internal
+  system_user_api_key: ""
+  cache:
+    store: memory
+    addresses:
+    - 127.0.0.1:9233
+    database: settings-cache
+    files_table: settings_files
+    directories_table: settings_dirs
+    ttl: 10m0s
+    disable_persistence: false
+    username: ""
+    password: ""
+    enable_tls: false
+    tls_insecure: false
+    tls_root_ca_certificate: ""
+bundles_path: ""
+admin_user_id: ""
+token_manager:
+  jwt_secret: ""
+set_default_assignments: false
+service_account_ids:
+- service-user-id
+default_language: ""
+translation_path: ""
diff --git a/versioned_docs/version-7.x/_static/env-vars/settings_configvars.md b/versioned_docs/version-7.x/_static/env-vars/settings_configvars.md
new file mode 100644
index 000000000..b252dcb33
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/settings_configvars.md
@@ -0,0 +1,43 @@
+## Environment variables for the **settings** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`SETTINGS_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`SETTINGS_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9194`|
+|`SETTINGS_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`SETTINGS_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`SETTINGS_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`SETTINGS_HTTP_ADDR`| 1.0.0 |string|`The bind address of the HTTP service.`|`127.0.0.1:9190`|
+|`OC_HTTP_TLS_ENABLED`| 1.0.0 |bool|`Activates TLS for the http based services using the server certifcate and key configured via OC_HTTP_TLS_CERTIFICATE and OC_HTTP_TLS_KEY. If OC_HTTP_TLS_CERTIFICATE is not set a temporary server certificate is generated - to be used with PROXY_INSECURE_BACKEND=true.`|`false`|
+|`OC_HTTP_TLS_CERTIFICATE`| 1.0.0 |string|`Path/File name of the TLS server certificate (in PEM format) for the http services.`|``|
+|`OC_HTTP_TLS_KEY`| 1.0.0 |string|`Path/File name for the TLS certificate key (in PEM format) for the server certificate to use for the http services.`|``|
+|`SETTINGS_HTTP_ROOT`| 1.0.0 |string|`Subdirectory that serves as the root for this HTTP service.`|`/`|
+|`OC_CORS_ALLOW_ORIGINS`<br/>`SETTINGS_CORS_ALLOW_ORIGINS`| 1.0.0 |[]string|`A list of allowed CORS origins. See following chapter for more details: *Access-Control-Allow-Origin* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin. See the Environment Variable Types description for more details.`|`[*]`|
+|`OC_CORS_ALLOW_METHODS`<br/>`SETTINGS_CORS_ALLOW_METHODS`| 1.0.0 |[]string|`A list of allowed CORS methods. See following chapter for more details: *Access-Control-Request-Method* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Method. See the Environment Variable Types description for more details.`|`[GET POST PUT PATCH DELETE OPTIONS]`|
+|`OC_CORS_ALLOW_HEADERS`<br/>`SETTINGS_CORS_ALLOW_HEADERS`| 1.0.0 |[]string|`A list of allowed CORS headers. See following chapter for more details: *Access-Control-Request-Headers* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Headers. See the Environment Variable Types description for more details.`|`[Authorization Origin Content-Type Accept X-Requested-With X-Request-Id]`|
+|`OC_CORS_ALLOW_CREDENTIALS`<br/>`SETTINGS_CORS_ALLOW_CREDENTIALS`| 1.0.0 |bool|`Allow credentials for CORS.See following chapter for more details: *Access-Control-Allow-Credentials* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Credentials.`|`true`|
+|`SETTINGS_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9191`|
+|`SETTINGS_STORAGE_GATEWAY_GRPC_ADDR`<br/>`STORAGE_GATEWAY_GRPC_ADDR`| 1.0.0 |string|`GRPC address of the STORAGE-SYSTEM service.`|`eu.opencloud.api.storage-system`|
+|`SETTINGS_STORAGE_GRPC_ADDR`<br/>`STORAGE_GRPC_ADDR`| 1.0.0 |string|`GRPC address of the STORAGE-SYSTEM service.`|`eu.opencloud.api.storage-system`|
+|`OC_SYSTEM_USER_ID`<br/>`SETTINGS_SYSTEM_USER_ID`| 1.0.0 |string|`ID of the OpenCloud STORAGE-SYSTEM system user. Admins need to set the ID for the STORAGE-SYSTEM system user in this config option which is then used to reference the user. Any reasonable long string is possible, preferably this would be an UUIDv4 format.`|``|
+|`OC_SYSTEM_USER_IDP`<br/>`SETTINGS_SYSTEM_USER_IDP`| 1.0.0 |string|`IDP of the OpenCloud STORAGE-SYSTEM system user.`|`internal`|
+|`OC_SYSTEM_USER_API_KEY`| 1.0.0 |string|`API key for the STORAGE-SYSTEM system user.`|``|
+|`OC_CACHE_STORE`<br/>`SETTINGS_CACHE_STORE`| 1.0.0 |string|`The type of the cache store. Supported values are: 'memory', 'redis-sentinel', 'nats-js-kv', 'noop'. See the text description for details.`|`memory`|
+|`OC_CACHE_STORE_NODES`<br/>`SETTINGS_CACHE_STORE_NODES`| 1.0.0 |[]string|`A list of nodes to access the configured store. This has no effect when 'memory' store is configured. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details.`|`[127.0.0.1:9233]`|
+|`OC_CACHE_DATABASE`| 1.0.0 |string|`The database name the configured store should use.`|`settings-cache`|
+|`SETTINGS_FILE_CACHE_TABLE`| 1.0.0 |string|`The database table the store should use for the file cache.`|`settings_files`|
+|`SETTINGS_DIRECTORY_CACHE_TABLE`| 1.0.0 |string|`The database table the store should use for the directory cache.`|`settings_dirs`|
+|`OC_CACHE_TTL`<br/>`SETTINGS_CACHE_TTL`| 1.0.0 |Duration|`Default time to live for entries in the cache. Only applied when access tokens has no expiration. See the Environment Variable Types description for more details.`|`10m0s`|
+|`OC_CACHE_DISABLE_PERSISTENCE`<br/>`SETTINGS_CACHE_DISABLE_PERSISTENCE`| 1.0.0 |bool|`Disables persistence of the cache. Only applies when store type 'nats-js-kv' is configured. Defaults to false.`|`false`|
+|`OC_CACHE_AUTH_USERNAME`<br/>`SETTINGS_CACHE_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the cache. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_CACHE_AUTH_PASSWORD`<br/>`SETTINGS_CACHE_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the cache. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_CACHE_ENABLE_TLS`<br/>`SETTINGS_CACHE_ENABLE_TLS`| next |bool|`Enable TLS for the connection to file metadata cache.`|`false`|
+|`OC_INSECURE`<br/>`OC_CACHE_TLS_INSECURE`<br/>`SETTINGS_CACHE_TLS_INSECURE`| next |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_CACHE_TLS_ROOT_CA_CERTIFICATE`<br/>`SETTINGS_CACHE_TLS_ROOT_CA_CERTIFICATE`| next |string|`The root CA certificate used to validate the server's TLS certificate. If provided SETTINGS_CACHE_TLS_INSECURE will be seen as false.`|``|
+|`SETTINGS_BUNDLES_PATH`| 1.0.0 |string|`The path to a JSON file with a list of bundles. If not defined, the default bundles will be loaded.`|``|
+|`OC_ADMIN_USER_ID`<br/>`SETTINGS_ADMIN_USER_ID`| 1.0.0 |string|`ID of the user that should receive admin privileges. Consider that the UUID can be encoded in some LDAP deployment configurations like in .ldif files. These need to be decoded beforehand.`|``|
+|`OC_JWT_SECRET`<br/>`SETTINGS_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`IDM_CREATE_DEMO_USERS`<br/>`SETTINGS_SETUP_DEFAULT_ASSIGNMENTS`| 1.0.0 |bool|`The default role assignments the demo users should be setup.`|`false`|
+|`SETTINGS_SERVICE_ACCOUNT_IDS`<br/>`OC_SERVICE_ACCOUNT_ID`| 1.0.0 |[]string|`The list of all service account IDs. These will be assigned the hidden 'service-account' role. Note: When using 'OC_SERVICE_ACCOUNT_ID' this will contain only one value while 'SETTINGS_SERVICE_ACCOUNT_IDS' can have multiple. See the 'auth-service' service description for more details about service accounts.`|`[service-user-id]`|
+|`OC_DEFAULT_LANGUAGE`| 1.0.0 |string|`The default language used by services and the WebUI. If not defined, English will be used as default. See the documentation for more details.`|``|
+|`OC_TRANSLATION_PATH`<br/>`SETTINGS_TRANSLATION_PATH`| 1.0.0 |string|`(optional) Set this to a path with custom translations to overwrite the builtin translations. Note that file and folder naming rules apply, see the documentation for more details.`|``|
diff --git a/versioned_docs/version-7.x/_static/env-vars/settings_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/settings_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/settings_readme.md b/versioned_docs/version-7.x/_static/env-vars/settings_readme.md
new file mode 100755
index 000000000..e48f9bc13
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/settings_readme.md
@@ -0,0 +1,468 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The `settings` service provides functionality for other services to register new settings as well as storing and retrieving the respective settings' values.
+
+
+## Table of Contents
+
+* [Settings Managed](#settings-managed)
+* [Caching](#caching)
+* [Settings Management](#settings-management)
+* [Settings Usage](#settings-usage)
+* [Service Accounts](#service-accounts)
+* [Translations](#translations)
+  * [Translation Rules](#translation-rules)
+* [Default Language](#default-language)
+* [Custom Roles](#custom-roles)
+
+## Settings Managed
+
+The settings service is currently used for managing the:
+
+*   users' `profile` settings like the language and the email notification settings,
+*   possible user roles and their respective permissions,
+*   assignment of roles to users.
+
+As an example, user profile settings that can be changed in the Web UI must be persistent.
+
+The settings service persists the settings data via the `storage-system` service.
+
+<!--- Note: The diagramm is outdate, leaving it here for a future rework
+The diagram shows how the settings service integrates into OpenCloud:
+
+The diagram shows how the settings service integrates into OpenCloud:
+
+```mermaid
+graph TD
+    ows ---|"listSettingsBundles(),<br>saveSettingsValue(value)"| os[opencloud-settings]
+    owc ---|"listSettingsValues()"| sdk[oC SDK]
+    sdk --- sdks{opencloud-settings<br>available?}
+    sdks ---|"yes"| os
+    sdks ---|"no"| defaults[Use set of<br>default values]
+    oa[OpenCloud services<br>e.g. opencloud-accounts] ---|"saveSettingsBundle(bundle)"| os
+```
+-->
+
+## Caching
+
+The `settings` service caches the results of queries against the storage backend to provide faster responses. The content of this cache is independent of the cache used in the `storage-system` service as it caches directory listing and settings content stored in files.
+
+The store used for the cache can be configured using the `SETTINGS_CACHE_STORE` environment variable. Possible stores are:
+  -   `memory`: Basic in-memory store and the default.
+  -   `redis-sentinel`: Stores data in a configured Redis Sentinel cluster.
+  -   `nats-js-kv`: Stores data using key-value-store feature of [nats jetstream](https://docs.nats.io/nats-concepts/jetstream/key-value-store)
+  -   `noop`: Stores nothing. Useful for testing. Not recommended in production environments.
+
+Other store types may work but are not supported currently.
+
+Note: The service can only be scaled if not using `memory` store and the stores are configured identically over all instances!
+
+
+Note that if you have used one of the deprecated stores, you should reconfigure to one of the supported ones as the deprecated stores will be removed in a later version.
+
+Store specific notes:
+  -   When using `redis-sentinel`, the Redis master to use is configured via e.g. `OC_CACHE_STORE_NODES` in the form of `<sentinel-host>:<sentinel-port>/<redis-master>` like `10.10.0.200:26379/mymaster`.
+  -   When using `nats-js-kv` it is recommended to set `OC_CACHE_STORE_NODES` to the same value as `OC_EVENTS_ENDPOINT`. That way the cache uses the same nats instance as the event bus.
+  -   When using the `nats-js-kv` store, it is possible to set `OC_CACHE_DISABLE_PERSISTENCE` to instruct nats to not persist cache data on disc.
+
+## Settings Management
+
+OpenCloud services can register *settings bundles* with the settings service.
+
+## Settings Usage
+
+Services can set or query OpenCloud *setting values* of a user from settings bundles.
+
+## Service Accounts
+
+The settings service needs to know the IDs of service accounts but it doesn't need their secrets. They can be configured using the `SETTINGS_SERVICE_ACCOUNTS_IDS` envvar. When only using one service account `OC_SERVICE_ACCOUNT_ID` can also be used. All configured service accounts will get a hidden 'service-account' role. This role contains all permissions the service account needs but will not appear calls to the list roles endpoint. It is not possible to assign the 'service-account' role to a normal user.
+
+## Translations
+
+The `settings` service has embedded translations sourced via transifex to provide a basic set of translated languages. These embedded translations are available for all deployment scenarios. In addition, the service supports custom translations, though it is currently not possible to just add custom translations to embedded ones. If custom translations are configured, the embedded ones are not used. To configure custom translations, the `SETTINGS_TRANSLATION_PATH` environment variable needs to point to a base folder that will contain the translation files. This path must be available from all instances of the userlog service, a shared storage is recommended. Translation files must be of type  [.po](https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html#PO-Files) or [.mo](https://www.gnu.org/software/gettext/manual/html_node/Binaries.html). For each language, the filename needs to be `settings.po` (or `settings.mo`) and stored in a folder structure defining the language code. In general the path/name pattern for a translation file needs to be:
+
+```text
+{SETTINGS_TRANSLATION_PATH}/{language-code}/LC_MESSAGES/settings.po
+```
+
+The language code pattern is composed of `language[_territory]` where  `language` is the base language and `_territory` is optional and defines a country.
+
+For example, for the language `de`, one needs to place the corresponding translation files to `{SETTINGS_TRANSLATION_PATH}/de_DE/LC_MESSAGES/settings.po`.
+
+<!-- also see the notifications readme -->
+
+Important: For the time being, the embedded OpenCloud Web frontend only supports the main language code but does not handle any territory. When strings are available in the language code `language_territory`, the web frontend does not see it as it only requests `language`. In consequence, any translations made must exist in the requested `language` to avoid a fallback to the default.
+
+### Translation Rules
+
+*   If a requested language code is not available, the service tries to fall back to the base language if available. For example, if the requested language-code `de_DE` is not available, the service tries to fall back to translations in the `de` folder.
+*   If the base language `de` is also not available, the service falls back to the system's default English (`en`),
+which is the source of the texts provided by the code.
+
+## Default Language
+
+The default language can be defined via the `OC_DEFAULT_LANGUAGE` environment variable. If this variable is not defined, English will be used as default. The value has the ISO 639-1 format ("de", "en", etc.) and is limited by the list supported languages. This setting can be used to set the default language for notification and invitation emails.
+
+Important developer note: the list of supported languages is at the moment not easy defineable, as it is the minimum intersection of languages shown in the WebUI and languages defined in the OpenCloud code for the use of notifications and userlog. Even more, not all languages where there are translations available on transifex, are available in the WebUI respectively for OpenCloud notifications, and the translation rate for existing languages is partially not that high. You will see therefore quite often English default strings though a supported language may exist and was selected.
+
+The `OC_DEFAULT_LANGUAGE` setting impacts the `notification` and `userlog` services and the WebUI. Note that translations must exist for all named components to be presented correctly.
+
+*   If  `OC_DEFAULT_LANGUAGE` **is not set**, the expected behavior is:
+    *   The `notification` and `userlog` services and the WebUI use English by default until a user sets another language in the WebUI via _Account -> Language_.
+    *    If a user sets another language in the WebUI in _Account -> Language_, then the `notification` and `userlog` services and WebUI use the language defined by the user. If no translation is found, it falls back to English.
+
+*   If  `OC_DEFAULT_LANGUAGE` **is set**, the expected behavior is:
+    *   The `notification` and `userlog` services and the WebUI use `OC_DEFAULT_LANGUAGE`  by default until a user sets another language in the WebUI via _Account -> Language_.
+    *   If a user sets another language in the WebUI in _Account -> Language_, the `notification` and `userlog` services and WebUI use the language defined by the user. If no translation is found, it falls back to `OC_DEFAULT_LANGUAGE` and then to English.
+
+## Custom Roles
+
+It is possible to replace the default OpenCloud roles (`admin`, `user`) with custom roles that contain custom permissions. One can set `SETTINGS_BUNDLES_PATH` to the path of a `json` file containing the new roles.
+
+Role Example:
+```json
+[
+    {
+        "id": "38071a68-456a-4553-846a-fa67bf5596cc", // ID of the role. Recommendation is to use a random uuidv4. But any unique string will do.
+        "name": "user-light",                         // Internal name of the role. This is used by the system to identify the role. Any string will do here, but it should be unique among the other roles.
+        "type": "TYPE_ROLE",                          // Always use `TYPE_ROLE`
+        "extension": "opencloud-roles",               // Always use `opencloud-roles`
+        "displayName": "User Light",                  // DisplayName of the role used in webui
+        "settings": [
+        ],                                            // Permissions attached to the role. See Details below.
+        "resource": {
+            "type": "TYPE_SYSTEM"                     // Always use `TYPE_SYSTEM`
+        }
+    }
+]
+```
+
+To create custom roles:
+* Copy the role example to a `json` file.
+* Change `id`, `name`, and `displayName` to your liking.
+* Copy the desired permissions from the `user-all-permissions` example below to the `settings` array of the role.
+* Set the `SETTINGS_BUNDLE_PATH` envvar to the path of the json file and start OpenCloud
+
+Example File:
+```json
+[
+    {
+        "id": "38071a68-456a-4553-846a-fa67bf5596cc",
+        "name": "user-1-permission",
+        "type": "TYPE_ROLE",
+        "extension": "opencloud-roles",
+        "displayName": "User with one permission only",
+        "settings": [
+            {
+                "id": "7d81f103-0488-4853-bce5-98dcce36d649",
+                "name": "Language.ReadWrite",
+                "displayName": "Permission to read and set the language",
+                "permissionValue": {
+                    "operation": "OPERATION_READWRITE",
+                    "constraint": "CONSTRAINT_OWN"
+                },
+                "resource": {
+                    "type": "TYPE_SETTING",
+                    "id": "aa8cfbe5-95d4-4f7e-a032-c3c01f5f062f"
+                }
+            }
+        ],
+        "resource": {
+            "type": "TYPE_SYSTEM"
+        }
+    },
+    {
+        "id": "71881883-1768-46bd-a24d-a356a2afdf7f",
+        "name": "user-all-permissions",
+        "type": "TYPE_ROLE",
+        "extension": "opencloud-roles",
+        "displayName": "User with all available permissions",
+        "settings": [
+            {
+                "id": "8e587774-d929-4215-910b-a317b1e80f73",
+                "name": "Accounts.ReadWrite",
+                "displayName": "Account Management",
+                "description": "This permission gives full access to everything that is related to account management.",
+                "permissionValue": {
+                    "operation": "OPERATION_READWRITE",
+                    "constraint": "CONSTRAINT_ALL"
+                },
+                "resource": {
+                    "type": "TYPE_USER",
+                    "id": "all"
+                }
+            },
+            {
+                "id": "4e41363c-a058-40a5-aec8-958897511209",
+                "name": "AutoAcceptShares.ReadWriteDisabled",
+                "displayName": "enable/disable auto accept shares",
+                "permissionValue": {
+                    "operation": "OPERATION_READWRITE",
+                    "constraint": "CONSTRAINT_OWN"
+                },
+                "resource": {
+                    "type": "TYPE_SETTING",
+                    "id": "ec3ed4a3-3946-4efc-8f9f-76d38b12d3a9"
+                }
+            },
+            {
+                "id": "ed83fc10-1f54-4a9e-b5a7-fb517f5f3e01",
+                "name": "Logo.Write",
+                "displayName": "Change logo",
+                "description": "This permission permits to change the system logo.",
+                "permissionValue": {
+                    "operation": "OPERATION_READWRITE",
+                    "constraint": "CONSTRAINT_ALL"
+                },
+                "resource": {
+                    "type": "TYPE_SYSTEM"
+                }
+            },
+            {
+                "id": "11516bbd-7157-49e1-b6ac-d00c820f980b",
+                "name": "PublicLink.Write",
+                "displayName": "Write publiclink",
+                "description": "This permission allows creating public links.",
+                "permissionValue": {
+                    "operation": "OPERATION_WRITE",
+                    "constraint": "CONSTRAINT_ALL"
+                },
+                "resource": {
+                    "type": "TYPE_SHARE"
+                }
+            },
+            {
+                "id": "069c08b1-e31f-4799-9ed6-194b310e7244",
+                "name": "Shares.Write",
+                "displayName": "Write share",
+                "description": "This permission allows creating shares.",
+                "permissionValue": {
+                    "operation": "OPERATION_WRITE",
+                    "constraint": "CONSTRAINT_ALL"
+                },
+                "resource": {
+                    "type": "TYPE_SHARE"
+                }
+            },
+            {
+                "id": "79e13b30-3e22-11eb-bc51-0b9f0bad9a58",
+                "name": "Drives.Create",
+                "displayName": "Create Space",
+                "description": "This permission allows creating new spaces.",
+                "permissionValue": {
+                    "operation": "OPERATION_READWRITE",
+                    "constraint": "CONSTRAINT_ALL"
+                },
+                "resource": {
+                    "type": "TYPE_SYSTEM"
+                }
+            },
+            {
+                "id": "5de9fe0a-4bc5-4a47-b758-28f370caf169",
+                "name": "Drives.DeletePersonal",
+                "displayName": "Delete All Home Spaces",
+                "description": "This permission allows deleting home spaces.",
+                "permissionValue": {
+                    "operation": "OPERATION_DELETE",
+                    "constraint": "CONSTRAINT_ALL"
+                },
+                "resource": {
+                    "type": "TYPE_SYSTEM"
+                }
+            },
+            {
+                "id": "fb60b004-c1fa-4f09-bf87-55ce7d46ac61",
+                "name": "Drives.DeleteProject",
+                "displayName": "Delete AllSpaces",
+                "description": "This permission allows deleting all spaces.",
+                "permissionValue": {
+                    "operation": "OPERATION_DELETE",
+                    "constraint": "CONSTRAINT_ALL"
+                },
+                "resource": {
+                    "type": "TYPE_SYSTEM"
+                }
+            },
+            {
+                "id": "e9a697c5-c67b-40fc-982b-bcf628e9916d",
+                "name": "ReadOnlyPublicLinkPassword.Delete",
+                "displayName": "Delete Read-Only Public link password",
+                "description": "This permission permits to opt out of a public link password enforcement.",
+                "permissionValue": {
+                    "operation": "OPERATION_WRITE",
+                    "constraint": "CONSTRAINT_ALL"
+                },
+                "resource": {
+                    "type": "TYPE_SHARE"
+                }
+            },
+            {
+                "id": "ad5bb5e5-dc13-4cd3-9304-09a424564ea8",
+                "name": "EmailNotifications.ReadWriteDisabled",
+                "displayName": "Disable Email Notifications",
+                "permissionValue": {
+                    "operation": "OPERATION_READWRITE",
+                    "constraint": "CONSTRAINT_OWN"
+                },
+                "resource": {
+                    "type": "TYPE_SETTING",
+                    "id": "33ffb5d6-cd07-4dc0-afb0-84f7559ae438"
+                }
+            },
+            {
+                "id": "522adfbe-5908-45b4-b135-41979de73245",
+                "name": "Groups.ReadWrite",
+                "displayName": "Group Management",
+                "description": "This permission gives full access to everything that is related to group management.",
+                "permissionValue": {
+                    "operation": "OPERATION_READWRITE",
+                    "constraint": "CONSTRAINT_ALL"
+                },
+                "resource": {
+                    "type": "TYPE_GROUP",
+                    "id": "all"
+                }
+            },
+            {
+                "id": "7d81f103-0488-4853-bce5-98dcce36d649",
+                "name": "Language.ReadWrite",
+                "displayName": "Permission to read and set the language",
+                "permissionValue": {
+                    "operation": "OPERATION_READWRITE",
+                    "constraint": "CONSTRAINT_ALL"
+                },
+                "resource": {
+                    "type": "TYPE_SETTING",
+                    "id": "aa8cfbe5-95d4-4f7e-a032-c3c01f5f062f"
+                }
+            },
+            {
+                "id": "4ebaa725-bfaa-43c5-9817-78bc9994bde4",
+                "name": "Favorites.List",
+                "displayName": "List Favorites",
+                "description": "This permission allows listing favorites.",
+                "permissionValue": {
+                    "operation": "OPERATION_READ",
+                    "constraint": "CONSTRAINT_OWN"
+                },
+                "resource": {
+                    "type": "TYPE_SYSTEM"
+                }
+            },
+            {
+                "id": "016f6ddd-9501-4a0a-8ebe-64a20ee8ec82",
+                "name": "Drives.List",
+                "displayName": "List All Spaces",
+                "description": "This permission allows listing all spaces.",
+                "permissionValue": {
+                    "operation": "OPERATION_READ",
+                    "constraint": "CONSTRAINT_ALL"
+                },
+                "resource": {
+                    "type": "TYPE_SYSTEM"
+                }
+            },
+            {
+                "id": "b44b4054-31a2-42b8-bb71-968b15cfbd4f",
+                "name": "Drives.ReadWrite",
+                "displayName": "Manage space properties",
+                "description": "This permission allows managing space properties such as name and description.",
+                "permissionValue": {
+                    "operation": "OPERATION_READWRITE",
+                    "constraint": "CONSTRAINT_ALL"
+                },
+                "resource": {
+                    "type": "TYPE_SYSTEM"
+                }
+            },
+            {
+                "id": "a53e601e-571f-4f86-8fec-d4576ef49c62",
+                "name": "Roles.ReadWrite",
+                "displayName": "Role Management",
+                "description": "This permission gives full access to everything that is related to role management.",
+                "permissionValue": {
+                    "operation": "OPERATION_READWRITE",
+                    "constraint": "CONSTRAINT_ALL"
+                },
+                "resource": {
+                    "type": "TYPE_USER",
+                    "id": "all"
+                }
+            },
+            {
+                "id": "4e6f9709-f9e7-44f1-95d4-b762d27b7896",
+                "name": "Drives.ReadWritePersonalQuota",
+                "displayName": "Set Personal Space Quota",
+                "description": "This permission allows managing personal space quotas.",
+                "permissionValue": {
+                    "operation": "OPERATION_READWRITE",
+                    "constraint": "CONSTRAINT_ALL"
+                },
+                "resource": {
+                    "type": "TYPE_SYSTEM"
+                }
+            },
+            {
+                "id": "977f0ae6-0da2-4856-93f3-22e0a8482489",
+                "name": "Drives.ReadWriteProjectQuota",
+                "displayName": "Set Project Space Quota",
+                "description": "This permission allows managing project space quotas.",
+                "permissionValue": {
+                    "operation": "OPERATION_READWRITE",
+                    "constraint": "CONSTRAINT_ALL"
+                },
+                "resource": {
+                    "type": "TYPE_SYSTEM"
+                }
+            },
+            {
+                "id": "3d58f441-4a05-42f8-9411-ef5874528ae1",
+                "name": "Settings.ReadWrite",
+                "displayName": "Settings Management",
+                "description": "This permission gives full access to everything that is related to settings management.",
+                "permissionValue": {
+                    "operation": "OPERATION_READWRITE",
+                    "constraint": "CONSTRAINT_ALL"
+                },
+                "resource": {
+                    "type": "TYPE_USER",
+                    "id": "all"
+                }
+            },
+            {
+                "id": "cf3faa8c-50d9-4f84-9650-ff9faf21aa9d",
+                "name": "Drives.ReadWriteEnabled",
+                "displayName": "Space ability",
+                "description": "This permission allows enabling and disabling spaces.",
+                "permissionValue": {
+                    "operation": "OPERATION_READWRITE",
+                    "constraint": "CONSTRAINT_ALL"
+                },
+                "resource": {
+                    "type": "TYPE_SYSTEM"
+                }
+            },
+            {
+                "id": "a54778fd-1c45-47f0-892d-655caf5236f2",
+                "name": "Favorites.Write",
+                "displayName": "Write Favorites",
+                "description": "This permission allows marking files as favorites.",
+                "permissionValue": {
+                    "operation": "OPERATION_WRITE",
+                    "constraint": "CONSTRAINT_OWN"
+                },
+                "resource": {
+                    "type": "TYPE_FILE"
+                }
+            }
+        ],
+        "resource": {
+            "type": "TYPE_SYSTEM"
+        }
+    }
+]
+```
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/sharing.yaml b/versioned_docs/version-7.x/_static/env-vars/sharing.yaml
new file mode 100644
index 000000000..5c99825aa
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/sharing.yaml
@@ -0,0 +1,79 @@
+# Autogenerated
+# Filename: sharing.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9151
+  token: ""
+  pprof: false
+  zpages: false
+grpc:
+  addr: 127.0.0.1:9150
+  tls: null
+  protocol: tcp
+token_manager:
+  jwt_secret: ""
+reva:
+  address: eu.opencloud.api.gateway
+  tls:
+    mode: ""
+    cacert: ""
+events:
+  endpoint: 127.0.0.1:9233
+  cluster: opencloud-cluster
+  tls_insecure: false
+  tls_root_ca_cert_path: ""
+  enable_tls: false
+  auth_username: ""
+  auth_password: ""
+service_account:
+  service_account_id: ""
+  service_account_secret: ""
+skip_user_groups_in_token: false
+user_sharing_driver: jsoncs3
+user_sharing_drivers:
+  jsoncs3:
+    provider_addr: eu.opencloud.api.storage-system
+    system_user_id: ""
+    system_user_idp: internal
+    system_user_api_key: ""
+    cache_ttl: 0
+    max_concurrency: 1
+  json:
+    file: /var/lib/opencloud/storage/shares.json
+  cs3:
+    provider_addr: eu.opencloud.api.storage-system
+    system_user_id: ""
+    system_user_idp: internal
+    system_user_api_key: ""
+  owncloudsql:
+    db_username: owncloud
+    db_password: ""
+    db_host: mysql
+    db_port: 3306
+    db_name: owncloud
+    user_storage_mount_id: ""
+public_sharing_driver: jsoncs3
+public_sharing_drivers:
+  json:
+    file: /var/lib/opencloud/storage/publicshares.json
+  jsoncs3:
+    provider_addr: eu.opencloud.api.storage-system
+    system_user_id: ""
+    system_user_idp: internal
+    system_user_api_key: ""
+  cs3:
+    provider_addr: eu.opencloud.api.storage-system
+    system_user_id: ""
+    system_user_idp: internal
+    system_user_api_key: ""
+public_sharing_writeableshare_must_have_password: false
+public_sharing_share_must_have_password: true
+enable_expired_shares_cleanup: true
+password_policy:
+  min_characters: 8
+  min_lowercase_characters: 1
+  min_uppercase_characters: 1
+  min_digits: 1
+  min_special_characters: 1
+  banned_passwords_list: ""
diff --git a/versioned_docs/version-7.x/_static/env-vars/sharing_configvars.md b/versioned_docs/version-7.x/_static/env-vars/sharing_configvars.md
new file mode 100644
index 000000000..5b778c65b
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/sharing_configvars.md
@@ -0,0 +1,62 @@
+## Environment variables for the **sharing** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`SHARING_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`SHARING_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9151`|
+|`SHARING_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`SHARING_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`SHARING_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`SHARING_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9150`|
+|`OC_GRPC_PROTOCOL`<br/>`SHARING_GRPC_PROTOCOL`| 1.0.0 |string|`The transport protocol of the GRPC service.`|`tcp`|
+|`OC_JWT_SECRET`<br/>`SHARING_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`The CS3 gateway endpoint.`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
+|`OC_EVENTS_ENDPOINT`<br/>`SHARING_EVENTS_ENDPOINT`| 1.0.0 |string|`The address of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture.`|`127.0.0.1:9233`|
+|`OC_EVENTS_CLUSTER`<br/>`SHARING_EVENTS_CLUSTER`| 1.0.0 |string|`The clusterID of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture. Mandatory when using NATS as event system.`|`opencloud-cluster`|
+|`OC_INSECURE`<br/>`OC_EVENTS_TLS_INSECURE`<br/>`SHARING_EVENTS_TLS_INSECURE`| 1.0.0 |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_EVENTS_TLS_ROOT_CA_CERTIFICATE`<br/>`SHARING_EVENTS_TLS_ROOT_CA_CERTIFICATE`| 1.0.0 |string|`The root CA certificate used to validate the server's TLS certificate. If provided SHARING_EVENTS_TLS_INSECURE will be seen as false.`|``|
+|`OC_EVENTS_ENABLE_TLS`<br/>`SHARING_EVENTS_ENABLE_TLS`| 1.0.0 |bool|`Enable TLS for the connection to the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|`false`|
+|`OC_EVENTS_AUTH_USERNAME`<br/>`SHARING_EVENTS_AUTH_USERNAME`| 1.0.0 |string|`Username for the events broker.`|``|
+|`OC_EVENTS_AUTH_PASSWORD`<br/>`SHARING_EVENTS_AUTH_PASSWORD`| 1.0.0 |string|`Password for the events broker.`|``|
+|`OC_SERVICE_ACCOUNT_ID`<br/>`SHARING_SERVICE_ACCOUNT`| 7.0.0 |string|`The ID of the service account the service should use. See the 'auth-service' service description for more details.`|``|
+|`OC_SERVICE_ACCOUNT_SECRET`<br/>`SHARING_SERVICE_ACCOUNT_SECRET`| 7.0.0 |string|`The service account secret.`|``|
+|`SHARING_SKIP_USER_GROUPS_IN_TOKEN`| 1.0.0 |bool|`Disables the loading of user's group memberships from the reva access token.`|`false`|
+|`SHARING_USER_DRIVER`| 1.0.0 |string|`Driver to be used to persist shares. Supported values are 'jsoncs3', 'json', 'cs3' (deprecated) and 'owncloudsql'.`|`jsoncs3`|
+|`SHARING_USER_JSONCS3_PROVIDER_ADDR`| 1.0.0 |string|`GRPC address of the STORAGE-SYSTEM service.`|`eu.opencloud.api.storage-system`|
+|`OC_SYSTEM_USER_ID`<br/>`SHARING_USER_JSONCS3_SYSTEM_USER_ID`| 1.0.0 |string|`ID of the OpenCloud STORAGE-SYSTEM system user. Admins need to set the ID for the STORAGE-SYSTEM system user in this config option which is then used to reference the user. Any reasonable long string is possible, preferably this would be an UUIDv4 format.`|``|
+|`OC_SYSTEM_USER_IDP`<br/>`SHARING_USER_JSONCS3_SYSTEM_USER_IDP`| 1.0.0 |string|`IDP of the OpenCloud STORAGE-SYSTEM system user.`|`internal`|
+|`OC_SYSTEM_USER_API_KEY`<br/>`SHARING_USER_JSONCS3_SYSTEM_USER_API_KEY`| 1.0.0 |string|`API key for the STORAGE-SYSTEM system user.`|``|
+|`SHARING_USER_JSONCS3_CACHE_TTL`| 1.0.0 |int|`TTL for the internal caches in seconds.`|`0`|
+|`OC_MAX_CONCURRENCY`<br/>`SHARING_USER_JSONCS3_MAX_CONCURRENCY`| 1.0.0 |int|`Maximum number of concurrent go-routines. Higher values can potentially get work done faster but will also cause more load on the system. Values of 0 or below will be ignored and the default value will be used.`|`1`|
+|`SHARING_USER_JSON_FILE`| 1.0.0 |string|`Path to the JSON file where shares will be persisted. If not defined, the root directory derives from $OC_BASE_DATA_PATH/storage.`|`/var/lib/opencloud/storage/shares.json`|
+|`SHARING_USER_CS3_PROVIDER_ADDR`| 1.0.0 |string|`GRPC address of the STORAGE-SYSTEM service.`|`eu.opencloud.api.storage-system`|
+|`OC_SYSTEM_USER_ID`<br/>`SHARING_USER_CS3_SYSTEM_USER_ID`| 1.0.0 |string|`ID of the OpenCloud STORAGE-SYSTEM system user. Admins need to set the ID for the STORAGE-SYSTEM system user in this config option which is then used to reference the user. Any reasonable long string is possible, preferably this would be an UUIDv4 format.`|``|
+|`OC_SYSTEM_USER_IDP`<br/>`SHARING_USER_CS3_SYSTEM_USER_IDP`| 1.0.0 |string|`IDP of the OpenCloud STORAGE-SYSTEM system user.`|`internal`|
+|`OC_SYSTEM_USER_API_KEY`<br/>`SHARING_USER_CS3_SYSTEM_USER_API_KEY`| 1.0.0 |string|`API key for the STORAGE-SYSTEM system user.`|``|
+|`SHARING_USER_OWNCLOUDSQL_DB_USERNAME`| 1.0.0 |string|`Username for the database.`|`owncloud`|
+|`SHARING_USER_OWNCLOUDSQL_DB_PASSWORD`| 1.0.0 |string|`Password for the database.`|``|
+|`SHARING_USER_OWNCLOUDSQL_DB_HOST`| 1.0.0 |string|`Hostname or IP of the database server.`|`mysql`|
+|`SHARING_USER_OWNCLOUDSQL_DB_PORT`| 1.0.0 |int|`Port that the database server is listening on.`|`3306`|
+|`SHARING_USER_OWNCLOUDSQL_DB_NAME`| 1.0.0 |string|`Name of the database to be used.`|`owncloud`|
+|`SHARING_USER_OWNCLOUDSQL_USER_STORAGE_MOUNT_ID`| 1.0.0 |string|`Mount ID of the ownCloudSQL users storage for mapping ownCloud 10 shares.`|``|
+|`SHARING_PUBLIC_DRIVER`| 1.0.0 |string|`Driver to be used to persist public shares. Supported values are 'jsoncs3', 'json' and 'cs3' (deprecated).`|`jsoncs3`|
+|`SHARING_PUBLIC_JSON_FILE`| 1.0.0 |string|`Path to the JSON file where public share meta-data will be stored. This JSON file contains the information about public shares that have been created. If not defined, the root directory derives from $OC_BASE_DATA_PATH/storage.`|`/var/lib/opencloud/storage/publicshares.json`|
+|`SHARING_PUBLIC_JSONCS3_PROVIDER_ADDR`| 1.0.0 |string|`GRPC address of the STORAGE-SYSTEM service.`|`eu.opencloud.api.storage-system`|
+|`OC_SYSTEM_USER_ID`<br/>`SHARING_PUBLIC_JSONCS3_SYSTEM_USER_ID`| 1.0.0 |string|`ID of the OpenCloud STORAGE-SYSTEM system user. Admins need to set the ID for the STORAGE-SYSTEM system user in this config option which is then used to reference the user. Any reasonable long string is possible, preferably this would be an UUIDv4 format.`|``|
+|`OC_SYSTEM_USER_IDP`<br/>`SHARING_PUBLIC_JSONCS3_SYSTEM_USER_IDP`| 1.0.0 |string|`IDP of the OpenCloud STORAGE-SYSTEM system user.`|`internal`|
+|`OC_SYSTEM_USER_API_KEY`<br/>`SHARING_PUBLIC_JSONCS3_SYSTEM_USER_API_KEY`| 1.0.0 |string|`API key for the STORAGE-SYSTEM system user.`|``|
+|`SHARING_PUBLIC_CS3_PROVIDER_ADDR`| 1.0.0 |string|`GRPC address of the STORAGE-SYSTEM service.`|`eu.opencloud.api.storage-system`|
+|`OC_SYSTEM_USER_ID`<br/>`SHARING_PUBLIC_CS3_SYSTEM_USER_ID`| 1.0.0 |string|`ID of the OpenCloud STORAGE-SYSTEM system user. Admins need to set the ID for the STORAGE-SYSTEM system user in this config option which is then used to reference the user. Any reasonable long string is possible, preferably this would be an UUIDv4 format.`|``|
+|`OC_SYSTEM_USER_IDP`<br/>`SHARING_PUBLIC_CS3_SYSTEM_USER_IDP`| 1.0.0 |string|`IDP of the OpenCloud STORAGE-SYSTEM system user.`|`internal`|
+|`OC_SYSTEM_USER_API_KEY`<br/>`SHARING_PUBLIC_CS3_SYSTEM_USER_API_KEY`| 1.0.0 |string|`API key for the STORAGE-SYSTEM system user.`|``|
+|`OC_SHARING_PUBLIC_WRITEABLE_SHARE_MUST_HAVE_PASSWORD`<br/>`SHARING_PUBLIC_WRITEABLE_SHARE_MUST_HAVE_PASSWORD`| 1.0.0 |bool|`Set this to true if you want to enforce passwords on Uploader, Editor or Contributor shares. If not using the global OC_SHARING_PUBLIC_WRITEABLE_SHARE_MUST_HAVE_PASSWORD, you must define the FRONTEND_OCS_PUBLIC_WRITEABLE_SHARE_MUST_HAVE_PASSWORD (deprecated) in the frontend service.`|`false`|
+|`OC_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD`<br/>`SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD`| 1.0.0 |bool|`Set this to true if you want to enforce passwords on all public shares.`|`true`|
+|`OC_PASSWORD_POLICY_DISABLED`<br/>`SHARING_PASSWORD_POLICY_DISABLED`| 1.0.0 |bool|`Disable the password policy. Defaults to false if not set.`|`false`|
+|`OC_PASSWORD_POLICY_MIN_CHARACTERS`<br/>`SHARING_PASSWORD_POLICY_MIN_CHARACTERS`| 1.0.0 |int|`Define the minimum password length. Defaults to 8 if not set.`|`8`|
+|`OC_PASSWORD_POLICY_MIN_LOWERCASE_CHARACTERS`<br/>`SHARING_PASSWORD_POLICY_MIN_LOWERCASE_CHARACTERS`| 1.0.0 |int|`Define the minimum number of uppercase letters. Defaults to 1 if not set.`|`1`|
+|`OC_PASSWORD_POLICY_MIN_UPPERCASE_CHARACTERS`<br/>`SHARING_PASSWORD_POLICY_MIN_UPPERCASE_CHARACTERS`| 1.0.0 |int|`Define the minimum number of lowercase letters. Defaults to 1 if not set.`|`1`|
+|`OC_PASSWORD_POLICY_MIN_DIGITS`<br/>`SHARING_PASSWORD_POLICY_MIN_DIGITS`| 1.0.0 |int|`Define the minimum number of digits. Defaults to 1 if not set.`|`1`|
+|`OC_PASSWORD_POLICY_MIN_SPECIAL_CHARACTERS`<br/>`SHARING_PASSWORD_POLICY_MIN_SPECIAL_CHARACTERS`| 1.0.0 |int|`Define the minimum number of characters from the special characters list to be present. Defaults to 1 if not set.`|`1`|
+|`OC_PASSWORD_POLICY_BANNED_PASSWORDS_LIST`<br/>`SHARING_PASSWORD_POLICY_BANNED_PASSWORDS_LIST`| 1.0.0 |string|`Path to the 'banned passwords list' file. This only impacts public link password validation. See the documentation for more details.`|``|
diff --git a/versioned_docs/version-7.x/_static/env-vars/sharing_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/sharing_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/sharing_readme.md b/versioned_docs/version-7.x/_static/env-vars/sharing_readme.md
new file mode 100755
index 000000000..d9409b5f6
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/sharing_readme.md
@@ -0,0 +1,55 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The `sharing` service provides the CS3 Sharing API for OpenCloud. It manages user shares and public link shares, implementing the core sharing functionality.
+
+
+## Table of Contents
+
+* [Overview](#overview)
+* [Integration](#integration)
+* [Share Types](#share-types)
+* [Configuration](#configuration)
+* [Scalability](#scalability)
+
+## Overview
+
+The sharing service handles:
+- User-to-user shares (share a file or folder with another user)
+- Public link shares (share via a public URL)
+- Share permissions and roles
+- Share lifecycle management (create, update, delete)
+
+This service works in conjunction with the storage providers (`storage-shares` and `storage-publiclink`) to persist and manage share information.
+
+## Integration
+
+The sharing service integrates with:
+- `frontend` and `ocs` - Provide HTTP APIs that translate to CS3 sharing calls
+- `storage-shares` - Stores and manages received shares
+- `storage-publiclink` - Manages public link shares
+- `graph` - Provides LibreGraph API for sharing with roles
+
+## Share Types
+
+The service supports different types of shares:
+- **User shares** - Share resources with specific users
+- **Group shares** - Share resources with groups
+- **Public link shares** - Create public URLs for sharing
+- **Federated shares** - Share with users on other OpenCloud instances (via `ocm` service)
+
+## Configuration
+
+Share behavior can be configured via environment variables:
+- Password enforcement for public shares
+- Auto-acceptance of shares
+- Share permissions and restrictions
+
+See the `frontend` service README for more details on share-related configuration options.
+
+## Scalability
+
+The sharing service depends on the configured storage backends for share metadata. Scalability characteristics depend on the chosen storage backend configuration.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/sse.yaml b/versioned_docs/version-7.x/_static/env-vars/sse.yaml
new file mode 100644
index 000000000..e2767c3a9
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/sse.yaml
@@ -0,0 +1,41 @@
+# Autogenerated
+# Filename: sse.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9139
+  token: ""
+  pprof: false
+  zpages: false
+keepalive_interval: 0s
+events:
+  endpoint: 127.0.0.1:9233
+  cluster: opencloud-cluster
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+  enable_tls: false
+  username: ""
+  password: ""
+http:
+  addr: 127.0.0.1:9135
+  root: /
+  cors:
+    allow_origins:
+    - '*'
+    allow_methods:
+    - GET
+    allow_headers:
+    - Authorization
+    - Origin
+    - Content-Type
+    - Accept
+    - X-Requested-With
+    - X-Request-Id
+    - Ocs-Apirequest
+    allow_credentials: true
+  tls:
+    enabled: false
+    cert: ""
+    key: ""
+token_manager:
+  jwt_secret: ""
diff --git a/versioned_docs/version-7.x/_static/env-vars/sse_configvars.md b/versioned_docs/version-7.x/_static/env-vars/sse_configvars.md
new file mode 100644
index 000000000..520e50300
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/sse_configvars.md
@@ -0,0 +1,27 @@
+## Environment variables for the **sse** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`SSE_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`SSE_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9139`|
+|`SSE_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`SSE_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`SSE_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`SSE_KEEPALIVE_INTERVAL`| 1.0.0 |Duration|`To prevent intermediate proxies from closing the SSE connection, send periodic SSE comments to keep it open.`|`0s`|
+|`OC_EVENTS_ENDPOINT`<br/>`SSE_EVENTS_ENDPOINT`| 1.0.0 |string|`The address of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture.`|`127.0.0.1:9233`|
+|`OC_EVENTS_CLUSTER`<br/>`SSE_EVENTS_CLUSTER`| 1.0.0 |string|`The clusterID of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture. Mandatory when using NATS as event system.`|`opencloud-cluster`|
+|`OC_INSECURE`<br/>`OC_EVENTS_TLS_INSECURE`<br/>`SSE_EVENTS_TLS_INSECURE`| 1.0.0 |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_EVENTS_TLS_ROOT_CA_CERTIFICATE`<br/>`SSE_EVENTS_TLS_ROOT_CA_CERTIFICATE`| 1.0.0 |string|`The root CA certificate used to validate the server's TLS certificate. If provided SSE_EVENTS_TLS_INSECURE will be seen as false.`|``|
+|`OC_EVENTS_ENABLE_TLS`<br/>`SSE_EVENTS_ENABLE_TLS`| 1.0.0 |bool|`Enable TLS for the connection to the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|`false`|
+|`OC_EVENTS_AUTH_USERNAME`<br/>`SSE_EVENTS_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_EVENTS_AUTH_PASSWORD`<br/>`SSE_EVENTS_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`SSE_HTTP_ADDR`| 1.0.0 |string|`The bind address of the HTTP service.`|`127.0.0.1:9135`|
+|`SSE_HTTP_ROOT`| 1.0.0 |string|`Subdirectory that serves as the root for this HTTP service.`|`/`|
+|`OC_CORS_ALLOW_ORIGINS`<br/>`SSE_CORS_ALLOW_ORIGINS`| 1.0.0 |[]string|`A list of allowed CORS origins. See following chapter for more details: *Access-Control-Allow-Origin* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin. See the Environment Variable Types description for more details.`|`[*]`|
+|`OC_CORS_ALLOW_METHODS`<br/>`SSE_CORS_ALLOW_METHODS`| 1.0.0 |[]string|`A list of allowed CORS methods. See following chapter for more details: *Access-Control-Request-Method* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Method. See the Environment Variable Types description for more details.`|`[GET]`|
+|`OC_CORS_ALLOW_HEADERS`<br/>`SSE_CORS_ALLOW_HEADERS`| 1.0.0 |[]string|`A list of allowed CORS headers. See following chapter for more details: *Access-Control-Request-Headers* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Headers. See the Environment Variable Types description for more details.`|`[Authorization Origin Content-Type Accept X-Requested-With X-Request-Id Ocs-Apirequest]`|
+|`OC_CORS_ALLOW_CREDENTIALS`<br/>`SSE_CORS_ALLOW_CREDENTIALS`| 1.0.0 |bool|`Allow credentials for CORS.See following chapter for more details: *Access-Control-Allow-Credentials* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Credentials.`|`true`|
+|`OC_HTTP_TLS_ENABLED`| 1.0.0 |bool|`Activates TLS for the http based services using the server certifcate and key configured via OC_HTTP_TLS_CERTIFICATE and OC_HTTP_TLS_KEY. If OC_HTTP_TLS_CERTIFICATE is not set a temporary server certificate is generated - to be used with PROXY_INSECURE_BACKEND=true.`|`false`|
+|`OC_HTTP_TLS_CERTIFICATE`| 1.0.0 |string|`Path/File name of the TLS server certificate (in PEM format) for the http services.`|``|
+|`OC_HTTP_TLS_KEY`| 1.0.0 |string|`Path/File name for the TLS certificate key (in PEM format) for the server certificate to use for the http services.`|``|
+|`OC_JWT_SECRET`<br/>`SSE_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
diff --git a/versioned_docs/version-7.x/_static/env-vars/sse_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/sse_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/sse_readme.md b/versioned_docs/version-7.x/_static/env-vars/sse_readme.md
new file mode 100755
index 000000000..2034844fb
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/sse_readme.md
@@ -0,0 +1,30 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The `sse` service is responsible for sending sse (Server-Sent Events) to a user. See [What is Server-Sent Events](https://medium.com/yemeksepeti-teknoloji/what-is-server-sent-events-sse-and-how-to-implement-it-904938bffd73) for a simple introduction and examples of server sent events.
+
+
+## Table of Contents
+
+* [The Log Service Ecosystem](#the-log-service-ecosystem)
+* [Subscribing](#subscribing)
+* [Keep SSE Connections Alive](#keep-sse-connections-alive)
+
+## The Log Service Ecosystem
+
+Log services like the `userlog`, `clientlog` and `sse` are responsible for composing notifications for a certain audience.
+  -   The `userlog` service translates and adjusts messages to be human readable.
+  -   The `clientlog` service composes machine readable messages, so clients can act without the need to query the server.
+  -   The `sse` service is only responsible for sending these messages. It does not care about their form or language.
+
+## Subscribing
+
+Clients can subscribe to the `/sse` endpoint to be informed by the server when an event happens. The `sse` endpoint will respect language changes of the user without needing to reconnect. Note that SSE has a limitation of six open connections per browser which can be reached if one has opened various tabs of the Web UI pointing to the same OpenCloud instance.
+
+## Keep SSE Connections Alive
+
+Some intermediate proxies drop connections after an idle time with no activity. If this is the case, configure the `SSE_KEEPALIVE_INTERVAL` envvar. This will send periodic SSE comments to keep connections open.
+
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/storage-publiclink.yaml b/versioned_docs/version-7.x/_static/env-vars/storage-publiclink.yaml
new file mode 100644
index 000000000..66f3b842a
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/storage-publiclink.yaml
@@ -0,0 +1,23 @@
+# Autogenerated
+# Filename: storage-publiclink.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9179
+  token: ""
+  pprof: false
+  zpages: false
+grpc:
+  addr: 127.0.0.1:9178
+  tls: null
+  protocol: tcp
+token_manager:
+  jwt_secret: ""
+reva:
+  address: eu.opencloud.api.gateway
+  tls:
+    mode: ""
+    cacert: ""
+skip_user_groups_in_token: false
+storage_provider:
+  mount_id: 7993447f-687f-490d-875c-ac95e89a62a4
diff --git a/versioned_docs/version-7.x/_static/env-vars/storage-publiclink_configvars.md b/versioned_docs/version-7.x/_static/env-vars/storage-publiclink_configvars.md
new file mode 100644
index 000000000..f4eef664a
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/storage-publiclink_configvars.md
@@ -0,0 +1,17 @@
+## Environment variables for the **storage-publiclink** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`STORAGE_PUBLICLINK_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`STORAGE_PUBLICLINK_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9179`|
+|`STORAGE_PUBLICLINK_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`STORAGE_PUBLICLINK_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`STORAGE_PUBLICLINK_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`STORAGE_PUBLICLINK_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9178`|
+|`OC_GRPC_PROTOCOL`<br/>`STORAGE_PUBLICLINK_GRPC_PROTOCOL`| 1.0.0 |string|`The transport protocol of the GRPC service.`|`tcp`|
+|`OC_JWT_SECRET`<br/>`STORAGE_PUBLICLINK_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`The CS3 gateway endpoint.`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
+|`STORAGE_PUBLICLINK_SKIP_USER_GROUPS_IN_TOKEN`| 1.0.0 |bool|`Disables the loading of user's group memberships from the reva access token.`|`false`|
+|`STORAGE_PUBLICLINK_STORAGE_PROVIDER_MOUNT_ID`| 1.0.0 |string|`Mount ID of this storage. Admins can set the ID for the storage in this config option manually which is then used to reference the storage. Any reasonable long string is possible, preferably this would be an UUIDv4 format.`|`7993447f-687f-490d-875c-ac95e89a62a4`|
diff --git a/versioned_docs/version-7.x/_static/env-vars/storage-publiclink_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/storage-publiclink_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/storage-publiclink_readme.md b/versioned_docs/version-7.x/_static/env-vars/storage-publiclink_readme.md
new file mode 100755
index 000000000..911f710f0
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/storage-publiclink_readme.md
@@ -0,0 +1,50 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The `storage-publiclink` service provides storage backend functionality for public link shares in OpenCloud. It implements the CS3 storage provider interface specifically for working with public link shared resources.
+
+
+## Table of Contents
+
+* [Overview](#overview)
+* [Integration](#integration)
+* [Storage Registry](#storage-registry)
+* [Access Control](#access-control)
+* [Scalability](#scalability)
+
+## Overview
+
+This service is part of the storage services family and is responsible for:
+- Providing access to publicly shared resources
+- Handling anonymous access to shared content
+
+## Integration
+
+The storage-publiclink service integrates with:
+- `sharing` service - Manages and persists public link shares
+- `frontend` service - Provides HTTP/WebDAV access to public links
+- Storage drivers - Accesses the actual file content
+
+## Storage Registry
+
+The service is registered in the gateway's storage registry with:
+- Provider ID: `7993447f-687f-490d-875c-ac95e89a62a4`
+- Mount point: `/public`
+- Space types: `grant` and `mountpoint`
+
+See the `gateway` README for more details on storage registry configuration.
+
+## Access Control
+
+Public link shares can be configured with:
+- Password protection
+- Expiration dates
+- Read-only or read-write permissions
+- Download limits
+
+## Scalability
+
+The storage-publiclink service can be scaled horizontally.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/storage-shares.yaml b/versioned_docs/version-7.x/_static/env-vars/storage-shares.yaml
new file mode 100644
index 000000000..4f1502c23
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/storage-shares.yaml
@@ -0,0 +1,24 @@
+# Autogenerated
+# Filename: storage-shares.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9156
+  token: ""
+  pprof: false
+  zpages: false
+grpc:
+  addr: 127.0.0.1:9154
+  tls: null
+  protocol: tcp
+token_manager:
+  jwt_secret: ""
+reva:
+  address: eu.opencloud.api.gateway
+  tls:
+    mode: ""
+    cacert: ""
+skip_user_groups_in_token: false
+mount_id: 7639e57c-4433-4a12-8201-722fd0009154
+readonly: false
+user_share_provider_endpoint: eu.opencloud.api.sharing
diff --git a/versioned_docs/version-7.x/_static/env-vars/storage-shares_configvars.md b/versioned_docs/version-7.x/_static/env-vars/storage-shares_configvars.md
new file mode 100644
index 000000000..dc878fa31
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/storage-shares_configvars.md
@@ -0,0 +1,19 @@
+## Environment variables for the **storage-shares** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`STORAGE_SHARES_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`STORAGE_SHARES_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9156`|
+|`STORAGE_SHARES_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`STORAGE_SHARES_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`STORAGE_SHARES_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`STORAGE_SHARES_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9154`|
+|`OC_GRPC_PROTOCOL`<br/>`STORAGE_SHARES_GRPC_PROTOCOL`| 1.0.0 |string|`The transport protocol of the GRPC service.`|`tcp`|
+|`OC_JWT_SECRET`<br/>`STORAGE_SHARES_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`The CS3 gateway endpoint.`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
+|`STORAGE_SHARES_SKIP_USER_GROUPS_IN_TOKEN`| 1.0.0 |bool|`Disables the loading of user's group memberships from the reva access token.`|`false`|
+|`STORAGE_SHARES_MOUNT_ID`| 1.0.0 |string|`Mount ID of this storage. Admins can set the ID for the storage in this config option manually which is then used to reference the storage. Any reasonable long string is possible, preferably this would be an UUIDv4 format.`|`7639e57c-4433-4a12-8201-722fd0009154`|
+|`STORAGE_SHARES_READ_ONLY`| 1.0.0 |bool|`Set this storage to be read-only.`|`false`|
+|`STORAGE_SHARES_USER_SHARE_PROVIDER_ENDPOINT`| 1.0.0 |string|`GRPC endpoint of the SHARING service.`|`eu.opencloud.api.sharing`|
diff --git a/versioned_docs/version-7.x/_static/env-vars/storage-shares_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/storage-shares_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/storage-shares_readme.md b/versioned_docs/version-7.x/_static/env-vars/storage-shares_readme.md
new file mode 100755
index 000000000..3651f0017
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/storage-shares_readme.md
@@ -0,0 +1,46 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The `storage-shares` service provides storage backend functionality for user and group shares in OpenCloud. It implements the CS3 storage provider interface specifically for working with shared resources.
+
+
+## Table of Contents
+
+* [Overview](#overview)
+* [Integration](#integration)
+* [Virtual Shares Folder](#virtual-shares-folder)
+* [Storage Registry](#storage-registry)
+* [Scalability](#scalability)
+
+## Overview
+
+This service is part of the storage services family and is responsible for:
+- Providing a virtual view of received shares
+- Handling access to resources shared by other users
+
+## Integration
+
+The storage-shares service integrates with:
+- `sharing` service - Manages and persists shares
+- `storage-users` service - Accesses the underlying file content
+- `frontend` service - Provides HTTP/WebDAV access to shares
+
+## Virtual Shares Folder
+
+The service provides a virtual "Shares" folder for each user where all received shares are mounted. This allows users to access all files and folders that have been shared with them in a centralized location.
+
+## Storage Registry
+
+The service is registered in the gateway's storage registry with:
+- Provider ID: `a0ca6a90-a365-4782-871e-d44447bbc668`
+- Mount point: `/users/{{.CurrentUser.Id.OpaqueId}}/Shares`
+- Space types: `virtual`, `grant`, and `mountpoint`
+
+See the `gateway` README for more details on storage registry configuration.
+
+## Scalability
+
+The storage-shares service can be scaled horizontally.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/storage-system.yaml b/versioned_docs/version-7.x/_static/env-vars/storage-system.yaml
new file mode 100644
index 000000000..850524914
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/storage-system.yaml
@@ -0,0 +1,45 @@
+# Autogenerated
+# Filename: storage-system.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9217
+  token: ""
+  pprof: false
+  zpages: false
+grpc:
+  addr: 127.0.0.1:9215
+  tls: null
+  protocol: tcp
+http:
+  addr: 127.0.0.1:9216
+  protocol: tcp
+token_manager:
+  jwt_secret: ""
+reva:
+  address: eu.opencloud.api.gateway
+  tls:
+    mode: ""
+    cacert: ""
+system_user_id: ""
+system_user_api_key: ""
+skip_user_groups_in_token: false
+cache:
+  store: memory
+  nodes:
+  - 127.0.0.1:9233
+  database: storage-system
+  ttl: 24h0m0s
+  disable_persistence: false
+  auth_username: ""
+  auth_password: ""
+  enable_tls: false
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+driver: decomposed
+drivers:
+  decomposed:
+    root: /var/lib/opencloud/storage/metadata
+    max_acquire_lock_cycles: 20
+    lock_cycle_duration_factor: 30
+data_server_url: http://localhost:9216/data
diff --git a/versioned_docs/version-7.x/_static/env-vars/storage-system_configvars.md b/versioned_docs/version-7.x/_static/env-vars/storage-system_configvars.md
new file mode 100644
index 000000000..8ad08ebb3
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/storage-system_configvars.md
@@ -0,0 +1,35 @@
+## Environment variables for the **storage-system** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`STORAGE_SYSTEM_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`STORAGE_SYSTEM_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9217`|
+|`STORAGE_SYSTEM_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint`|``|
+|`STORAGE_SYSTEM_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling`|`false`|
+|`STORAGE_SYSTEM_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`STORAGE_SYSTEM_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9215`|
+|`OC_GRPC_PROTOCOL`<br/>`STORAGE_SYSTEM_GRPC_PROTOCOL`| 1.0.0 |string|`The transport protocol of the GPRC service.`|`tcp`|
+|`STORAGE_SYSTEM_HTTP_ADDR`| 1.0.0 |string|`The bind address of the HTTP service.`|`127.0.0.1:9216`|
+|`STORAGE_SYSTEM_HTTP_PROTOCOL`| 1.0.0 |string|`The transport protocol of the HTTP service.`|`tcp`|
+|`OC_JWT_SECRET`<br/>`STORAGE_SYSTEM_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`The CS3 gateway endpoint.`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
+|`OC_SYSTEM_USER_ID`| 1.0.0 |string|`ID of the OpenCloud storage-system system user. Admins need to set the ID for the STORAGE-SYSTEM system user in this config option which is then used to reference the user. Any reasonable long string is possible, preferably this would be an UUIDv4 format.`|``|
+|`OC_SYSTEM_USER_API_KEY`| 1.0.0 |string|`API key for the STORAGE-SYSTEM system user.`|``|
+|`STORAGE_SYSTEM_SKIP_USER_GROUPS_IN_TOKEN`| 1.0.0 |bool|`Disables the loading of user's group memberships from the reva access token.`|`false`|
+|`OC_CACHE_STORE`<br/>`STORAGE_SYSTEM_CACHE_STORE`| 1.0.0 |string|`The type of the cache store. Supported values are: 'memory', 'redis-sentinel', 'nats-js-kv', 'noop'. See the text description for details.`|`memory`|
+|`OC_CACHE_STORE_NODES`<br/>`STORAGE_SYSTEM_CACHE_STORE_NODES`| 1.0.0 |[]string|`A list of nodes to access the configured store. This has no effect when 'memory' store is configured. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details.`|`[127.0.0.1:9233]`|
+|`OC_CACHE_DATABASE`| 1.0.0 |string|`The database name the configured store should use.`|`storage-system`|
+|`OC_CACHE_TTL`<br/>`STORAGE_SYSTEM_CACHE_TTL`| 1.0.0 |Duration|`Default time to live for user info in the user info cache. Only applied when access tokens has no expiration. See the Environment Variable Types description for more details.`|`24h0m0s`|
+|`OC_CACHE_DISABLE_PERSISTENCE`<br/>`STORAGE_SYSTEM_CACHE_DISABLE_PERSISTENCE`| 1.0.0 |bool|`Disables persistence of the cache. Only applies when store type 'nats-js-kv' is configured. Defaults to false.`|`false`|
+|`OC_CACHE_AUTH_USERNAME`<br/>`STORAGE_SYSTEM_CACHE_AUTH_USERNAME`| 1.0.0 |string|`Username for the configured store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_CACHE_AUTH_PASSWORD`<br/>`STORAGE_SYSTEM_CACHE_AUTH_PASSWORD`| 1.0.0 |string|`Password for the configured store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_CACHE_ENABLE_TLS`<br/>`STORAGE_SYSTEM_CACHE_ENABLE_TLS`| next |bool|`Enable TLS for the connection to file metadata cache.`|`false`|
+|`OC_INSECURE`<br/>`OC_CACHE_TLS_INSECURE`<br/>`STORAGE_SYSTEM_CACHE_TLS_INSECURE`| next |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_CACHE_TLS_ROOT_CA_CERTIFICATE`<br/>`STORAGE_SYSTEM_CACHE_TLS_ROOT_CA_CERTIFICATE`| next |string|`The root CA certificate used to validate the server's TLS certificate. If provided STORAGE_SYSTEM_CACHE_TLS_INSECURE will be seen as false.`|``|
+|`STORAGE_SYSTEM_DRIVER`| 1.0.0 |string|`The driver which should be used by the service. The only supported driver is 'decomposed'. For backwards compatibility reasons it's also possible to use the 'ocis' driver and configure it using the 'decomposed' options. `|`decomposed`|
+|`STORAGE_SYSTEM_OC_ROOT`| 1.0.0 |string|`Path for the directory where the STORAGE-SYSTEM service stores it's persistent data. If not defined, the root directory derives from $OC_BASE_DATA_PATH/storage.`|`/var/lib/opencloud/storage/metadata`|
+|`STORAGE_SYSTEM_OC_MAX_ACQUIRE_LOCK_CYCLES`| 1.0.0 |int|`When trying to lock files, OpenCloud will try this amount of times to acquire the lock before failing. After each try it will wait for an increasing amount of time. Values of 0 or below will be ignored and the default value of 20 will be used.`|`20`|
+|`STORAGE_SYSTEM_OC_LOCK_CYCLE_DURATION_FACTOR`| 1.0.0 |int|`When trying to lock files, OpenCloud will multiply the cycle with this factor and use it as a millisecond timeout. Values of 0 or below will be ignored and the default value of 30 will be used.`|`30`|
+|`STORAGE_SYSTEM_DATA_SERVER_URL`| 1.0.0 |string|`URL of the data server, needs to be reachable by other services using this service.`|`http://localhost:9216/data`|
diff --git a/versioned_docs/version-7.x/_static/env-vars/storage-system_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/storage-system_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/storage-system_readme.md b/versioned_docs/version-7.x/_static/env-vars/storage-system_readme.md
new file mode 100755
index 000000000..9a7901e39
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/storage-system_readme.md
@@ -0,0 +1,31 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The OpenCloud Storage-System service persists and caches user related data that is defined via OpenCloud. This can be among other data role assignments, user settings and users shares.
+
+
+## Table of Contents
+
+* [Caching](#caching)
+
+## Caching
+
+The `storage-system` service caches file metadata via the configured store in `STORAGE_SYSTEM_CACHE_STORE`. Possible stores are:
+  -   `memory`: Basic in-memory store and the default.
+  -   `redis-sentinel`: Stores data in a configured Redis Sentinel cluster.
+  -   `nats-js-kv`: Stores data using key-value-store feature of [nats jetstream](https://docs.nats.io/nats-concepts/jetstream/key-value-store)
+  -   `noop`: Stores nothing. Useful for testing. Not recommended in production environments.
+
+Other store types may work but are not supported currently.
+
+Note: The service can only be scaled if not using `memory` store and the stores are configured identically over all instances!
+
+Note that if you have used one of the deprecated stores, you should reconfigure to one of the supported ones as the deprecated stores will be removed in a later version.
+
+Store specific notes:
+  -   When using `redis-sentinel`, the Redis master to use is configured via e.g. `OC_CACHE_STORE_NODES` in the form of `<sentinel-host>:<sentinel-port>/<redis-master>` like `10.10.0.200:26379/mymaster`.
+  -   When using `nats-js-kv` it is recommended to set `OC_CACHE_STORE_NODES` to the same value as `OC_EVENTS_ENDPOINT`. That way the cache uses the same nats instance as the event bus.
+  -   When using the `nats-js-kv` store, it is possible to set `OC_CACHE_DISABLE_PERSISTENCE` to instruct nats to not persist cache data on disc.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/storage-users.yaml b/versioned_docs/version-7.x/_static/env-vars/storage-users.yaml
new file mode 100644
index 000000000..b17172a67
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/storage-users.yaml
@@ -0,0 +1,202 @@
+# Autogenerated
+# Filename: storage-users.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9159
+  token: ""
+  pprof: false
+  zpages: false
+grpc:
+  addr: 127.0.0.1:9157
+  tls: null
+  protocol: tcp
+http:
+  addr: 127.0.0.1:9158
+  protocol: tcp
+  prefix: data
+  cors:
+    allow_origins:
+    - https://localhost:9200
+    allow_methods:
+    - POST
+    - HEAD
+    - PATCH
+    - OPTIONS
+    - GET
+    - DELETE
+    allow_headers:
+    - Authorization
+    - Origin
+    - X-Requested-With
+    - X-Request-Id
+    - X-HTTP-Method-Override
+    - Content-Type
+    - Upload-Length
+    - Upload-Offset
+    - Tus-Resumable
+    - Upload-Metadata
+    - Upload-Defer-Length
+    - Upload-Concat
+    - Upload-Incomplete
+    - Upload-Draft-Interop-Version
+    allow_credentials: false
+    expose_headers:
+    - Upload-Offset
+    - Location
+    - Upload-Length
+    - Tus-Version
+    - Tus-Resumable
+    - Tus-Max-Size
+    - Tus-Extension
+    - Upload-Metadata
+    - Upload-Defer-Length
+    - Upload-Concat
+    - Upload-Incomplete
+    - Upload-Draft-Interop-Version
+    max_age: 86400
+token_manager:
+  jwt_secret: ""
+reva:
+  address: eu.opencloud.api.gateway
+  tls:
+    mode: ""
+    cacert: ""
+skip_user_groups_in_token: false
+graceful_shutdown_timeout: 30
+driver: posix
+drivers:
+  decomposed:
+    propagator: sync
+    async_propagator_options:
+      propagation_delay: 0s
+    root: /var/lib/opencloud/storage/users
+    user_layout: '{{.Id.OpaqueId}}'
+    permissions_endpoint: eu.opencloud.api.settings
+    personalspacealias_template: '{{.SpaceType}}/{{.User.Username | lower}}'
+    personalspacepath_template: ""
+    generalspacealias_template: '{{.SpaceType}}/{{.SpaceName | replace " " "-" | lower}}'
+    generalspacepath_template: ""
+    share_folder: /Shares
+    max_acquire_lock_cycles: 20
+    lock_cycle_duration_factor: 30
+    max_concurrency: 5
+    async_uploads: true
+    max_quota: 0
+    disable_versioning: false
+  decomposeds3:
+    propagator: sync
+    async_propagator_options:
+      propagation_delay: 0s
+    root: /var/lib/opencloud/storage/users
+    user_layout: '{{.Id.OpaqueId}}'
+    permissions_endpoint: eu.opencloud.api.settings
+    region: default
+    access_key: ""
+    secret_key: ""
+    endpoint: ""
+    bucket: ""
+    put_object_disable_content_sha254: false
+    put_object_disable_multipart: false
+    put_object_send_content_md5: true
+    put_object_concurrent_stream_parts: false
+    put_object_num_threads: 4
+    put_object_part_size: 0
+    personalspacealias_template: '{{.SpaceType}}/{{.User.Username | lower}}'
+    personalspacepath_template: ""
+    generalspacealias_template: '{{.SpaceType}}/{{.SpaceName | replace " " "-" | lower}}'
+    generalspacepath_template: ""
+    share_folder: /Shares
+    max_acquire_lock_cycles: 20
+    lock_cycle_duration_factor: 30
+    max_concurrency: 5
+    async_uploads: true
+    disable_versioning: false
+  owncloudsql:
+    root: /var/lib/opencloud/storage/owncloud
+    share_folder: /Shares
+    user_layout: '{{.Username}}'
+    upload_info_dir: /var/lib/opencloud/storage/uploadinfo
+    db_username: owncloud
+    db_password: owncloud
+    db_host: ""
+    db_port: 3306
+    db_name: owncloud
+    users_provider_endpoint: eu.opencloud.api.users
+  posix:
+    root: /var/lib/opencloud/storage/users
+    propagator: ""
+    async_propagator_options:
+      propagation_delay: 0s
+    personalspacealias_template: '{{.SpaceType}}/{{.User.Username | lower}}'
+    personalspacepath_template: users/{{.User.Id.OpaqueId}}
+    generalspacealias_template: '{{.SpaceType}}/{{.SpaceName | replace " " "-" | lower}}'
+    generalspacepath_template: projects/{{.SpaceId}}
+    permissions_endpoint: eu.opencloud.api.settings
+    async_uploads: true
+    scan_debounce_delay: 1s
+    max_quota: 0
+    max_acquire_lock_cycles: 0
+    lock_cycle_duration_factor: 0
+    max_concurrency: 0
+    disable_versioning: false
+    use_space_groups: false
+    enable_fs_revisions: false
+    scan_fs: true
+    watch_fs: false
+    watch_type: ""
+    watch_path: ""
+    watch_notification_brokers: ""
+    watch_root: ""
+    inotify_stats_frequency: 5m0s
+data_server_url: http://localhost:9158/data
+data_gateway_url: http://localhost:9140/data
+transfer_expires: 86400
+events:
+  endpoint: 127.0.0.1:9233
+  cluster: opencloud-cluster
+  tls_insecure: false
+  tls_root_ca_cert_path: ""
+  enable_tls: false
+  num_consumers: 0
+  username: ""
+  password: ""
+filemetadata_cache:
+  store: memory
+  nodes:
+  - 127.0.0.1:9233
+  database: storage-users
+  ttl: 24h0m0s
+  disable_persistence: false
+  username: ""
+  password: ""
+  enable_tls: false
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+id_cache:
+  store: nats-js-kv
+  nodes:
+  - 127.0.0.1:9233
+  database: ids-storage-users
+  ttl: 0s
+  disable_persistence: false
+  username: ""
+  password: ""
+  enable_tls: false
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+mount_id: ""
+expose_data_server: false
+readonly: false
+upload_expiration: 86400
+tasks:
+  purge_trash_bin:
+    user_id: ""
+    personal_delete_before: 720h0m0s
+    project_delete_before: 720h0m0s
+service_account:
+  service_account_id: ""
+  service_account_secret: ""
+gateway_addr: 127.0.0.1:9142
+machine_auth_api_key: ""
+max_attempts_rename_file: 0
diff --git a/versioned_docs/version-7.x/_static/env-vars/storage-users_configvars.md b/versioned_docs/version-7.x/_static/env-vars/storage-users_configvars.md
new file mode 100644
index 000000000..78031f1a4
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/storage-users_configvars.md
@@ -0,0 +1,155 @@
+
+2026-06-19-00-12-13
+
+## Deprecation Notice
+
+| Deprecation Info | Deprecation Version | Removal Version | Deprecation Replacement |
+|---|---|---|:---|
+| STORAGE_USERS_POSIX_WATCH_FOLDER_KAFKA_BROKERS is deprecated and will be removed in a future version. Please use STORAGE_USERS_POSIX_WATCH_NOTIFICATION_BROKERS instead. | 4.0.0 |  |  |
+
+## Environment variables for the **storage-users** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`STORAGE_USERS_SERVICE_NAME`| 1.0.0 |string|`Service name to use. Change this when starting an additional storage provider with a custom configuration to prevent it from colliding with the default 'storage-users' service.`|`storage-users`|
+|`OC_LOG_LEVEL`<br/>`STORAGE_USERS_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`STORAGE_USERS_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9159`|
+|`STORAGE_USERS_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`STORAGE_USERS_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`STORAGE_USERS_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`STORAGE_USERS_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9157`|
+|`OC_GRPC_PROTOCOL`<br/>`STORAGE_USERS_GRPC_PROTOCOL`| 1.0.0 |string|`The transport protocol of the GPRC service.`|`tcp`|
+|`STORAGE_USERS_HTTP_ADDR`| 1.0.0 |string|`The bind address of the HTTP service.`|`127.0.0.1:9158`|
+|`STORAGE_USERS_HTTP_PROTOCOL`| 1.0.0 |string|`The transport protocol of the HTTP service.`|`tcp`|
+|`OC_CORS_ALLOW_ORIGINS`<br/>`STORAGE_USERS_CORS_ALLOW_ORIGINS`| 1.0.0 |[]string|`A list of allowed CORS origins. See following chapter for more details: *Access-Control-Allow-Origin* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin. See the Environment Variable Types description for more details.`|`[https://localhost:9200]`|
+|`OC_CORS_ALLOW_METHODS`<br/>`STORAGE_USERS_CORS_ALLOW_METHODS`| 1.0.0 |[]string|`A list of allowed CORS methods. See following chapter for more details: *Access-Control-Request-Method* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Method. See the Environment Variable Types description for more details.`|`[POST HEAD PATCH OPTIONS GET DELETE]`|
+|`OC_CORS_ALLOW_HEADERS`<br/>`STORAGE_USERS_CORS_ALLOW_HEADERS`| 1.0.0 |[]string|`A list of allowed CORS headers. See following chapter for more details: *Access-Control-Request-Headers* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Headers. See the Environment Variable Types description for more details.`|`[Authorization Origin X-Requested-With X-Request-Id X-HTTP-Method-Override Content-Type Upload-Length Upload-Offset Tus-Resumable Upload-Metadata Upload-Defer-Length Upload-Concat Upload-Incomplete Upload-Draft-Interop-Version]`|
+|`OC_CORS_ALLOW_CREDENTIALS`<br/>`STORAGE_USERS_CORS_ALLOW_CREDENTIALS`| 1.0.0 |bool|`Allow credentials for CORS.See following chapter for more details: *Access-Control-Allow-Credentials* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Credentials.`|`false`|
+|`OC_CORS_EXPOSE_HEADERS`<br/>`STORAGE_USERS_CORS_EXPOSE_HEADERS`| 1.0.0 |[]string|`A list of exposed CORS headers. See following chapter for more details: *Access-Control-Expose-Headers* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Expose-Headers. See the Environment Variable Types description for more details.`|`[Upload-Offset Location Upload-Length Tus-Version Tus-Resumable Tus-Max-Size Tus-Extension Upload-Metadata Upload-Defer-Length Upload-Concat Upload-Incomplete Upload-Draft-Interop-Version]`|
+|`OC_CORS_MAX_AGE`<br/>`STORAGE_USERS_CORS_MAX_AGE`| 1.0.0 |uint|`The max cache duration of preflight headers. See following chapter for more details: *Access-Control-Max-Age* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Max-Age. See the Environment Variable Types description for more details.`|`86400`|
+|`OC_JWT_SECRET`<br/>`STORAGE_USERS_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`The CS3 gateway endpoint.`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
+|`STORAGE_USERS_SKIP_USER_GROUPS_IN_TOKEN`| 1.0.0 |bool|`Disables the loading of user's group memberships from the reva access token.`|`false`|
+|`STORAGE_USERS_GRACEFUL_SHUTDOWN_TIMEOUT`| 1.0.0 |int|`The number of seconds to wait for the 'storage-users' service to shutdown cleanly before exiting with an error that gets logged. Note: This setting is only applicable when running the 'storage-users' service as a standalone service. See the text description for more details.`|`30`|
+|`STORAGE_USERS_DRIVER`| 1.0.0 |string|`The storage driver which should be used by the service. Defaults to 'posix'. Supported values are: 'posix', 'decomposed', 'decomposeds3' and 'owncloudsql'. For backwards compatibility reasons it's also possible to use the 'ocis' and 's3ng' driver and configure them using the 'decomposed'/'decomposeds3' options. The 'posix' driver stores data directly on a POSIX-compliant filesystem. The 'decomposed' driver stores all data (blob and meta data) in a POSIX compliant volume. The 'decomposeds3' driver stores metadata in a POSIX compliant volume and uploads blobs to the s3 bucket.`|`posix`|
+|`OC_DECOMPOSEDFS_PROPAGATOR`<br/>`STORAGE_USERS_DECOMPOSED_PROPAGATOR`| 1.0.0 |string|`The propagator used for decomposedfs. At the moment, only 'sync' is fully supported, 'async' is available as an experimental option.`|`sync`|
+|`STORAGE_USERS_ASYNC_PROPAGATOR_PROPAGATION_DELAY`| 1.0.0 |Duration|`The delay between a change made to a tree and the propagation start on treesize and treetime. Multiple propagations are computed to a single one. See the Environment Variable Types description for more details.`|`0s`|
+|`STORAGE_USERS_DECOMPOSED_ROOT`| 1.0.0 |string|`The directory where the filesystem storage will store blobs and metadata. If not defined, the root directory derives from $OC_BASE_DATA_PATH/storage/users.`|`/var/lib/opencloud/storage/users`|
+|`STORAGE_USERS_DECOMPOSED_USER_LAYOUT`| 1.0.0 |string|`Template string for the user storage layout in the user directory.`|`{{.Id.OpaqueId}}`|
+|`STORAGE_USERS_PERMISSION_ENDPOINT`<br/>`STORAGE_USERS_DECOMPOSED_PERMISSIONS_ENDPOINT`| 1.0.0 |string|`Endpoint of the permissions service. The endpoints can differ for 'decomposed' and 'decomposeds3'.`|`eu.opencloud.api.settings`|
+|`STORAGE_USERS_DECOMPOSED_PERSONAL_SPACE_ALIAS_TEMPLATE`| 1.0.0 |string|`Template string to construct personal space aliases.`|`{{.SpaceType}}/{{.User.Username \| lower}}`|
+|`STORAGE_USERS_DECOMPOSED_PERSONAL_SPACE_PATH_TEMPLATE`| 1.0.0 |string|`Template string to construct the paths of the personal space roots.`|``|
+|`STORAGE_USERS_DECOMPOSED_GENERAL_SPACE_ALIAS_TEMPLATE`| 1.0.0 |string|`Template string to construct general space aliases.`|`{{.SpaceType}}/{{.SpaceName \| replace " " "-" \| lower}}`|
+|`STORAGE_USERS_DECOMPOSED_GENERAL_SPACE_PATH_TEMPLATE`| 1.0.0 |string|`Template string to construct the paths of the projects space roots.`|``|
+|`STORAGE_USERS_DECOMPOSED_SHARE_FOLDER`| 1.0.0 |string|`Name of the folder jailing all shares.`|`/Shares`|
+|`STORAGE_USERS_DECOMPOSED_MAX_ACQUIRE_LOCK_CYCLES`| 1.0.0 |int|`When trying to lock files, OpenCloud will try this amount of times to acquire the lock before failing. After each try it will wait for an increasing amount of time. Values of 0 or below will be ignored and the default value will be used.`|`20`|
+|`STORAGE_USERS_DECOMPOSED_LOCK_CYCLE_DURATION_FACTOR`| 1.0.0 |int|`When trying to lock files, OpenCloud will multiply the cycle with this factor and use it as a millisecond timeout. Values of 0 or below will be ignored and the default value will be used.`|`30`|
+|`OC_MAX_CONCURRENCY`<br/>`STORAGE_USERS_DECOMPOSED_MAX_CONCURRENCY`| 1.0.0 |int|`Maximum number of concurrent go-routines. Higher values can potentially get work done faster but will also cause more load on the system. Values of 0 or below will be ignored and the default value will be used.`|`5`|
+|`OC_ASYNC_UPLOADS`| 1.0.0 |bool|`Enable asynchronous file uploads.`|`true`|
+|`OC_SPACES_MAX_QUOTA`<br/>`STORAGE_USERS_DECOMPOSED_MAX_QUOTA`| 1.0.0 |uint64|`Set a global max quota for spaces in bytes. A value of 0 equals unlimited. If not using the global OC_SPACES_MAX_QUOTA, you must define the FRONTEND_MAX_QUOTA in the frontend service.`|`0`|
+|`OC_DISABLE_VERSIONING`| 1.0.0 |bool|`Disables versioning of files. When set to true, new uploads with the same filename will overwrite existing files instead of creating a new version.`|`false`|
+|`OC_DECOMPOSEDFS_PROPAGATOR`<br/>`STORAGE_USERS_DECOMPOSEDS3_PROPAGATOR`| 1.0.0 |string|`The propagator used for decomposedfs. At the moment, only 'sync' is fully supported, 'async' is available as an experimental option.`|`sync`|
+|`STORAGE_USERS_ASYNC_PROPAGATOR_PROPAGATION_DELAY`| 1.0.0 |Duration|`The delay between a change made to a tree and the propagation start on treesize and treetime. Multiple propagations are computed to a single one. See the Environment Variable Types description for more details.`|`0s`|
+|`STORAGE_USERS_DECOMPOSEDS3_ROOT`| 1.0.0 |string|`The directory where the filesystem storage will store metadata for blobs. If not defined, the root directory derives from $OC_BASE_DATA_PATH/storage/users.`|`/var/lib/opencloud/storage/users`|
+|`STORAGE_USERS_DECOMPOSEDS3_USER_LAYOUT`| 1.0.0 |string|`Template string for the user storage layout in the user directory.`|`{{.Id.OpaqueId}}`|
+|`STORAGE_USERS_PERMISSION_ENDPOINT`<br/>`STORAGE_USERS_DECOMPOSEDS3_PERMISSIONS_ENDPOINT`| 1.0.0 |string|`Endpoint of the permissions service. The endpoints can differ for 'decomposed' and 'decomposeds3'.`|`eu.opencloud.api.settings`|
+|`STORAGE_USERS_DECOMPOSEDS3_REGION`| 1.0.0 |string|`Region of the S3 bucket.`|`default`|
+|`STORAGE_USERS_DECOMPOSEDS3_ACCESS_KEY`| 1.0.0 |string|`Access key for the S3 bucket.`|``|
+|`STORAGE_USERS_DECOMPOSEDS3_SECRET_KEY`| 1.0.0 |string|`Secret key for the S3 bucket.`|``|
+|`STORAGE_USERS_DECOMPOSEDS3_ENDPOINT`| 1.0.0 |string|`Endpoint for the S3 bucket.`|``|
+|`STORAGE_USERS_DECOMPOSEDS3_BUCKET`| 1.0.0 |string|`Name of the S3 bucket.`|``|
+|`STORAGE_USERS_DECOMPOSEDS3_PUT_OBJECT_DISABLE_CONTENT_SHA256`| 1.0.0 |bool|`Disable sending content sha256 when copying objects to S3.`|`false`|
+|`STORAGE_USERS_DECOMPOSEDS3_PUT_OBJECT_DISABLE_MULTIPART`| 1.0.0 |bool|`Disable multipart uploads when copying objects to S3.`|`false`|
+|`STORAGE_USERS_DECOMPOSEDS3_PUT_OBJECT_SEND_CONTENT_MD5`| 1.0.0 |bool|`Send a Content-MD5 header when copying objects to S3.`|`true`|
+|`STORAGE_USERS_DECOMPOSEDS3_PUT_OBJECT_CONCURRENT_STREAM_PARTS`| 1.0.0 |bool|`Always precreate parts when copying objects to S3. This is not recommended. It uses a memory buffer. If true, PartSize needs to be set.`|`false`|
+|`STORAGE_USERS_DECOMPOSEDS3_PUT_OBJECT_NUM_THREADS`| 1.0.0 |uint|`Number of concurrent uploads to use when copying objects to S3.`|`4`|
+|`STORAGE_USERS_DECOMPOSEDS3_PUT_OBJECT_PART_SIZE`| 1.0.0 |uint64|`Part size for concurrent uploads to S3. If no value or 0 is set, the library automatically calculates the part size according to the total size of the file to be uploaded. The value range is min 5MB and max 5GB.`|`0`|
+|`STORAGE_USERS_DECOMPOSEDS3_PERSONAL_SPACE_ALIAS_TEMPLATE`| 1.0.0 |string|`Template string to construct personal space aliases.`|`{{.SpaceType}}/{{.User.Username \| lower}}`|
+|`STORAGE_USERS_DECOMPOSEDS3_PERSONAL_SPACE_PATH_TEMPLATE`| 1.0.0 |string|`Template string to construct the paths of the personal space roots.`|``|
+|`STORAGE_USERS_DECOMPOSEDS3_GENERAL_SPACE_ALIAS_TEMPLATE`| 1.0.0 |string|`Template string to construct general space aliases.`|`{{.SpaceType}}/{{.SpaceName \| replace " " "-" \| lower}}`|
+|`STORAGE_USERS_DECOMPOSEDS3_GENERAL_SPACE_PATH_TEMPLATE`| 1.0.0 |string|`Template string to construct the paths of the projects space roots.`|``|
+|`STORAGE_USERS_DECOMPOSEDS3_SHARE_FOLDER`| 1.0.0 |string|`Name of the folder jailing all shares.`|`/Shares`|
+|`STORAGE_USERS_DECOMPOSEDS3_MAX_ACQUIRE_LOCK_CYCLES`| 1.0.0 |int|`When trying to lock files, OpenCloud will try this amount of times to acquire the lock before failing. After each try it will wait for an increasing amount of time. Values of 0 or below will be ignored and the default value of 20 will be used.`|`20`|
+|`STORAGE_USERS_DECOMPOSEDS3_LOCK_CYCLE_DURATION_FACTOR`| 1.0.0 |int|`When trying to lock files, OpenCloud will multiply the cycle with this factor and use it as a millisecond timeout. Values of 0 or below will be ignored and the default value of 30 will be used.`|`30`|
+|`OC_MAX_CONCURRENCY`<br/>`STORAGE_USERS_DECOMPOSEDS3_MAX_CONCURRENCY`| 1.0.0 |int|`Maximum number of concurrent go-routines. Higher values can potentially get work done faster but will also cause more load on the system. Values of 0 or below will be ignored and the default value of 100 will be used.`|`5`|
+|`OC_ASYNC_UPLOADS`| 1.0.0 |bool|`Enable asynchronous file uploads.`|`true`|
+|`OC_DISABLE_VERSIONING`| 1.0.0 |bool|`Disables versioning of files. When set to true, new uploads with the same filename will overwrite existing files instead of creating a new version.`|`false`|
+|`STORAGE_USERS_OWNCLOUDSQL_DATADIR`| 1.0.0 |string|`The directory where the filesystem storage will store SQL migration data. If not defined, the root directory derives from $OC_BASE_DATA_PATH/storage/owncloud.`|`/var/lib/opencloud/storage/owncloud`|
+|`STORAGE_USERS_OWNCLOUDSQL_SHARE_FOLDER`| 1.0.0 |string|`Name of the folder jailing all shares.`|`/Shares`|
+|`STORAGE_USERS_OWNCLOUDSQL_LAYOUT`| 1.0.0 |string|`Path layout to use to navigate into a users folder in an owncloud data directory`|`{{.Username}}`|
+|`STORAGE_USERS_OWNCLOUDSQL_UPLOADINFO_DIR`| 1.0.0 |string|`The directory where the filesystem will store uploads temporarily. If not defined, the root directory derives from $OC_BASE_DATA_PATH/storage/uploadinfo.`|`/var/lib/opencloud/storage/uploadinfo`|
+|`STORAGE_USERS_OWNCLOUDSQL_DB_USERNAME`| 1.0.0 |string|`Username for the database.`|`owncloud`|
+|`STORAGE_USERS_OWNCLOUDSQL_DB_PASSWORD`| 1.0.0 |string|`Password for the database.`|`owncloud`|
+|`STORAGE_USERS_OWNCLOUDSQL_DB_HOST`| 1.0.0 |string|`Hostname or IP of the database server.`|``|
+|`STORAGE_USERS_OWNCLOUDSQL_DB_PORT`| 1.0.0 |int|`Port that the database server is listening on.`|`3306`|
+|`STORAGE_USERS_OWNCLOUDSQL_DB_NAME`| 1.0.0 |string|`Name of the database to be used.`|`owncloud`|
+|`STORAGE_USERS_OWNCLOUDSQL_USERS_PROVIDER_ENDPOINT`| 1.0.0 |string|`Endpoint of the users provider.`|`eu.opencloud.api.users`|
+|`STORAGE_USERS_POSIX_ROOT`| 1.0.0 |string|`The directory where the filesystem storage will store its data. If not defined, the root directory derives from $OC_BASE_DATA_PATH/storage/users.`|`/var/lib/opencloud/storage/users`|
+|`OC_DECOMPOSEDFS_PROPAGATOR`<br/>`STORAGE_USERS_POSIX_PROPAGATOR`| 2.0.0 |string|`The propagator used for the posix driver. At the moment, only 'sync' is fully supported, 'async' is available as an experimental option.`|``|
+|`STORAGE_USERS_ASYNC_PROPAGATOR_PROPAGATION_DELAY`| 1.0.0 |Duration|`The delay between a change made to a tree and the propagation start on treesize and treetime. Multiple propagations are computed to a single one. See the Environment Variable Types description for more details.`|`0s`|
+|`STORAGE_USERS_POSIX_PERSONAL_SPACE_ALIAS_TEMPLATE`| 1.0.0 |string|`Template string to construct personal space aliases.`|`{{.SpaceType}}/{{.User.Username \| lower}}`|
+|`STORAGE_USERS_POSIX_PERSONAL_SPACE_PATH_TEMPLATE`| 1.0.0 |string|`Template string to construct the paths of the personal space roots.`|`users/{{.User.Id.OpaqueId}}`|
+|`STORAGE_USERS_POSIX_GENERAL_SPACE_ALIAS_TEMPLATE`| 1.0.0 |string|`Template string to construct general space aliases.`|`{{.SpaceType}}/{{.SpaceName \| replace " " "-" \| lower}}`|
+|`STORAGE_USERS_POSIX_GENERAL_SPACE_PATH_TEMPLATE`| 1.0.0 |string|`Template string to construct the paths of the projects space roots.`|`projects/{{.SpaceId}}`|
+|`STORAGE_USERS_PERMISSION_ENDPOINT`<br/>`STORAGE_USERS_POSIX_PERMISSIONS_ENDPOINT`| 1.0.0 |string|`Endpoint of the permissions service. The endpoints can differ for 'decomposed', 'posix' and 'decomposeds3'.`|`eu.opencloud.api.settings`|
+|`OC_ASYNC_UPLOADS`| 1.0.0 |bool|`Enable asynchronous file uploads.`|`true`|
+|`STORAGE_USERS_POSIX_SCAN_DEBOUNCE_DELAY`| 1.0.0 |Duration|`The time in milliseconds to wait before scanning the filesystem for changes after a change has been detected.`|`1s`|
+|`OC_SPACES_MAX_QUOTA`<br/>`STORAGE_USERS_POSIX_MAX_QUOTA`| 2.0.0 |uint64|`Set a global max quota for spaces in bytes. A value of 0 equals unlimited. If not using the global OC_SPACES_MAX_QUOTA, you must define the FRONTEND_MAX_QUOTA in the frontend service.`|`0`|
+|`STORAGE_USERS_POSIX_MAX_ACQUIRE_LOCK_CYCLES`| 2.0.0 |int|`When trying to lock files, OpenCloud will try this amount of times to acquire the lock before failing. After each try it will wait for an increasing amount of time. Values of 0 or below will be ignored and the default value will be used.`|`0`|
+|`STORAGE_USERS_POSIX_LOCK_CYCLE_DURATION_FACTOR`| 2.0.0 |int|`When trying to lock files, OpenCloud will multiply the cycle with this factor and use it as a millisecond timeout. Values of 0 or below will be ignored and the default value will be used.`|`0`|
+|`OC_MAX_CONCURRENCY`<br/>`STORAGE_USERS_POSIX_MAX_CONCURRENCY`| 2.0.0 |int|`Maximum number of concurrent go-routines. Higher values can potentially get work done faster but will also cause more load on the system. Values of 0 or below will be ignored and the default value will be used.`|`0`|
+|`OC_DISABLE_VERSIONING`| 2.0.0 |bool|`Disables versioning of files. When set to true, new uploads with the same filename will overwrite existing files instead of creating a new version.`|`false`|
+|`STORAGE_USERS_POSIX_USE_SPACE_GROUPS`| 1.0.0 |bool|`Use space groups to manage permissions on spaces.`|`false`|
+|`STORAGE_USERS_POSIX_ENABLE_FS_REVISIONS`| 1.0.0 |bool|`Allow for generating revisions from changes done to the local storage. Note: This doubles the number of bytes stored on disk because a copy of the current revision is stored to be turned into a revision later.`|`false`|
+|`STORAGE_USERS_POSIX_SCAN_FS`| 6.2.0 |bool|`Scan the filesystem at startup for changes and update the metadata accordingly.`|`true`|
+|`STORAGE_USERS_POSIX_WATCH_FS`| 2.0.0 |bool|`Enable the filesystem watcher to detect changes to the filesystem. This is used to detect changes to the filesystem and update the metadata accordingly.`|`false`|
+|`STORAGE_USERS_POSIX_WATCH_TYPE`| 1.0.0 |string|`Type of the watcher to use for getting notified about changes to the filesystem. Currently available options are 'inotifywait' (default), 'cephfs', 'gpfswatchfolder' and 'gpfsfileauditlogging'.`|``|
+|`STORAGE_USERS_POSIX_WATCH_PATH`| 1.0.0 |string|`Path to the watch directory/file. Only applies to the 'gpfsfileauditlogging' and 'inotifywait' watcher, in which case it is the path of the file audit log file/base directory to watch.`|``|
+|`STORAGE_USERS_POSIX_WATCH_NOTIFICATION_BROKERS,STORAGE_USERS_POSIX_WATCH_FOLDER_KAFKA_BROKERS`| 1.0.0 |string|`Comma-separated list of kafka brokers to read the watchfolder events from.`|``|
+|`STORAGE_USERS_POSIX_WATCH_ROOT`| 4.0.0 |string|`Path to the watch root directory. Event paths will be considered relative to this path. Only applies to the 'gpswatchfolder' and 'cephfs' watchers.`|``|
+|`STORAGE_USERS_POSIX_INOTIFY_STATS_FREQUENCY`| 4.0.0 |Duration|`Frequency to log inotify stats.`|`5m0s`|
+|`STORAGE_USERS_DATA_SERVER_URL`| 1.0.0 |string|`URL of the data server, needs to be reachable by the data gateway provided by the frontend service or the user if directly exposed.`|`http://localhost:9158/data`|
+|`STORAGE_USERS_DATA_GATEWAY_URL`| 1.0.0 |string|`URL of the data gateway server`|`http://localhost:9140/data`|
+|`STORAGE_USERS_TRANSFER_EXPIRES`| 1.0.0 |int64|`The time after which the token for upload postprocessing expires`|`86400`|
+|`OC_EVENTS_ENDPOINT`<br/>`STORAGE_USERS_EVENTS_ENDPOINT`| 1.0.0 |string|`The address of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture.`|`127.0.0.1:9233`|
+|`OC_EVENTS_CLUSTER`<br/>`STORAGE_USERS_EVENTS_CLUSTER`| 1.0.0 |string|`The clusterID of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture. Mandatory when using NATS as event system.`|`opencloud-cluster`|
+|`OC_INSECURE`<br/>`OC_EVENTS_TLS_INSECURE`<br/>`STORAGE_USERS_EVENTS_TLS_INSECURE`| 1.0.0 |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_EVENTS_TLS_ROOT_CA_CERTIFICATE`<br/>`STORAGE_USERS_EVENTS_TLS_ROOT_CA_CERTIFICATE`| 1.0.0 |string|`The root CA certificate used to validate the server's TLS certificate. If provided STORAGE_USERS_EVENTS_TLS_INSECURE will be seen as false.`|``|
+|`OC_EVENTS_ENABLE_TLS`<br/>`STORAGE_USERS_EVENTS_ENABLE_TLS`| 1.0.0 |bool|`Enable TLS for the connection to the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|`false`|
+|`STORAGE_USERS_EVENTS_NUM_CONSUMERS`| 1.0.0 |int|`The amount of concurrent event consumers to start. Event consumers are used for post-processing files. Multiple consumers increase parallelisation, but will also increase CPU and memory demands. The setting has no effect when the OC_ASYNC_UPLOADS is set to false. The default and minimum value is 1.`|`0`|
+|`OC_EVENTS_AUTH_USERNAME`<br/>`STORAGE_USERS_EVENTS_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_EVENTS_AUTH_PASSWORD`<br/>`STORAGE_USERS_EVENTS_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_CACHE_STORE`<br/>`STORAGE_USERS_FILEMETADATA_CACHE_STORE`| 1.0.0 |string|`The type of the cache store. Supported values are: 'memory', 'redis-sentinel', 'nats-js-kv', 'noop'. See the text description for details.`|`memory`|
+|`OC_CACHE_STORE_NODES`<br/>`STORAGE_USERS_FILEMETADATA_CACHE_STORE_NODES`| 1.0.0 |[]string|`A list of nodes to access the configured store. This has no effect when 'memory' store is configured. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details.`|`[127.0.0.1:9233]`|
+|`OC_CACHE_DATABASE`<br/>`STORAGE_USERS_FILEMETADATA_CACHE_DATABASE`| 1.0.0 |string|`The database name the configured store should use.`|`storage-users`|
+|`OC_CACHE_TTL`<br/>`STORAGE_USERS_FILEMETADATA_CACHE_TTL`| 1.0.0 |Duration|`Default time to live for user info in the user info cache. Only applied when access tokens has no expiration. See the Environment Variable Types description for more details.`|`24h0m0s`|
+|`OC_CACHE_DISABLE_PERSISTENCE`<br/>`STORAGE_USERS_FILEMETADATA_CACHE_DISABLE_PERSISTENCE`| 1.0.0 |bool|`Disables persistence of the cache. Only applies when store type 'nats-js-kv' is configured. Defaults to false.`|`false`|
+|`OC_CACHE_AUTH_USERNAME`<br/>`STORAGE_USERS_FILEMETADATA_CACHE_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the cache store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_CACHE_AUTH_PASSWORD`<br/>`STORAGE_USERS_FILEMETADATA_CACHE_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the cache store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_CACHE_ENABLE_TLS`<br/>`STORAGE_USERS_FILEMETADATA_CACHE_ENABLE_TLS`| next |bool|`Enable TLS for the connection to file metadata cache.`|`false`|
+|`OC_INSECURE`<br/>`OC_CACHE_TLS_INSECURE`<br/>`STORAGE_USERS_FILEMETADATA_CACHE_TLS_INSECURE`| next |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_CACHE_TLS_ROOT_CA_CERTIFICATE`<br/>`STORAGE_USERS_FILEMETADATA_CACHE_TLS_ROOT_CA_CERTIFICATE`| next |string|`The root CA certificate used to validate the server's TLS certificate. If provided STORAGE_USERS_FILEMETADATA_CACHE_TLS_INSECURE will be seen as false.`|``|
+|`OC_CACHE_STORE`<br/>`STORAGE_USERS_ID_CACHE_STORE`| 1.0.0 |string|`The type of the cache store. Supported values are: 'memory', 'redis-sentinel', 'nats-js-kv', 'noop'. See the text description for details.`|`nats-js-kv`|
+|`OC_CACHE_STORE_NODES`<br/>`STORAGE_USERS_ID_CACHE_STORE_NODES`| 1.0.0 |[]string|`A list of nodes to access the configured store. This has no effect when 'memory' store is configured. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details.`|`[127.0.0.1:9233]`|
+|`OC_CACHE_DATABASE`| 1.0.0 |string|`The database name the configured store should use.`|`ids-storage-users`|
+|`OC_CACHE_TTL`<br/>`STORAGE_USERS_ID_CACHE_TTL`| 1.0.0 |Duration|`Default time to live for user info in the user info cache. Only applied when access tokens have no expiration. Defaults to 300s which is derived from the underlaying package though not explicitly set as default. See the Environment Variable Types description for more details.`|`0s`|
+|`OC_CACHE_DISABLE_PERSISTENCE`<br/>`STORAGE_USERS_ID_CACHE_DISABLE_PERSISTENCE`| 1.0.0 |bool|`Disables persistence of the cache. Only applies when store type 'nats-js-kv' is configured. Defaults to false.`|`false`|
+|`OC_CACHE_AUTH_USERNAME`<br/>`STORAGE_USERS_ID_CACHE_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the cache store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_CACHE_AUTH_PASSWORD`<br/>`STORAGE_USERS_ID_CACHE_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the cache store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_CACHE_ENABLE_TLS`<br/>`STORAGE_USERS_ID_CACHE_ENABLE_TLS`| next |bool|`Enable TLS for the connection to file metadata cache.`|`false`|
+|`OC_INSECURE`<br/>`OC_CACHE_TLS_INSECURE`<br/>`STORAGE_USERS_ID_CACHE_TLS_INSECURE`| next |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_CACHE_TLS_ROOT_CA_CERTIFICATE`<br/>`STORAGE_USERS_ID_CACHE_TLS_ROOT_CA_CERTIFICATE`| next |string|`The root CA certificate used to validate the server's TLS certificate. If provided STORAGE_USERS_ID_CACHE_TLS_INSECURE will be seen as false.`|``|
+|`STORAGE_USERS_MOUNT_ID`| 1.0.0 |string|`Mount ID of this storage.`|``|
+|`STORAGE_USERS_EXPOSE_DATA_SERVER`| 1.0.0 |bool|`Exposes the data server directly to users and bypasses the data gateway. Ensure that the data server address is reachable by users.`|`false`|
+|`STORAGE_USERS_READ_ONLY`| 1.0.0 |bool|`Set this storage to be read-only.`|`false`|
+|`STORAGE_USERS_UPLOAD_EXPIRATION`| 1.0.0 |int64|`Duration in seconds after which uploads will expire. Note that when setting this to a low number, uploads could be cancelled before they are finished and return a 403 to the user.`|`86400`|
+|`OC_ADMIN_USER_ID`<br/>`STORAGE_USERS_PURGE_TRASH_BIN_USER_ID`| 1.0.0 |string|`ID of the user who collects all necessary information for deletion. Consider that the UUID can be encoded in some LDAP deployment configurations like in .ldif files. These need to be decoded beforehand.`|``|
+|`STORAGE_USERS_PURGE_TRASH_BIN_PERSONAL_DELETE_BEFORE`| 1.0.0 |Duration|`Specifies the period of time in which items that have been in the personal trash-bin for longer than this value should be deleted. A value of 0 means no automatic deletion. See the Environment Variable Types description for more details.`|`720h0m0s`|
+|`STORAGE_USERS_PURGE_TRASH_BIN_PROJECT_DELETE_BEFORE`| 1.0.0 |Duration|`Specifies the period of time in which items that have been in the project trash-bin for longer than this value should be deleted. A value of 0 means no automatic deletion. See the Environment Variable Types description for more details.`|`720h0m0s`|
+|`OC_SERVICE_ACCOUNT_ID`<br/>`STORAGE_USERS_SERVICE_ACCOUNT_ID`| 1.0.0 |string|`The ID of the service account the service should use. See the 'auth-service' service description for more details.`|``|
+|`OC_SERVICE_ACCOUNT_SECRET`<br/>`STORAGE_USERS_SERVICE_ACCOUNT_SECRET`| 1.0.0 |string|`The service account secret.`|``|
+|`OC_GATEWAY_GRPC_ADDR`<br/>`STORAGE_USERS_GATEWAY_GRPC_ADDR`| 1.0.0 |string|`The bind address of the gateway GRPC address.`|`127.0.0.1:9142`|
+|`OC_MACHINE_AUTH_API_KEY`<br/>`STORAGE_USERS_MACHINE_AUTH_API_KEY`| 1.0.0 |string|`Machine auth API key used to validate internal requests necessary for the access to resources from other services.`|``|
+|`STORAGE_USERS_CLI_MAX_ATTEMPTS_RENAME_FILE`| 1.0.0 |int|`The maximum number of attempts to rename a file when a user restores a file to an existing destination with the same name. The minimum value is 100.`|`0`|
diff --git a/versioned_docs/version-7.x/_static/env-vars/storage-users_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/storage-users_deprecation.md
new file mode 100644
index 000000000..c59cea0de
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/storage-users_deprecation.md
@@ -0,0 +1,4 @@
+
+:::danger
+storage-users has deprecated environment variables. Please refer to the table below for more information.
+:::
\ No newline at end of file
diff --git a/versioned_docs/version-7.x/_static/env-vars/storage-users_readme.md b/versioned_docs/version-7.x/_static/env-vars/storage-users_readme.md
new file mode 100755
index 000000000..767ef7558
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/storage-users_readme.md
@@ -0,0 +1,246 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+Purpose and description to be added
+
+
+## Table of Contents
+
+* [Graceful Shutdown](#graceful-shutdown)
+* [CLI Commands](#cli-commands)
+  * [Manage Unfinished Uploads](#manage-unfinished-uploads)
+    * [Sessions command](#sessions-command)
+    * [Command Examples](#command-examples)
+  * [Manage Trash-Bin Items](#manage-trashbin-items)
+    * [Purge Expired](#purge-expired)
+    * [List and Restore Trash-Bins Items](#list-and-restore-trashbins-items)
+* [Caching](#caching)
+
+## Graceful Shutdown
+
+You can define a graceful shutdown period for the `storage-users` service.
+
+IMPORTANT: The graceful shutdown period is only applicable if the `storage-users` service runs as standalone service. It does not apply if the `storage-users` service runs as part of the single binary or as single Docker environment. To build an environment where the `storage-users` service runs as a standalone service, you must start two instances, one _without_ the `storage-users` service and one _only with_ the the `storage-users` service. Note that both instances must be able to communicate on the same network.
+
+When hard-stopping OpenCloud, for example with the `kill <pid>` command (SIGKILL), it is possible and likely that not all data from the decomposedfs (metadata) has been written to the storage which may result in an inconsistent decomposedfs. When gracefully shutting down OpenCloud, using a command like SIGTERM, the process will no longer accept any write requests from _other_ services and will try to write the internal open  requests which can take an undefined duration based on many factors. To mitigate that situation, the following things have been implemented:
+
+*   With the value of the environment variable `STORAGE_USERS_GRACEFUL_SHUTDOWN_TIMEOUT`, the `storage-users` service will delay its shutdown giving it time to finalize writing necessary data. This delay can be necessary if there is a lot of data to be saved and/or if storage access/thruput is slow. In such a case you would receive an error log entry informing you that not all data could be saved in time. To prevent such occurrences, you must increase the default value.
+
+*   If a shutdown error has been logged, the command-line maintenance tool to inspect and manipulate node metadata can help to fix the issue. Please contact support for details.
+
+## CLI Commands
+
+For any command listed, use `--help` to get more details and possible options and arguments.
+
+To authenticate CLI commands use:
+
+*   `OC_SERVICE_ACCOUNT_SECRET=<acc-secret>` and
+*   `OC_SERVICE_ACCOUNT_ID=<acc-id>`.
+
+The `storage-users` CLI tool uses the default address to establish the connection to the `gateway` service. If the connection fails, check your custom `gateway` service `GATEWAY_GRPC_ADDR` configuration and set the same address in `storage-users` `OC_GATEWAY_GRPC_ADDR` or `STORAGE_USERS_GATEWAY_GRPC_ADDR`.
+
+### Manage Unfinished Uploads
+
+<!-- referencing: [oCIS FS] clean up aborted uploads https://github.com/owncloud/ocis/issues/2622 -->
+
+When using OpenCloud as user storage, a directory named `storage/users/uploads` can be found in the OpenCloud data folder. This is an intermediate directory based on [TUS](https://tus.io) which is an open protocol for resumable uploads. Each upload consists of a _blob_ and a _blob.info_ file. Note that the term _blob_ is just a placeholder.
+
+*   **If an upload succeeds**, the _blob_ file will be moved to the target and the _blob.info_ file will be deleted.
+
+*   **In case of incomplete uploads**, the _blob_ and _blob.info_ files will continue to receive data until either the upload succeeds in time or the upload expires based on the `STORAGE_USERS_UPLOAD_EXPIRATION` variable, see the table below for details.
+
+*   **In case of expired uploads**, the _blob_ and _blob.info_ files will _not_ be removed automatically. Thus a lot of data can pile up over time wasting storage space.
+
+*   **In the rare case of a failure**, after the upload succeeded but the file was not moved to its target location, which can happen when postprocessing fails, the situation is the same as with expired uploads.
+
+Example cases for expired uploads:
+
+*   When a user uploads a big file but the file exceeds the user-quota, the upload can't be moved to the target after it has finished. The file stays at the upload location until it is manually cleared.
+
+*   If the bandwidth is limited and the file to transfer can't be transferred completely before the upload expiration time is reached, the file expires and can't be processed.
+
+*   If the upload was technically successful, but the postprocessing step failed due to an internal error, it will not get further processed. See the procedure **Resume Post-Processing** in the `postprocessing` service documentation for details how to solve this.
+
+The following commands are available to manage unfinished uploads:
+
+```bash
+opencloud storage-users uploads <command>
+```
+
+```plaintext
+COMMANDS:
+   sessions   Print a list of upload sessions
+```
+
+#### Sessions command
+
+The `sessions` command is the entry point for listing, restarting and cleaning unfinished uploads.
+
+**IMPORTANT**
+> If not noted otherwise, commands with the `restart` option can also use the `resume` option. This changes behaviour slightly.
+>
+> * `restart`\
+> When restarting an upload, all steps for open items will be restarted, except if otherwise defined.
+> * `resume`\
+> When resuming an upload, processing will continue unfinished items from their last completed step.
+
+```bash
+opencloud storage-users uploads sessions <commandoptions>
+```
+
+```
+NAME:
+   opencloud storage-users uploads sessions - Print a list of upload sessions
+
+USAGE:
+   opencloud storage-users uploads sessions [command options]
+
+OPTIONS:
+   --id value    filter sessions by upload session id (default: unset)
+   --processing  filter sessions by processing status (default: unset)
+   --expired     filter sessions by expired status (default: unset)
+   --has-virus   filter sessions by virus scan result (default: unset)
+   --json        output as json (default: false)
+   --restart     send restart event for all listed sessions (default: false)
+   --resume      send resume event for all listed sessions (default: false)
+   --clean       remove uploads (default: false)
+   --help, -h    show help
+```
+
+This will always output a list of uploads that match the criteria. See Command Examples section.
+
+Some additional information on returned information:
+  -  `Offset` is the amount of bytes the server has already received. If `Offset` == `Size` the server has reveived all bytes of the upload.
+  -  `Processing` indicates if the uploaded file is currently going through postprocessing.
+  -  `Scan Date` and `Scan Result` indicate the scanning status. If `Scan Date` is set and `Scan Result` is empty the file is not virus infected.
+
+#### Command Examples
+
+Command to list ongoing upload sessions
+
+```bash
+opencloud storage-users uploads sessions --expired=false --processing=false
+```
+
+```plaintext
+Not expired sessions:
++--------------------------------------+--------------------------------------+---------+--------+------+--------------------------------------+--------------------------------------+---------------------------+------------+---------------------------+-----------------------+
+|                Space                 |              Upload Id               |  Name   | Offset | Size |              Executant               |                Owner                 |          Expires          | Processing |         Scan Date         |      Scan Result      |
++--------------------------------------+--------------------------------------+---------+--------+------+--------------------------------------+--------------------------------------+---------------------------+------------+---------------------------+-----------------------+
+| f7fbf8c8-139b-4376-b307-cf0a8c2d0d9c | 5e387954-7313-4223-a904-bf996da6ec0b | foo.txt |      0 | 1234 | f7fbf8c8-139b-4376-b307-cf0a8c2d0d9c | f7fbf8c8-139b-4376-b307-cf0a8c2d0d9c | 2024-01-26T13:04:31+01:00 | false      | 2024-04-24T11:24:14+02:00 |   infected: virus A   |
+| f7fbf8c8-139b-4376-b307-cf0a8c2d0d9c | f066244d-97b2-48e7-a30d-b40fcb60cec6 | bar.txt |      0 | 4321 | f7fbf8c8-139b-4376-b307-cf0a8c2d0d9c | f7fbf8c8-139b-4376-b307-cf0a8c2d0d9c | 2024-01-26T13:18:47+01:00 | false      | 2024-04-24T14:38:29+02:00 |                       |
++--------------------------------------+--------------------------------------+---------+--------+------+--------------------------------------+--------------------------------------+---------------------------+------------+---------------------------+-----------------------+
+```
+
+The sessions command can also output json
+
+```bash
+opencloud storage-users uploads sessions --expired=false --processing=false --json
+```
+
+```json
+{"id":"5e387954-7313-4223-a904-bf996da6ec0b","space":"f7fbf8c8-139b-4376-b307-cf0a8c2d0d9c","filename":"foo.txt","offset":0,"size":1234,"executant":{"idp":"https://cloud.opencloud.test","opaque_id":"f7fbf8c8-139b-4376-b307-cf0a8c2d0d9c"},"spaceowner":{"opaque_id":"f7fbf8c8-139b-4376-b307-cf0a8c2d0d9c"},"expires":"2024-01-26T13:04:31+01:00","processing":false, "scanDate": "2024-04-24T11:24:14+02:00", "scanResult": "infected: virus A"}
+{"id":"f066244d-97b2-48e7-a30d-b40fcb60cec6","space":"f7fbf8c8-139b-4376-b307-cf0a8c2d0d9c","filename":"bar.txt","offset":0,"size":4321,"executant":{"idp":"https://cloud.opencloud.test","opaque_id":"f7fbf8c8-139b-4376-b307-cf0a8c2d0d9c"},"spaceowner":{"opaque_id":"f7fbf8c8-139b-4376-b307-cf0a8c2d0d9c"},"expires":"2024-01-26T13:18:47+01:00","processing":false, "scanDate": "2024-04-24T14:38:29+02:00", "scanResult": ""}
+```
+
+The sessions command can also clear and restart/resume uploads. The output is the same as if run without `--clean` or `--restart` flag.
+Note: It is recommended to run to command first without the `--clean` (`--processing`) flag to double check which uploads get cleaned (restarted/resumed).
+
+```bash
+# cleans all expired uploads regardless of processing and virus state.
+opencloud storage-users uploads sessions --expired=true --clean
+
+# resumes all uploads that are processing and are not virus infected
+opencloud storage-users uploads sessions --processing=false --has-virus=false --resume
+```
+
+### Manage Trash-Bin Items
+
+This command set provides commands to get an overview of trash-bin items, restore items and purge old items of `personal` spaces and `project` spaces (spaces that have been created manually). `trash-bin` commands require a `spaceID` as parameter. 
+
+```bash
+opencloud storage-users trash-bin <command>
+```
+
+```plaintext
+COMMANDS:
+   purge-expired  Purge expired trash-bin items
+   list           Print a list of all trash-bin items of a space.
+   restore-all    Restore all trash-bin items for a space.
+   restore        Restore a trash-bin item by ID.
+```
+
+#### Purge Expired
+
+*   Purge all expired items from the trash-bin.
+    ```bash
+    opencloud storage-users trash-bin purge-expired
+    ```
+
+The behaviour of the `purge-expired` command can be configured by using the following environment variables.
+
+*   `STORAGE_USERS_PURGE_TRASH_BIN_USER_ID`\
+Used to obtain space trash-bin information and takes the system admin user as the default which is the `OC_ADMIN_USER_ID` but can be set individually. It should be noted, that the `OC_ADMIN_USER_ID` is only assigned automatically when using the single binary deployment and must be manually assigned in all other deployments. The command only considers spaces to which the assigned user has access and delete permission.
+
+*   `STORAGE_USERS_PURGE_TRASH_BIN_PERSONAL_DELETE_BEFORE`\
+Has a default value of `720h` which equals `30 days`. This means, the command will delete all files older than `30 days`. The value is human-readable. A value of `0` is equivalent to disable and prevents the deletion of `personal space` trash-bin files.
+
+*   `STORAGE_USERS_PURGE_TRASH_BIN_PROJECT_DELETE_BEFORE`\
+Has a default value of `720h` which equals `30 days`. This means, the command will delete all files older than `30 days`. The value is human-readable. A value of `0` is equivalent to disable and prevents the deletion of `project space` trash-bin files.
+
+#### List and Restore Trash-Bins Items
+
+Restoring is possible only to the original location. The personal or project `spaceID` is required for the items to be restored. To authenticate the CLI tool use:
+
+```bash
+OC_SERVICE_ACCOUNT_SECRET=<acc-secret>
+OC_SERVICE_ACCOUNT_ID=<acc-id>
+```
+
+The `storage-users` CLI tool uses the default address to establish the connection to the `gateway` service. If the connection fails, check the `GATEWAY_GRPC_ADDR` configuration from your `gateway` service and set the same address to the `storage-users` variable `STORAGE_USERS_GATEWAY_GRPC_ADDR` or globally with `OC_GATEWAY_GRPC_ADDR`.
+
+*   Export the gateway address if your configuration differs from the default
+    ```bash
+    export STORAGE_USERS_GATEWAY_GRPC_ADDR=127.0.0.1:9142
+    ```
+
+*   Print a list of all trash-bin items of a space
+    ```bash
+    opencloud storage-users trash-bin list [command options] ['spaceID' required]
+    ```
+
+The restore option defines the behavior for an item to be restored, when the item name already exists in the target space. Supported options are: `skip`, `replace` and `keep-both`. The default value is `skip`.
+
+When the CLI tool restores the item with the `replace` option, the existing item will be moved to a trash-bin. When the CLI tool restores the item with the `keep-both` option and the designated item already exists, the name of the restored item will be changed by adding a numeric suffix in parentheses. The variable `STORAGE_USERS_CLI_MAX_ATTEMPTS_RENAME_FILE` defines a maximum number of attempts to rename an item.
+
+* Restore all trash-bin items for a space
+    ```bash
+    opencloud storage-users trash-bin restore-all [command options] ['spaceID' required]
+    ```
+
+* Restore a trash-bin item by ID
+    ```bash
+    opencloud storage-users trash-bin restore [command options] ['spaceID' required] ['itemID' required]
+    ```
+
+## Caching
+
+The `storage-users` service caches stat, metadata and uuids of files and folders via the configured store in `STORAGE_USERS_FILEMETADATA_CACHE_STORE` and `STORAGE_USERS_ID_CACHE_STORE`. Possible stores are:
+  -   `memory`: Basic in-memory store and the default.
+  -   `redis-sentinel`: Stores data in a configured Redis Sentinel cluster.
+  -   `nats-js-kv`: Stores data using key-value-store feature of [nats jetstream](https://docs.nats.io/nats-concepts/jetstream/key-value-store)
+  -   `noop`: Stores nothing. Useful for testing. Not recommended in production environments.
+
+Other store types may work but are not supported currently.
+
+Note: The service can only be scaled if not using `memory` store and the stores are configured identically over all instances!
+
+Note that if you have used one of the deprecated stores, you should reconfigure to one of the supported ones as the deprecated stores will be removed in a later version.
+
+Store specific notes:
+  -   When using `redis-sentinel`, the Redis master to use is configured via e.g. `OC_CACHE_STORE_NODES` in the form of `<sentinel-host>:<sentinel-port>/<redis-master>` like `10.10.0.200:26379/mymaster`.
+  -   When using `nats-js-kv` it is recommended to set `OC_CACHE_STORE_NODES` to the same value as `OC_EVENTS_ENDPOINT`. That way the cache uses the same nats instance as the event bus.
+  -   When using the `nats-js-kv` store, it is possible to set `OC_CACHE_DISABLE_PERSISTENCE` to instruct nats to not persist cache data on disc.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/thumbnails.yaml b/versioned_docs/version-7.x/_static/env-vars/thumbnails.yaml
new file mode 100644
index 000000000..c9da4da23
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/thumbnails.yaml
@@ -0,0 +1,63 @@
+# Autogenerated
+# Filename: thumbnails.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9189
+  token: ""
+  pprof: false
+  zpages: false
+grpc:
+  addr: 127.0.0.1:9185
+  tls: null
+  max_concurrent_requests: 0
+http:
+  addr: 127.0.0.1:9186
+  tls:
+    enabled: false
+    cert: ""
+    key: ""
+  root: /thumbnails
+  cors:
+    allow_origins:
+    - '*'
+    allow_methods:
+    - GET
+    - POST
+    - PUT
+    - PATCH
+    - DELETE
+    - OPTIONS
+    allow_headers:
+    - Authorization
+    - Origin
+    - Content-Type
+    - Accept
+    - X-Requested-With
+    - X-Request-Id
+    - Cache-Control
+    allow_credentials: true
+grpc_client_tls: null
+thumbnail:
+  resolutions:
+  - 16x16
+  - 32x32
+  - 64x64
+  - 128x128
+  - 1080x1920
+  - 1920x1080
+  - 2160x3840
+  - 3840x2160
+  - 4320x7680
+  - 7680x4320
+  filesystem_storage:
+    root_directory: /var/lib/opencloud/thumbnails
+  webdav_allow_insecure: false
+  cs3_allow_insecure: false
+  reva_gateway: eu.opencloud.api.gateway
+  font_map_file: ""
+  transfer_secret: ""
+  data_endpoint: http://127.0.0.1:9186/thumbnails/data
+  max_input_width: 7680
+  max_input_height: 7680
+  max_input_image_file_size: 50MB
diff --git a/versioned_docs/version-7.x/_static/env-vars/thumbnails_configvars.md b/versioned_docs/version-7.x/_static/env-vars/thumbnails_configvars.md
new file mode 100644
index 000000000..fbcc65fec
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/thumbnails_configvars.md
@@ -0,0 +1,31 @@
+## Environment variables for the **thumbnails** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`THUMBNAILS_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`THUMBNAILS_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9189`|
+|`THUMBNAILS_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`THUMBNAILS_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`THUMBNAILS_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`THUMBNAILS_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9185`|
+|`THUMBNAILS_MAX_CONCURRENT_REQUESTS`| 1.0.0 |int|`Number of maximum concurrent thumbnail requests. Default is 0 which is unlimited.`|`0`|
+|`THUMBNAILS_HTTP_ADDR`| 1.0.0 |string|`The bind address of the HTTP service.`|`127.0.0.1:9186`|
+|`OC_HTTP_TLS_ENABLED`| 1.0.0 |bool|`Activates TLS for the http based services using the server certifcate and key configured via OC_HTTP_TLS_CERTIFICATE and OC_HTTP_TLS_KEY. If OC_HTTP_TLS_CERTIFICATE is not set a temporary server certificate is generated - to be used with PROXY_INSECURE_BACKEND=true.`|`false`|
+|`OC_HTTP_TLS_CERTIFICATE`| 1.0.0 |string|`Path/File name of the TLS server certificate (in PEM format) for the http services.`|``|
+|`OC_HTTP_TLS_KEY`| 1.0.0 |string|`Path/File name for the TLS certificate key (in PEM format) for the server certificate to use for the http services.`|``|
+|`THUMBNAILS_HTTP_ROOT`| 1.0.0 |string|`Subdirectory that serves as the root for this HTTP service.`|`/thumbnails`|
+|`OC_CORS_ALLOW_ORIGINS`<br/>`THUMBNAILS_CORS_ALLOW_ORIGINS`| 1.0.0 |[]string|`A list of allowed CORS origins. See following chapter for more details: *Access-Control-Allow-Origin* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin. See the Environment Variable Types description for more details.`|`[*]`|
+|`OC_CORS_ALLOW_METHODS`<br/>`THUMBNAILS_CORS_ALLOW_METHODS`| 1.0.0 |[]string|`A list of allowed CORS methods. See following chapter for more details: *Access-Control-Request-Method* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Method. See the Environment Variable Types description for more details.`|`[GET POST PUT PATCH DELETE OPTIONS]`|
+|`OC_CORS_ALLOW_HEADERS`<br/>`THUMBNAILS_CORS_ALLOW_HEADERS`| 1.0.0 |[]string|`A list of allowed CORS headers. See following chapter for more details: *Access-Control-Request-Headers* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Headers. See the Environment Variable Types description for more details.`|`[Authorization Origin Content-Type Accept X-Requested-With X-Request-Id Cache-Control]`|
+|`OC_CORS_ALLOW_CREDENTIALS`<br/>`THUMBNAILS_CORS_ALLOW_CREDENTIALS`| 1.0.0 |bool|`Allow credentials for CORS.See following chapter for more details: *Access-Control-Allow-Credentials* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Credentials.`|`true`|
+|`THUMBNAILS_RESOLUTIONS`| 1.0.0 |[]string|`The supported list of target resolutions in the format WidthxHeight like 32x32. You can define any resolution as required. See the Environment Variable Types description for more details.`|`[16x16 32x32 64x64 128x128 1080x1920 1920x1080 2160x3840 3840x2160 4320x7680 7680x4320]`|
+|`THUMBNAILS_FILESYSTEMSTORAGE_ROOT`| 1.0.0 |string|`The directory where the filesystem storage will store the thumbnails. If not defined, the root directory derives from $OC_BASE_DATA_PATH/thumbnails.`|`/var/lib/opencloud/thumbnails`|
+|`OC_INSECURE`<br/>`THUMBNAILS_WEBDAVSOURCE_INSECURE`| 1.0.0 |bool|`Ignore untrusted SSL certificates when connecting to the webdav source.`|`false`|
+|`OC_INSECURE`<br/>`THUMBNAILS_CS3SOURCE_INSECURE`| 1.0.0 |bool|`Ignore untrusted SSL certificates when connecting to the CS3 source.`|`false`|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`CS3 gateway used to look up user metadata`|`eu.opencloud.api.gateway`|
+|`THUMBNAILS_TXT_FONTMAP_FILE`| 1.0.0 |string|`The path to a font file for txt thumbnails.`|``|
+|`THUMBNAILS_TRANSFER_TOKEN`| 1.0.0 |string|`The secret to sign JWT to download the actual thumbnail file.`|``|
+|`THUMBNAILS_DATA_ENDPOINT`| 1.0.0 |string|`The HTTP endpoint where the actual thumbnail file can be downloaded.`|`http://127.0.0.1:9186/thumbnails/data`|
+|`THUMBNAILS_MAX_INPUT_WIDTH`| 1.0.0 |int|`The maximum width of an input image which is being processed.`|`7680`|
+|`THUMBNAILS_MAX_INPUT_HEIGHT`| 1.0.0 |int|`The maximum height of an input image which is being processed.`|`7680`|
+|`THUMBNAILS_MAX_INPUT_IMAGE_FILE_SIZE`| 1.0.0 |string|`The maximum file size of an input image which is being processed. Usable common abbreviations: [KB, KiB, MB, MiB, GB, GiB, TB, TiB, PB, PiB, EB, EiB], example: 2GB.`|`50MB`|
diff --git a/versioned_docs/version-7.x/_static/env-vars/thumbnails_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/thumbnails_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/thumbnails_readme.md b/versioned_docs/version-7.x/_static/env-vars/thumbnails_readme.md
new file mode 100755
index 000000000..43500cb73
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/thumbnails_readme.md
@@ -0,0 +1,142 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The thumbnails service provides methods to generate thumbnails for various files and resolutions based on requests. It retrieves the sources at the location where the user files are stored and saves the thumbnails where system files are stored. Those locations have defaults but can be manually defined via environment variables.
+
+
+## Table of Contents
+
+* [File Locations Overview](#file-locations-overview)
+* [Thumbnail Location](#thumbnail-location)
+* [Thumbnail Source File Types](#thumbnail-source-file-types)
+* [Thumbnail Target File Types](#thumbnail-target-file-types)
+* [Thumbnail Query String Parameters](#thumbnail-query-string-parameters)
+* [Thumbnail Resolution](#thumbnail-resolution)
+* [Thumbnail Processors](#thumbnail-processors)
+* [Deleting Thumbnails](#deleting-thumbnails)
+* [Memory Considerations](#memory-considerations)
+* [Thumbnails and SecureView](#thumbnails-and-secureview)
+* [Using libvips for Thumbnail Generation](#using-libvips-for-thumbnail-generation)
+
+## File Locations Overview
+
+The relevant environment variables defining file locations are:
+
+-   (1) `OC_BASE_DATA_PATH`
+-   (2) `STORAGE_USERS_DECOMPOSED_ROOT`
+-   (3) `THUMBNAILS_FILESYSTEMSTORAGE_ROOT`
+
+(1) ... Having a default set by the OpenCloud code, but if defined, used as base path for other services.
+(2) ... Source files, defaults to (1) plus path component, but can be freely defined if required.
+(3) ... Target files, defaults to (1) plus path component, but can be freely defined if required.
+
+For details and defaults for these environment variables see the OpenCloud admin documentation.
+
+## Thumbnail Location
+
+It may be beneficial to define the location of the thumbnails to be other than the default (with system files). This is due the fact that storing thumbnails can consume a lot of space over time which not necessarily needs to reside on the same partition or mount or expensive drives.
+
+## Thumbnail Source File Types
+
+Thumbnails can be generated from the following source file types:
+
+-   png
+-   jpg
+-   gif
+-   tiff
+-   bmp
+-   txt
+
+The thumbnail service retrieves source files using the information provided by the backend. The Linux backend identifies source files usually based on the extension.
+
+If a file type was not properly assigned or the type identification failed, thumbnail generation will fail and an error will be logged.
+
+## Thumbnail Target File Types
+
+Thumbnails can either be generated as `png`, `jpg` or `gif` files. These types are hardcoded and no other types can be requested. A requestor, like another service or a client, can request one of the available types to be generated. If more than one type is required, each type must be requested individually.
+
+## Thumbnail Query String Parameters
+
+Clients can request thumbnail previews for files by adding `?preview=1` to the file URL. Requests for files with no thumbnail available respond with HTTP status `404`.
+
+The following query parameters are supported:
+
+| Parameter | Required | Default Value                                        | Description                                                                     |
+|-----------|----------|------------------------------------------------------|---------------------------------------------------------------------------------|
+| preview   | YES      | 1                                                    | generates preview                                                               |
+| x         | YES      | first x-value configured in `THUMBNAILS_RESOLUTIONS` | horizontal target size                                                          |
+| y         | YES      | first y-value configured in `THUMBNAILS_RESOLUTIONS` | vertical target size                                                            |
+| scalingup | NO       | 0                                                    | prevents up-scaling of small images                                             |
+| a         | NO       | 1                                                    | aspect ratio                                                                    |
+| c         | NO       | Caching string                                       | Clients should send the etag, so they get a fresh thumbnail after a file change |
+| processor | NO       | `resize` for gifs and `thumbnail` for all others     | preferred thumbnail processor                                                   |
+
+## Thumbnail Resolution
+
+Various resolutions can be defined via `THUMBNAILS_RESOLUTIONS`. A requestor can request any arbitrary resolution and the thumbnail service will use the one closest to the requested resolution. If more than one resolution is required, each resolution must be requested individually.
+
+Example:
+
+Requested: 18x12\
+Available: 30x20, 15x10, 9x6\
+Returned: 15x10
+
+## Thumbnail Processors
+
+Normally, an image might get cropped when creating a preview, depending on the aspect ratio of the original image. This can have negative
+impacts on previews as only a part of the image will be shown. When using an _optional_ processor in the request, cropping can be avoided by defining on how the preview image generation will be done. The following processors are available:
+
+*   `resize` resizes the image to the specified width and height and returns the transformed image. If one of width or height is 0, the image aspect ratio is preserved.
+*   `fit` scales down the image to fit the specified maximum width and height and returns the transformed image.
+*   `fill`: creates an image with the specified dimensions and fills it with the scaled source image. To achieve the correct aspect ratio without stretching, the source image will be cropped.
+*   `thumbnail` scales the image up or down, crops it to the specified width and height and returns the transformed image.
+
+To apply one of those, a query parameter has to be added to the request, like `?processor=fit`. If no query parameter or processor is added, the default behaviour applies which is `resize` for gifs and `thumbnail` for all others.
+
+## Deleting Thumbnails
+
+As of now, there is no automated thumbnail deletion. This is especially true when a source file gets deleted or moved. This situation will be solved at a later stage. For the time being, if you run short on physical thumbnails space, you have to manually delete the thumbnail store to free space. Thumbnails will then be recreated on request.
+
+## Memory Considerations
+
+Since source files need to be loaded into memory when generating thumbnails, large source files could potentially crash this service if there is insufficient memory available. For bigger instances when using container orchestration deployment methods, this service can be dedicated to its own server(s) with more memory.
+To have more control over memory (and CPU) consumption the maximum number of concurrent requests can be limited by setting the environment variable `THUMBNAILS_MAX_CONCURRENT_REQUESTS`. The default value is 0 which does not apply any restrictions to the number of concurrent requests. As soon as the number of concurrent requests is reached any further request will be responded with `429/Too Many Requests` and the client can retry at a later point in time.
+
+## Thumbnails and SecureView
+
+If a resource is shared using SecureView, the share reciever will get a 403 (forbidden) response when requesting a thumbnail. The requesting client needs to decide what to show and usually a placeholder thumbnail is used.
+
+## Using libvips for Thumbnail Generation
+
+To improve performance and to support a wider range of images formats, the thumbnails service is able to utilize the [libvips library](https://www.libvips.org/) for thumbnail generation. Support for libvips needs to be
+enabled at buildtime and has a couple of implications:
+
+*  With libvips support enabled, it is not possible to create a statically linked OpenCloud binary.
+*  Therefore, the libvips shared libraries need to be available at runtime in the same release that was used to build the OpenCloud binary.
+*  When using the OpenCloud docker images, the libvips shared libraries are included in the image and are correctly embedded.
+
+Support of libvips is disabled by default. To enable it, make sure libvips and its buildtime dependencies are installed in your build environment. For macOS users, add the build time dependencies via:
+
+```shell
+brew install vips pkg-config
+export PKG_CONFIG_PATH="/usr/local/opt/libffi/lib/pkgconfig"
+```
+
+Then you just need to set the `ENABLE_VIPS` variable on the `make` command:
+
+```shell
+make -C opencloud build ENABLE_VIPS=1
+```
+
+Or include the `enable_vips` build tag in the `go build` command:
+
+```shell
+go build -tags enable_vips -o opencloud -o bin/opencloud ./cmd/opencloud
+```
+
+When building a docker image using the Dockerfile in the top-level directory of OpenCloud, libvips support is enabled and the libvips shared libraries are included
+in the resulting docker image.
+
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/userlog.yaml b/versioned_docs/version-7.x/_static/env-vars/userlog.yaml
new file mode 100644
index 000000000..756fa70d8
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/userlog.yaml
@@ -0,0 +1,61 @@
+# Autogenerated
+# Filename: userlog.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9214
+  token: ""
+  pprof: false
+  zpages: false
+http:
+  addr: 127.0.0.1:9210
+  root: /
+  cors:
+    allow_origins:
+    - '*'
+    allow_methods:
+    - GET
+    allow_headers:
+    - Authorization
+    - Origin
+    - Content-Type
+    - Accept
+    - X-Requested-With
+    - X-Request-Id
+    - Ocs-Apirequest
+    allow_credentials: true
+  tls:
+    enabled: false
+    cert: ""
+    key: ""
+grpc_client_tls: null
+token_manager:
+  jwt_secret: ""
+reva_gateway: eu.opencloud.api.gateway
+translation_path: ""
+default_language: ""
+events:
+  endpoint: 127.0.0.1:9233
+  cluster: opencloud-cluster
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+  enable_tls: false
+  username: ""
+  password: ""
+max_concurrency: 1
+persistence:
+  store: memory
+  nodes: []
+  database: userlog
+  table: events
+  ttl: 336h0m0s
+  username: ""
+  password: ""
+  enable_tls: false
+  tls_insecure: false
+  tls_root_ca_certificate: ""
+disable_sse: false
+global_notifications_secret: ""
+service_account:
+  service_account_id: ""
+  service_account_secret: ""
diff --git a/versioned_docs/version-7.x/_static/env-vars/userlog_configvars.md b/versioned_docs/version-7.x/_static/env-vars/userlog_configvars.md
new file mode 100644
index 000000000..34ae372c4
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/userlog_configvars.md
@@ -0,0 +1,44 @@
+## Environment variables for the **userlog** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`USERLOG_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`USERLOG_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9214`|
+|`USERLOG_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`USERLOG_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`USERLOG_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`USERLOG_HTTP_ADDR`| 1.0.0 |string|`The bind address of the HTTP service.`|`127.0.0.1:9210`|
+|`USERLOG_HTTP_ROOT`| 1.0.0 |string|`Subdirectory that serves as the root for this HTTP service.`|`/`|
+|`OC_CORS_ALLOW_ORIGINS`<br/>`USERLOG_CORS_ALLOW_ORIGINS`| 1.0.0 |[]string|`A list of allowed CORS origins. See following chapter for more details: *Access-Control-Allow-Origin* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin. See the Environment Variable Types description for more details.`|`[*]`|
+|`OC_CORS_ALLOW_METHODS`<br/>`USERLOG_CORS_ALLOW_METHODS`| 1.0.0 |[]string|`A list of allowed CORS methods. See following chapter for more details: *Access-Control-Request-Method* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Method. See the Environment Variable Types description for more details.`|`[GET]`|
+|`OC_CORS_ALLOW_HEADERS`<br/>`USERLOG_CORS_ALLOW_HEADERS`| 1.0.0 |[]string|`A list of allowed CORS headers. See following chapter for more details: *Access-Control-Request-Headers* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Headers. See the Environment Variable Types description for more details.`|`[Authorization Origin Content-Type Accept X-Requested-With X-Request-Id Ocs-Apirequest]`|
+|`OC_CORS_ALLOW_CREDENTIALS`<br/>`USERLOG_CORS_ALLOW_CREDENTIALS`| 1.0.0 |bool|`Allow credentials for CORS.See following chapter for more details: *Access-Control-Allow-Credentials* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Credentials.`|`true`|
+|`OC_HTTP_TLS_ENABLED`| 1.0.0 |bool|`Activates TLS for the http based services using the server certifcate and key configured via OC_HTTP_TLS_CERTIFICATE and OC_HTTP_TLS_KEY. If OC_HTTP_TLS_CERTIFICATE is not set a temporary server certificate is generated - to be used with PROXY_INSECURE_BACKEND=true.`|`false`|
+|`OC_HTTP_TLS_CERTIFICATE`| 1.0.0 |string|`Path/File name of the TLS server certificate (in PEM format) for the http services.`|``|
+|`OC_HTTP_TLS_KEY`| 1.0.0 |string|`Path/File name for the TLS certificate key (in PEM format) for the server certificate to use for the http services.`|``|
+|`OC_JWT_SECRET`<br/>`USERLOG_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`CS3 gateway used to look up user metadata`|`eu.opencloud.api.gateway`|
+|`OC_TRANSLATION_PATH`<br/>`USERLOG_TRANSLATION_PATH`| 1.0.0 |string|`(optional) Set this to a path with custom translations to overwrite the builtin translations. Note that file and folder naming rules apply, see the documentation for more details.`|``|
+|`OC_DEFAULT_LANGUAGE`| 1.0.0 |string|`The default language used by services and the WebUI. If not defined, English will be used as default. See the documentation for more details.`|``|
+|`OC_EVENTS_ENDPOINT`<br/>`USERLOG_EVENTS_ENDPOINT`| 1.0.0 |string|`The address of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture.`|`127.0.0.1:9233`|
+|`OC_EVENTS_CLUSTER`<br/>`USERLOG_EVENTS_CLUSTER`| 1.0.0 |string|`The clusterID of the event system. The event system is the message queuing service. It is used as message broker for the microservice architecture. Mandatory when using NATS as event system.`|`opencloud-cluster`|
+|`OC_INSECURE`<br/>`OC_EVENTS_TLS_INSECURE`<br/>`USERLOG_EVENTS_TLS_INSECURE`| 1.0.0 |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_EVENTS_TLS_ROOT_CA_CERTIFICATE`<br/>`USERLOG_EVENTS_TLS_ROOT_CA_CERTIFICATE`| 1.0.0 |string|`The root CA certificate used to validate the server's TLS certificate. If provided NOTIFICATIONS_EVENTS_TLS_INSECURE will be seen as false.`|``|
+|`OC_EVENTS_ENABLE_TLS`<br/>`USERLOG_EVENTS_ENABLE_TLS`| 1.0.0 |bool|`Enable TLS for the connection to the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|`false`|
+|`OC_EVENTS_AUTH_USERNAME`<br/>`USERLOG_EVENTS_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_EVENTS_AUTH_PASSWORD`<br/>`USERLOG_EVENTS_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the events broker. The events broker is the OpenCloud service which receives and delivers events between the services.`|``|
+|`OC_MAX_CONCURRENCY`<br/>`USERLOG_MAX_CONCURRENCY`| 1.0.0 |int|`Maximum number of concurrent go-routines. Higher values can potentially get work done faster but will also cause more load on the system. Values of 0 or below will be ignored and the default value will be used.`|`1`|
+|`OC_PERSISTENT_STORE`<br/>`USERLOG_STORE`| 1.0.0 |string|`The type of the store. Supported values are: 'memory', 'nats-js-kv', 'redis-sentinel', 'noop'. See the text description for details.`|`memory`|
+|`OC_PERSISTENT_STORE_NODES`<br/>`USERLOG_STORE_NODES`| 1.0.0 |[]string|`A list of nodes to access the configured store. This has no effect when 'memory' store is configured. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details.`|`[]`|
+|`USERLOG_STORE_DATABASE`| 1.0.0 |string|`The database name the configured store should use.`|`userlog`|
+|`USERLOG_STORE_TABLE`| 1.0.0 |string|`The database table the store should use.`|`events`|
+|`OC_PERSISTENT_STORE_TTL`<br/>`USERLOG_STORE_TTL`| 1.0.0 |Duration|`Time to live for events in the store. Defaults to '336h' (2 weeks). See the Environment Variable Types description for more details.`|`336h0m0s`|
+|`OC_PERSISTENT_STORE_AUTH_USERNAME`<br/>`USERLOG_STORE_AUTH_USERNAME`| 1.0.0 |string|`The username to authenticate with the store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_PERSISTENT_STORE_AUTH_PASSWORD`<br/>`USERLOG_STORE_AUTH_PASSWORD`| 1.0.0 |string|`The password to authenticate with the store. Only applies when store type 'nats-js-kv' is configured.`|``|
+|`OC_PERSISTENT_STORE_ENABLE_TLS`<br/>`USERLOG_STORE_ENABLE_TLS`| next |bool|`Enable TLS for the connection to the store. Only applies when store type 'nats-js-kv' is configured.`|`false`|
+|`OC_INSECURE`<br/>`OC_PERSISTENT_STORE_TLS_INSECURE`<br/>`USERLOG_STORE_TLS_INSECURE`| next |bool|`Whether to verify the server TLS certificates.`|`false`|
+|`OC_PERSISTENT_STORE_TLS_ROOT_CA_CERTIFICATE`<br/>`USERLOG_STORE_TLS_ROOT_CA_CERTIFICATE`| next |string|`The root CA certificate used to validate the server's TLS certificate. If provided USERLOG_STORE_TLS_INSECURE will be seen as false.`|``|
+|`OC_DISABLE_SSE,USERLOG_DISABLE_SSE`| 1.0.0 |bool|`Disables server-sent events (sse). When disabled, clients will no longer receive sse notifications.`|`false`|
+|`USERLOG_GLOBAL_NOTIFICATIONS_SECRET`| 1.0.0 |string|`The secret to secure the global notifications endpoint. Only system admins and users knowing that secret can call the global notifications POST/DELETE endpoints.`|``|
+|`OC_SERVICE_ACCOUNT_ID`<br/>`USERLOG_SERVICE_ACCOUNT_ID`| 1.0.0 |string|`The ID of the service account the service should use. See the 'auth-service' service description for more details.`|``|
+|`OC_SERVICE_ACCOUNT_SECRET`<br/>`USERLOG_SERVICE_ACCOUNT_SECRET`| 1.0.0 |string|`The service account secret.`|``|
diff --git a/versioned_docs/version-7.x/_static/env-vars/userlog_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/userlog_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/userlog_readme.md b/versioned_docs/version-7.x/_static/env-vars/userlog_readme.md
new file mode 100755
index 000000000..1feed61fa
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/userlog_readme.md
@@ -0,0 +1,105 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The `userlog` service is a mediator between the `eventhistory` service and clients who want to be informed about user related events. It provides an API to retrieve those.
+
+
+## Table of Contents
+
+* [The Log Service Ecosystem](#the-log-service-ecosystem)
+* [Prerequisites](#prerequisites)
+* [Storing](#storing)
+* [Configuring](#configuring)
+* [Retrieving](#retrieving)
+* [Posting](#posting)
+  * [Authentication](#authentication)
+  * [Deprovisioning](#deprovisioning)
+* [Deleting](#deleting)
+* [Translations](#translations)
+  * [Translation Rules](#translation-rules)
+* [Default Language](#default-language)
+
+## The Log Service Ecosystem
+
+Log services like the `userlog`, `clientlog` and `sse` are responsible for composing notifications for a certain audience.
+  -   The `userlog` service translates and adjusts messages to be human readable.
+  -   The `clientlog` service composes machine readable messages, so clients can act without the need to query the server.
+  -   The `sse` service is only responsible for sending these messages. It does not care about their form or language.
+
+## Prerequisites
+
+Running the `userlog` service without running the `eventhistory` service is not possible.
+
+## Storing
+
+The `userlog` service persists information via the configured store in `USERLOG_STORE`. Possible stores are:
+  -   `memory`: Basic in-memory store and the default.
+  -   `redis-sentinel`: Stores data in a configured Redis Sentinel cluster.
+  -   `nats-js-kv`: Stores data using key-value-store feature of [nats jetstream](https://docs.nats.io/nats-concepts/jetstream/key-value-store)
+  -   `noop`: Stores nothing. Useful for testing. Not recommended in production environments.
+
+Other store types may work but are not supported currently.
+
+Note: The service can only be scaled if not using `memory` store and the stores are configured identically over all instances!
+
+Note that if you have used one of the deprecated stores, you should reconfigure to one of the supported ones as the deprecated stores will be removed in a later version.
+
+Store specific notes:
+  -   When using `redis-sentinel`, the Redis master to use is configured via e.g. `OC_CACHE_STORE_NODES` in the form of `<sentinel-host>:<sentinel-port>/<redis-master>` like `10.10.0.200:26379/mymaster`.
+  -   When using `nats-js-kv` it is recommended to set `OC_CACHE_STORE_NODES` to the same value as `OC_EVENTS_ENDPOINT`. That way the cache uses the same nats instance as the event bus.
+  -   When using the `nats-js-kv` store, it is possible to set `OC_CACHE_DISABLE_PERSISTENCE` to instruct nats to not persist cache data on disc.
+
+## Configuring
+
+For the time being, the configuration which user related events are of interest is hardcoded and cannot be changed.
+
+## Retrieving
+
+The `userlog` service provides an API to retrieve configured events. For now, this API is mostly following the [oc10 notification GET API](https://doc.owncloud.com/server/next/developer_manual/core/apis/ocs-notification-endpoint-v1.html#get-user-notifications).
+
+## Posting
+
+The userlog service is able to store global messages that will be displayed in the Web UI to all users. If a user deletes the message in the Web UI, it reappears on reload. Global messages use the endpoint `/ocs/v2.php/apps/notifications/api/v1/notifications/global` and are activated by sending a `POST` request. Note that sending another `POST` request of the same type overwrites the previous one. For the time being, only the type `deprovision` is supported.
+
+### Authentication
+
+`POST` and `DELETE` endpoints provide notifications to all users. Therefore only certain users can configure them. Two authentication methods for this endpoint are provided. Users with the `admin` role can always access these endpoints. Additionally, a static secret via the `USERLOG_GLOBAL_NOTIFICATIONS_SECRET` can be defined to enable access for users knowing this secret, which has to be sent with the header containing the request.
+
+### Deprovisioning
+
+Deprovision messages announce a deprovision text including a deprovision date of the instance to all users. With this message, users get informed that the instance will be shut down and deprovisioned and no further access to their data is possible past the given date. This implies that users must download their data before the given date. The text shown to users refers to this information. Note that the task to deprovision the instance does not depend on the message. The text of the message can be translated according to the translation settings, see section [Translations](#translations). The endpoint only expects a `deprovision_date` parameter in the `POST` request body as the final text is assembled automatically. The string hast to be in `RFC3339` format, however, this format can be changed by using `deprovision_date_format`. See the [go time formating](https://pkg.go.dev/time#pkg-constants) for more details.
+
+## Deleting
+
+To delete events for an user, use a `DELETE` request to `ocs/v2.php/apps/notifications/api/v1/notifications` containing the IDs to delete.
+
+Sending a `DELETE` request to the `ocs/v2.php/apps/notifications/api/v1/notifications/global` endpoint to remove a global message is a restricted action, see the [Authentication](#authentication) section for more details.)
+
+## Translations
+
+The `userlog` service has embedded translations sourced via transifex to provide a basic set of translated languages. These embedded translations are available for all deployment scenarios. In addition, the service supports custom translations, though it is currently not possible to just add custom translations to embedded ones. If custom translations are configured, the embedded ones are not used. To configure custom translations, the `USERLOG_TRANSLATION_PATH` environment variable needs to point to a base folder that will contain the translation files. This path must be available from all instances of the userlog service, a shared storage is recommended. Translation files must be of type  [.po](https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html#PO-Files) or [.mo](https://www.gnu.org/software/gettext/manual/html_node/Binaries.html). For each language, the filename needs to be `userlog.po` (or `userlog.mo`) and stored in a folder structure defining the language code. In general the path/name pattern for a translation file needs to be:
+
+```text
+{USERLOG_TRANSLATION_PATH}/{language-code}/LC_MESSAGES/userlog.po
+```
+
+The language code pattern is composed of `language[_territory]` where  `language` is the base language and `_territory` is optional and defines a country.
+
+For example, for the language `de`, one needs to place the corresponding translation files to `{USERLOG_TRANSLATION_PATH}/de_DE/LC_MESSAGES/userlog.po`.
+
+<!-- also see the notifications readme -->
+
+Important: For the time being, the embedded OpenCloud Web frontend only supports the main language code but does not handle any territory. When strings are available in the language code `language_territory`, the web frontend does not see it as it only requests `language`. In consequence, any translations made must exist in the requested `language` to avoid a fallback to the default.
+
+### Translation Rules
+
+*   If a requested language code is not available, the service tries to fall back to the base language if available. For example, if the requested language-code `de_DE` is not available, the service tries to fall back to translations in the `de` folder.
+*   If the base language `de` is also not available, the service falls back to the system's default English (`en`),
+which is the source of the texts provided by the code.
+
+## Default Language
+
+The default language can be defined via the `OC_DEFAULT_LANGUAGE` environment variable. See the `settings` service for a detailed description.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/users.yaml b/versioned_docs/version-7.x/_static/env-vars/users.yaml
new file mode 100644
index 000000000..d5a285577
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/users.yaml
@@ -0,0 +1,76 @@
+# Autogenerated
+# Filename: users.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9145
+  token: ""
+  pprof: false
+  zpages: false
+grpc:
+  addr: 127.0.0.1:9144
+  tls: null
+  protocol: tcp
+token_manager:
+  jwt_secret: ""
+reva:
+  address: eu.opencloud.api.gateway
+  tls:
+    mode: ""
+    cacert: ""
+skip_user_groups_in_token: false
+driver: ldap
+drivers:
+  ldap:
+    uri: ldap://localhost:9236
+    ca_cert: ""
+    insecure: false
+    bind_dn: uid=reva,ou=sysusers,o=libregraph-idm
+    bind_password: ""
+    user_base_dn: ou=users,o=libregraph-idm
+    group_base_dn: ou=groups,o=libregraph-idm
+    tenant_base_dn: ""
+    tenant_scope: sub
+    tenant_filter: ""
+    tenant_object_class: ""
+    tenant_schema:
+      id: ""
+      external_id: ""
+      name: ""
+    user_scope: sub
+    group_scope: sub
+    user_substring_filter_type: any
+    user_filter: ""
+    group_filter: ""
+    user_object_class: inetOrgPerson
+    group_object_class: groupOfNames
+    idp: https://localhost:9200
+    disable_user_mechanism: attribute
+    user_type_attribute: openCloudUserType
+    ldap_disabled_users_group_dn: cn=DisabledUsersGroup,ou=groups,o=libregraph-idm
+    user_schema:
+      id: openclouduuid
+      tenant_id: ""
+      id_is_octet_string: false
+      mail: mail
+      display_name: displayname
+      user_name: uid
+      user_enabled: openclouduserenabled
+    group_schema:
+      id: openclouduuid
+      id_is_octet_string: false
+      mail: mail
+      display_name: cn
+      group_name: cn
+      member: member
+  owncloudsql:
+    db_username: owncloud
+    db_password: secret
+    db_host: mysql
+    db_port: 3306
+    db_name: owncloud
+    idp: https://localhost:9200
+    nobody: 90
+    join_username: false
+    join_owncloud_uuid: false
+    enable_medial_search: false
diff --git a/versioned_docs/version-7.x/_static/env-vars/users_configvars.md b/versioned_docs/version-7.x/_static/env-vars/users_configvars.md
new file mode 100644
index 000000000..b60482f61
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/users_configvars.md
@@ -0,0 +1,65 @@
+## Environment variables for the **users** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`USERS_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`USERS_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9145`|
+|`USERS_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`USERS_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`USERS_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`USERS_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`127.0.0.1:9144`|
+|`OC_GRPC_PROTOCOL`<br/>`USERS_GRPC_PROTOCOL`| 1.0.0 |string|`The transport protocol of the GPRC service.`|`tcp`|
+|`OC_JWT_SECRET`<br/>`USERS_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`The CS3 gateway endpoint.`|`eu.opencloud.api.gateway`|
+|`OC_GRPC_CLIENT_TLS_MODE`| 1.0.0 |string|`TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification.`|``|
+|`OC_GRPC_CLIENT_TLS_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services.`|``|
+|`USERS_SKIP_USER_GROUPS_IN_TOKEN`| 1.0.0 |bool|`Disables the loading of user's group memberships from the reva access token.`|`false`|
+|`USERS_DRIVER`| 1.0.0 |string|`The driver which should be used by the users service. Supported values are 'ldap' and 'owncloudsql'.`|`ldap`|
+|`OC_LDAP_URI`<br/>`USERS_LDAP_URI`| 1.0.0 |string|`URI of the LDAP Server to connect to. Supported URI schemes are 'ldaps://' and 'ldap://'`|`ldap://localhost:9236`|
+|`OC_LDAP_CACERT`<br/>`USERS_LDAP_CACERT`| 1.0.0 |string|`Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the LDAP service. If not defined, the root directory derives from $OC_BASE_DATA_PATH/idm.`|``|
+|`OC_LDAP_INSECURE`<br/>`USERS_LDAP_INSECURE`| 1.0.0 |bool|`Disable TLS certificate validation for the LDAP connections. Do not set this in production environments.`|`false`|
+|`OC_LDAP_BIND_DN`<br/>`USERS_LDAP_BIND_DN`| 1.0.0 |string|`LDAP DN to use for simple bind authentication with the target LDAP server.`|`uid=reva,ou=sysusers,o=libregraph-idm`|
+|`OC_LDAP_BIND_PASSWORD`<br/>`USERS_LDAP_BIND_PASSWORD`| 1.0.0 |string|`Password to use for authenticating the 'bind_dn'.`|``|
+|`OC_LDAP_USER_BASE_DN`<br/>`USERS_LDAP_USER_BASE_DN`| 1.0.0 |string|`Search base DN for looking up LDAP users.`|`ou=users,o=libregraph-idm`|
+|`OC_LDAP_GROUP_BASE_DN`<br/>`USERS_LDAP_GROUP_BASE_DN`| 1.0.0 |string|`Search base DN for looking up LDAP groups.`|`ou=groups,o=libregraph-idm`|
+|`OC_LDAP_TENANT_BASE_DN`<br/>`USERS_LDAP_TENANT_BASE_DN`| 6.1.0 |string|`Search base DN for looking up LDAP tenants. Only relevant in multi-tenant setups.`|``|
+|`OC_LDAP_TENANT_SCOPE`<br/>`USERS_LDAP_TENANT_SCOPE`| 6.1.0 |string|`LDAP search scope to use when looking up tenants. Supported values are 'base', 'one' and 'sub'. Only relevant in multi-tenant setups.`|`sub`|
+|`OC_LDAP_TENANT_FILTER`<br/>`USERS_LDAP_TENANT_FILTER`| 6.1.0 |string|`LDAP filter to add to the default filters for tenant searches. Only relevant in multi-tenant setups.`|``|
+|`OC_LDAP_TENANT_OBJECTCLASS`<br/>`USERS_LDAP_TENANT_OBJECTCLASS`| 6.1.0 |string|`The object class to use for tenants in the default tenant search filter. Only relevant in multi-tenant setups.`|``|
+|`OC_LDAP_TENANT_SCHEMA_ID`<br/>`USERS_LDAP_TENANT_SCHEMA_ID`| 6.1.0 |string|`LDAP Attribute to use as the unique internal ID for tenants. Only relevant in multi-tenant setups.`|``|
+|`OC_LDAP_TENANT_SCHEMA_EXTERNAL_ID`<br/>`USERS_LDAP_TENANT_SCHEMA_EXTERNAL_ID`| 6.1.0 |string|`LDAP Attribute that holds the external tenant ID as it appears in OIDC claims. Only relevant in multi-tenant setups.`|``|
+|`OC_LDAP_TENANT_SCHEMA_NAME`<br/>`USERS_LDAP_TENANT_SCHEMA_NAME`| 6.1.0 |string|`LDAP Attribute to use for the human-readable name of a tenant. Only relevant in multi-tenant setups.`|``|
+|`OC_LDAP_USER_SCOPE`<br/>`USERS_LDAP_USER_SCOPE`| 1.0.0 |string|`LDAP search scope to use when looking up users. Supported values are 'base', 'one' and 'sub'.`|`sub`|
+|`OC_LDAP_GROUP_SCOPE`<br/>`USERS_LDAP_GROUP_SCOPE`| 1.0.0 |string|`LDAP search scope to use when looking up groups. Supported values are 'base', 'one' and 'sub'.`|`sub`|
+|`LDAP_USER_SUBSTRING_FILTER_TYPE`<br/>`USERS_LDAP_USER_SUBSTRING_FILTER_TYPE`| 1.0.0 |string|`Type of substring search filter to use for substring searches for users. Possible values: 'initial' for doing prefix only searches, 'final' for doing suffix only searches or 'any' for doing full substring searches`|`any`|
+|`OC_LDAP_USER_FILTER`<br/>`USERS_LDAP_USER_FILTER`| 1.0.0 |string|`LDAP filter to add to the default filters for user search like '(objectclass=openCloudUser)'.`|``|
+|`OC_LDAP_GROUP_FILTER`<br/>`USERS_LDAP_GROUP_FILTER`| 1.0.0 |string|`LDAP filter to add to the default filters for group searches.`|``|
+|`OC_LDAP_USER_OBJECTCLASS`<br/>`USERS_LDAP_USER_OBJECTCLASS`| 1.0.0 |string|`The object class to use for users in the default user search filter like 'inetOrgPerson'.`|`inetOrgPerson`|
+|`OC_LDAP_GROUP_OBJECTCLASS`<br/>`USERS_LDAP_GROUP_OBJECTCLASS`| 1.0.0 |string|`The object class to use for groups in the default group search filter like 'groupOfNames'.`|`groupOfNames`|
+|`OC_URL`<br/>`OC_OIDC_ISSUER`<br/>`USERS_IDP_URL`| 1.0.0 |string|`The identity provider value to set in the userids of the CS3 user objects for users returned by this user provider.`|`https://localhost:9200`|
+|`OC_LDAP_DISABLE_USER_MECHANISM`<br/>`USERS_LDAP_DISABLE_USER_MECHANISM`| 1.0.0 |string|`An option to control the behavior for disabling users. Valid options are 'none', 'attribute' and 'group'. If set to 'group', disabling a user via API will add the user to the configured group for disabled users, if set to 'attribute' this will be done in the ldap user entry, if set to 'none' the disable request is not processed.`|`attribute`|
+|`OC_LDAP_USER_SCHEMA_USER_TYPE`<br/>`USERS_LDAP_USER_TYPE_ATTRIBUTE`| 1.0.0 |string|`LDAP Attribute to distinguish between 'Member' and 'Guest' users. Default is 'openCloudUserType'.`|`openCloudUserType`|
+|`OC_LDAP_DISABLED_USERS_GROUP_DN`<br/>`USERS_LDAP_DISABLED_USERS_GROUP_DN`| 1.0.0 |string|`The distinguished name of the group to which added users will be classified as disabled when 'disable_user_mechanism' is set to 'group'.`|`cn=DisabledUsersGroup,ou=groups,o=libregraph-idm`|
+|`OC_LDAP_USER_SCHEMA_ID`<br/>`USERS_LDAP_USER_SCHEMA_ID`| 1.0.0 |string|`LDAP Attribute to use as the unique ID for users. This should be a stable globally unique ID like a UUID.`|`openclouduuid`|
+|`OC_LDAP_USER_SCHEMA_TENANT_ID`<br/>`USERS_LDAP_USER_SCHEMA_TENANT_ID`| 4.0.0 |string|`LDAP Attribute to use for the tenant ID of users. This is used to identify the tenant of a user in a multi-tenant environment.`|``|
+|`OC_LDAP_USER_SCHEMA_ID_IS_OCTETSTRING`<br/>`USERS_LDAP_USER_SCHEMA_ID_IS_OCTETSTRING`| 1.0.0 |bool|`Set this to true if the defined 'ID' attribute for users is of the 'OCTETSTRING' syntax. This is e.g. required when using the 'objectGUID' attribute of Active Directory for the user ID's.`|`false`|
+|`OC_LDAP_USER_SCHEMA_MAIL`<br/>`USERS_LDAP_USER_SCHEMA_MAIL`| 1.0.0 |string|`LDAP Attribute to use for the email address of users.`|`mail`|
+|`OC_LDAP_USER_SCHEMA_DISPLAYNAME`<br/>`USERS_LDAP_USER_SCHEMA_DISPLAYNAME`| 1.0.0 |string|`LDAP Attribute to use for the displayname of users.`|`displayname`|
+|`OC_LDAP_USER_SCHEMA_USERNAME`<br/>`USERS_LDAP_USER_SCHEMA_USERNAME`| 1.0.0 |string|`LDAP Attribute to use for username of users.`|`uid`|
+|`OC_LDAP_USER_ENABLED_ATTRIBUTE`<br/>`USERS_LDAP_USER_ENABLED_ATTRIBUTE`| 1.0.0 |string|`LDAP attribute to use as a flag telling if the user is enabled or disabled.`|`openclouduserenabled`|
+|`OC_LDAP_GROUP_SCHEMA_ID`<br/>`USERS_LDAP_GROUP_SCHEMA_ID`| 1.0.0 |string|`LDAP Attribute to use as the unique ID for groups. This should be a stable globally unique ID like a UUID.`|`openclouduuid`|
+|`OC_LDAP_GROUP_SCHEMA_ID_IS_OCTETSTRING`<br/>`USERS_LDAP_GROUP_SCHEMA_ID_IS_OCTETSTRING`| 1.0.0 |bool|`Set this to true if the defined 'id' attribute for groups is of the 'OCTETSTRING' syntax. This is e.g. required when using the 'objectGUID' attribute of Active Directory for the group ID's.`|`false`|
+|`OC_LDAP_GROUP_SCHEMA_MAIL`<br/>`USERS_LDAP_GROUP_SCHEMA_MAIL`| 1.0.0 |string|`LDAP Attribute to use for the email address of groups (can be empty).`|`mail`|
+|`OC_LDAP_GROUP_SCHEMA_DISPLAYNAME`<br/>`USERS_LDAP_GROUP_SCHEMA_DISPLAYNAME`| 1.0.0 |string|`LDAP Attribute to use for the displayname of groups (often the same as groupname attribute).`|`cn`|
+|`OC_LDAP_GROUP_SCHEMA_GROUPNAME`<br/>`USERS_LDAP_GROUP_SCHEMA_GROUPNAME`| 1.0.0 |string|`LDAP Attribute to use for the name of groups.`|`cn`|
+|`OC_LDAP_GROUP_SCHEMA_MEMBER`<br/>`USERS_LDAP_GROUP_SCHEMA_MEMBER`| 1.0.0 |string|`LDAP Attribute that is used for group members.`|`member`|
+|`USERS_OWNCLOUDSQL_DB_USERNAME`| 1.0.0 |string|`Database user to use for authenticating with the owncloud database.`|`owncloud`|
+|`USERS_OWNCLOUDSQL_DB_PASSWORD`| 1.0.0 |string|`Password for the database user.`|`secret`|
+|`USERS_OWNCLOUDSQL_DB_HOST`| 1.0.0 |string|`Hostname of the database server.`|`mysql`|
+|`USERS_OWNCLOUDSQL_DB_PORT`| 1.0.0 |int|`Network port to use for the database connection.`|`3306`|
+|`USERS_OWNCLOUDSQL_DB_NAME`| 1.0.0 |string|`Name of the owncloud database.`|`owncloud`|
+|`USERS_OWNCLOUDSQL_IDP`| 1.0.0 |string|`The identity provider value to set in the userids of the CS3 user objects for users returned by this user provider.`|`https://localhost:9200`|
+|`USERS_OWNCLOUDSQL_NOBODY`| 1.0.0 |int64|`Fallback number if no numeric UID and GID properties are provided.`|`90`|
+|`USERS_OWNCLOUDSQL_JOIN_USERNAME`| 1.0.0 |bool|`Join the user properties table to read usernames`|`false`|
+|`USERS_OWNCLOUDSQL_JOIN_OWNCLOUD_UUID`| 1.0.0 |bool|`Join the user properties table to read user IDs.`|`false`|
+|`USERS_OWNCLOUDSQL_ENABLE_MEDIAL_SEARCH`| 1.0.0 |bool|`Allow 'medial search' when searching for users instead of just doing a prefix search. This allows finding 'Alice' when searching for 'lic'.`|`false`|
diff --git a/versioned_docs/version-7.x/_static/env-vars/users_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/users_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/users_readme.md b/versioned_docs/version-7.x/_static/env-vars/users_readme.md
new file mode 100755
index 000000000..26a1b4af1
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/users_readme.md
@@ -0,0 +1,40 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The `users` service provides the CS3 Users API for OpenCloud. It is responsible for managing user information and authentication within the OpenCloud instance.
+
+This service implements the CS3 identity user provider interface, allowing other services to query and manage user accounts. It works as a backend provider for the `graph` service when using the CS3 backend mode.
+
+
+## Table of Contents
+
+* [Backend Integration](#backend-integration)
+* [API](#api)
+* [Usage](#usage)
+* [Scalability](#scalability)
+
+## Backend Integration
+
+The users service can work with different storage backends:
+- LDAP integration through the graph service
+- Direct CS3 API implementation
+
+When using the `graph` service with the CS3 backend (`GRAPH_IDENTITY_BACKEND=cs3`), the graph service queries user information through this service.
+
+## API
+
+The service provides CS3 gRPC APIs for:
+- Listing users
+- Getting user information
+- Finding users by username, email, or ID
+
+## Usage
+
+The users service is only used internally by other OpenCloud services and not being accessed directly by clients. The `frontend`, `ocs`, and `graph` services translate HTTP API requests into CS3 API calls to this service.
+
+## Scalability
+
+Since the users service queries backend systems (like LDAP through the configured identity backend), it can be scaled horizontally without additional configuration when using stateless backends.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/web.yaml b/versioned_docs/version-7.x/_static/env-vars/web.yaml
new file mode 100644
index 000000000..716cfa412
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/web.yaml
@@ -0,0 +1,126 @@
+# Autogenerated
+# Filename: web.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9104
+  token: ""
+  pprof: false
+  zpages: false
+http:
+  addr: 127.0.0.1:9100
+  tls:
+    enabled: false
+    cert: ""
+    key: ""
+  root: /
+  cache_ttl: 604800
+  cors:
+    allow_origins:
+    - https://localhost:9200
+    allow_methods:
+    - OPTIONS
+    - HEAD
+    - GET
+    - PUT
+    - PATCH
+    - POST
+    - DELETE
+    - MKCOL
+    - PROPFIND
+    - PROPPATCH
+    - MOVE
+    - COPY
+    - REPORT
+    - SEARCH
+    allow_headers:
+    - Origin
+    - Accept
+    - Content-Type
+    - Depth
+    - Authorization
+    - Ocs-Apirequest
+    - If-None-Match
+    - If-Match
+    - Destination
+    - Overwrite
+    - X-Request-Id
+    - X-Requested-With
+    - Tus-Resumable
+    - Tus-Checksum-Algorithm
+    - Upload-Concat
+    - Upload-Length
+    - Upload-Metadata
+    - Upload-Defer-Length
+    - Upload-Expires
+    - Upload-Checksum
+    - Upload-Offset
+    - X-HTTP-Method-Override
+    allow_credentials: false
+asset:
+  core_path: /var/lib/opencloud/web/assets/core
+  themes_path: /var/lib/opencloud/web/assets/themes
+  apps_path: /var/lib/opencloud/web/assets/apps
+file: ""
+web:
+  theme_server: https://localhost:9200
+  theme_path: /themes/opencloud/theme.json
+  config:
+    server: https://localhost:9200
+    oidc:
+      metadata_url: https://localhost:9200/.well-known/openid-configuration
+      authority: https://localhost:9200
+      client_id: web
+      response_type: code
+      scope: openid profile email
+      post_logout_redirect_uri: ""
+    apps:
+    - files
+    - search
+    - text-editor
+    - pdf-viewer
+    - external
+    - admin-settings
+    - epub-reader
+    - preview
+    - app-store
+    applications: []
+    external_apps: []
+    options:
+      accountEditLink: null
+      disableFeedbackLink: false
+      feedbackLink: null
+      runningOnEos: false
+      cernFeatures: false
+      openFilesInNewTab: false
+      upload: null
+      editor: null
+      contextHelpersReadMore: true
+      logoutUrl: ""
+      loginUrl: ""
+      tokenStorageLocal: true
+      disabledExtensions: []
+      embed:
+        enabled: ""
+        target: ""
+        messagesOrigin: ""
+        delegateAuthentication: false
+        delegateAuthenticationOrigin: ""
+      userListRequiresFilter: false
+      concurrentRequests:
+        resourceBatchActions: 0
+        sse: 0
+        shares:
+          create: 0
+          list: 0
+      defaultAppId: ""
+      oxAppSuite:
+        enabled: false
+        apiUrl: ""
+    styles: []
+    scripts: []
+    custom_translations: []
+apps: {}
+token_manager:
+  jwt_secret: ""
+gateway_addr: eu.opencloud.api.gateway
diff --git a/versioned_docs/version-7.x/_static/env-vars/web_configvars.md b/versioned_docs/version-7.x/_static/env-vars/web_configvars.md
new file mode 100644
index 000000000..fa88fbbef
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/web_configvars.md
@@ -0,0 +1,65 @@
+
+2026-06-19-00-12-13
+
+## Deprecation Notice
+
+| Deprecation Info | Deprecation Version | Removal Version | Deprecation Replacement |
+|---|---|---|:---|
+| WEB_OPTION_RUNNING_ON_EOS is deprecated and will be removed in a future release. | 6.2.0 | next-prod |  |
+
+## Environment variables for the **web** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`WEB_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`WEB_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9104`|
+|`WEB_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`WEB_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`WEB_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`WEB_HTTP_ADDR`| 1.0.0 |string|`The bind address of the HTTP service.`|`127.0.0.1:9100`|
+|`OC_HTTP_TLS_ENABLED`| 1.0.0 |bool|`Activates TLS for the http based services using the server certifcate and key configured via OC_HTTP_TLS_CERTIFICATE and OC_HTTP_TLS_KEY. If OC_HTTP_TLS_CERTIFICATE is not set a temporary server certificate is generated - to be used with PROXY_INSECURE_BACKEND=true.`|`false`|
+|`OC_HTTP_TLS_CERTIFICATE`| 1.0.0 |string|`Path/File name of the TLS server certificate (in PEM format) for the http services.`|``|
+|`OC_HTTP_TLS_KEY`| 1.0.0 |string|`Path/File name for the TLS certificate key (in PEM format) for the server certificate to use for the http services.`|``|
+|`WEB_HTTP_ROOT`| 1.0.0 |string|`Subdirectory that serves as the root for this HTTP service.`|`/`|
+|`WEB_CACHE_TTL`| 1.0.0 |int|`Cache policy in seconds for OpenCloud Web assets.`|`604800`|
+|`OC_CORS_ALLOW_ORIGINS`<br/>`WEB_CORS_ALLOW_ORIGINS`| 1.0.0 |[]string|`A list of allowed CORS origins. See following chapter for more details: *Access-Control-Allow-Origin* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin. See the Environment Variable Types description for more details.`|`[https://localhost:9200]`|
+|`OC_CORS_ALLOW_METHODS`<br/>`WEB_CORS_ALLOW_METHODS`| 1.0.0 |[]string|`A list of allowed CORS methods. See following chapter for more details: *Access-Control-Request-Method* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Method. See the Environment Variable Types description for more details.`|`[OPTIONS HEAD GET PUT PATCH POST DELETE MKCOL PROPFIND PROPPATCH MOVE COPY REPORT SEARCH]`|
+|`OC_CORS_ALLOW_HEADERS`<br/>`WEB_CORS_ALLOW_HEADERS`| 1.0.0 |[]string|`A list of allowed CORS headers. See following chapter for more details: *Access-Control-Request-Headers* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Headers. See the Environment Variable Types description for more details.`|`[Origin Accept Content-Type Depth Authorization Ocs-Apirequest If-None-Match If-Match Destination Overwrite X-Request-Id X-Requested-With Tus-Resumable Tus-Checksum-Algorithm Upload-Concat Upload-Length Upload-Metadata Upload-Defer-Length Upload-Expires Upload-Checksum Upload-Offset X-HTTP-Method-Override]`|
+|`OC_CORS_ALLOW_CREDENTIALS`<br/>`WEB_CORS_ALLOW_CREDENTIALS`| 1.0.0 |bool|`Allow credentials for CORS. See following chapter for more details: *Access-Control-Allow-Credentials* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Credentials.`|`false`|
+|`WEB_ASSET_CORE_PATH`| 1.0.0 |string|`Serve OpenCloud Web assets from a path on the filesystem instead of the builtin assets. If not defined, the root directory derives from $OC_BASE_DATA_PATH/web/assets/core`|`/var/lib/opencloud/web/assets/core`|
+|`OC_ASSET_THEMES_PATH`<br/>`WEB_ASSET_THEMES_PATH`| 1.0.0 |string|`Serve OpenCloud themes from a path on the filesystem instead of the builtin assets. If not defined, the root directory derives from $OC_BASE_DATA_PATH/web/assets/themes`|`/var/lib/opencloud/web/assets/themes`|
+|`WEB_ASSET_APPS_PATH`| 1.0.0 |string|`Serve OpenCloud Web apps assets from a path on the filesystem instead of the builtin assets. If not defined, the root directory derives from $OC_BASE_DATA_PATH/web/assets/apps`|`/var/lib/opencloud/web/assets/apps`|
+|`WEB_UI_CONFIG_FILE`| 1.0.0 |string|`Read the OpenCloud Web json based configuration from this path/file. The config file takes precedence over WEB_OPTION_xxx environment variables. See the text description for more details.`|``|
+|`OC_URL`<br/>`WEB_UI_THEME_SERVER`| 1.0.0 |string|`Base URL to load themes from. Will be prepended to the theme path.`|`https://localhost:9200`|
+|`WEB_UI_THEME_PATH`| 1.0.0 |string|`Path to the theme json file. Will be appended to the URL of the theme server.`|`/themes/opencloud/theme.json`|
+|`OC_URL`<br/>`WEB_UI_CONFIG_SERVER`| 1.0.0 |string|`URL, where the OpenCloud APIs are reachable for OpenCloud Web.`|`https://localhost:9200`|
+|`WEB_OIDC_METADATA_URL`| 1.0.0 |string|`URL for the OIDC well-known configuration endpoint. Defaults to the OpenCloud API URL + '/.well-known/openid-configuration'.`|`https://localhost:9200/.well-known/openid-configuration`|
+|`OC_URL`<br/>`OC_OIDC_ISSUER`<br/>`WEB_OIDC_AUTHORITY`| 1.0.0 |string|`URL of the OIDC issuer. It defaults to URL of the builtin IDP.`|`https://localhost:9200`|
+|`OC_OIDC_CLIENT_ID`<br/>`WEB_OIDC_CLIENT_ID`| 1.0.0 |string|`The OIDC client ID which OpenCloud Web uses. This client needs to be set up in your IDP. Note that this setting has no effect when using the builtin IDP.`|`web`|
+|`WEB_OIDC_RESPONSE_TYPE`| 1.0.0 |string|`The OIDC response type to use for authentication.`|`code`|
+|`WEB_OIDC_SCOPE`| 1.0.0 |string|`OIDC scopes to request during authentication to authorize access to user details. Defaults to 'openid profile email'. Values are separated by blank. More example values but not limited to are 'address' or 'phone' etc.`|`openid profile email`|
+|`WEB_OIDC_POST_LOGOUT_REDIRECT_URI`| 1.0.0 |string|`This value needs to point to a valid and reachable web page. The web client will trigger a redirect to that page directly after the logout action. The default value is empty and redirects to the login page.`|``|
+|`WEB_UI_CORE_APPS`| next |[]string|`Allows to override the default list of core apps in OpenCloud Web.`|`[files search text-editor pdf-viewer external admin-settings epub-reader preview app-store]`|
+|`WEB_OPTION_DISABLE_FEEDBACK_LINK`| 1.0.0 |bool|`Set this option to 'true' to disable the feedback link in the top bar. Keeping it enabled by setting the value to 'false' or with the absence of the option, allows OpenCloud to get feedback from your user base through a dedicated survey website.`|`false`|
+|`WEB_OPTION_RUNNING_ON_EOS`| 1.0.0 |bool|`Set this option to 'true' if running on an EOS storage backend (\https://eos-web.web.cern.ch/eos-web/) to enable its specific features. Defaults to 'false'.`|`false`|
+|`WEB_OPTION_OPEN_FILES_IN_NEW_TAB`| 5.3.0 |bool|`Set this option to 'true' to open files in a new browser tab instead of navigating in the same tab. Defaults to 'false'.`|`false`|
+|`WEB_OPTION_CONTEXTHELPERS_READ_MORE`| 1.0.0 |bool|`Specifies whether the 'Read more' link should be displayed or not.`|`true`|
+|`WEB_OPTION_LOGOUT_URL`| 1.0.0 |string|`Adds a link to the user's profile page to point him to an external page, where he can manage his session and devices. This is helpful when an external IdP is used. This option is disabled by default.`|``|
+|`WEB_OPTION_LOGIN_URL`| 1.0.0 |string|`Specifies the target URL to the login page. This is helpful when an external IdP is used. This option is disabled by default. Example URL like: \https://www.myidp.com/login.`|``|
+|`WEB_OPTION_TOKEN_STORAGE_LOCAL`| 1.0.0 |bool|`Specifies whether the access token will be stored in the local storage when set to 'true' or in the session storage when set to 'false'. If stored in the local storage, login state will be persisted across multiple browser tabs, means no additional logins are required.`|`true`|
+|`WEB_OPTION_DISABLED_EXTENSIONS`| 1.0.0 |[]string|`A list to disable specific Web extensions identified by their ID. The ID can e.g. be taken from the 'index.ts' file of the web extension. Example: 'com.github.opencloud-eu.web.files.search,com.github.opencloud-eu.web.files.print'. See the Environment Variable Types description for more details.`|`[]`|
+|`WEB_OPTION_EMBED_ENABLED`| 1.0.0 |string|`Defines whether Web should be running in 'embed' mode. Setting this to 'true' will enable a stripped down version of Web with reduced functionality used to integrate Web into other applications like via iFrame. Setting it to 'false' or not setting it (default) will run Web as usual with all functionality enabled. See the text description for more details.`|``|
+|`WEB_OPTION_EMBED_TARGET`| 1.0.0 |string|`Defines how Web is being integrated when running in 'embed' mode. Currently, the only supported options are '' (empty) and 'location'. With '' which is the default, Web will run regular as defined via the 'embed.enabled' config option. With 'location', Web will run embedded as location picker. Resource selection will be disabled and the selected resources array always includes the current folder as the only item. See the text description for more details.`|``|
+|`WEB_OPTION_EMBED_MESSAGES_ORIGIN`| 1.0.0 |string|`Defines a URL under which Web can be integrated via iFrame in 'embed' mode. Note that setting this is mandatory when running Web in 'embed' mode. Use '*' as value to allow running the iFrame under any URL, although this is not recommended for security reasons. See the text description for more details.`|``|
+|`WEB_OPTION_EMBED_DELEGATE_AUTHENTICATION`| 1.0.0 |bool|`Defines whether Web should require authentication to be done by the parent application when running in 'embed' mode. If set to 'true' Web will not try to authenticate the user on its own but will require an access token coming from the parent application. Defaults to being unset.`|`false`|
+|`WEB_OPTION_EMBED_DELEGATE_AUTHENTICATION_ORIGIN`| 1.0.0 |string|`Defines the host to validate the message event origin against when running Web in 'embed' mode with delegated authentication. Defaults to event message origin validation being omitted, which is only recommended for development setups.`|``|
+|`WEB_OPTION_USER_LIST_REQUIRES_FILTER`| 1.0.0 |bool|`Defines whether one or more filters must be set in order to list users in the Web admin settings. Set this option to 'true' if running in an environment with a lot of users and listing all users could slow down performance. Defaults to 'false'.`|`false`|
+|`WEB_OPTION_CONCURRENT_REQUESTS_RESOURCE_BATCH_ACTIONS`| 1.0.0 |int|`Defines the maximum number of concurrent requests per file/folder/space batch action. Defaults to 4.`|`0`|
+|`WEB_OPTION_CONCURRENT_REQUESTS_SSE`| 1.0.0 |int|`Defines the maximum number of concurrent requests in SSE event handlers. Defaults to 4.`|`0`|
+|`WEB_OPTION_CONCURRENT_REQUESTS_SHARES_CREATE`| 1.0.0 |int|`Defines the maximum number of concurrent requests per sharing invite batch. Defaults to 4.`|`0`|
+|`WEB_OPTION_CONCURRENT_REQUESTS_SHARES_LIST`| 1.0.0 |int|`Defines the maximum number of concurrent requests when loading individual share information inside listings. Defaults to 2.`|`0`|
+|`WEB_OPTION_DEFAULT_APP_ID`| 4.0.0 |string|`Defines the entrypoint for the web ui.`|``|
+|`WEB_OPTION_OX_APP_SUITE_ENABLED`| next |bool|`Enables the OX App Suite. Defaults to false.`|`false`|
+|`WEB_OPTION_OX_APP_SUITE_API_URL`| next |string|`The API URL for the OX App Suite. Defaults to an empty string.`|``|
+|`OC_JWT_SECRET`<br/>`WEB_JWT_SECRET`| 1.0.0 |string|`The secret to mint and validate jwt tokens.`|``|
+|`WEB_GATEWAY_GRPC_ADDR`| 1.0.0 |string|`The bind address of the GRPC service.`|`eu.opencloud.api.gateway`|
diff --git a/versioned_docs/version-7.x/_static/env-vars/web_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/web_deprecation.md
new file mode 100644
index 000000000..48f99f261
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/web_deprecation.md
@@ -0,0 +1,4 @@
+
+:::danger
+web has deprecated environment variables. Please refer to the table below for more information.
+:::
\ No newline at end of file
diff --git a/versioned_docs/version-7.x/_static/env-vars/web_readme.md b/versioned_docs/version-7.x/_static/env-vars/web_readme.md
new file mode 100755
index 000000000..d06ee4a6f
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/web_readme.md
@@ -0,0 +1,196 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The web service embeds and serves the static files for the [OpenCloud Web Client](https://github.com/opencloud-eu/web).
+Note that clients will respond with a connection error if the web service is not available.
+
+The web service also provides a minimal API for branding functionality like changing the logo shown.
+
+
+## Table of Contents
+
+* [Custom Compiled Web Assets](#custom-compiled-web-assets)
+* [Web UI Configuration](#web-ui-configuration)
+  * [Web UI Options](#web-ui-options)
+  * [Web UI Config File](#web-ui-config-file)
+  * [Embedding Web](#embedding-web)
+* [Web Apps](#web-apps)
+  * [Loading Themes](#loading-themes)
+  * [Loading Applications](#loading-applications)
+  * [Application Structure](#application-structure)
+  * [Application Configuration](#application-configuration)
+  * [Using Custom Assets](#using-custom-assets)
+* [Miscellaneous](#miscellaneous)
+
+## Custom Compiled Web Assets
+
+If you want to use your custom compiled web client assets instead of the embedded ones,
+then you can do that by setting the `WEB_ASSET_CORE_PATH` variable to point to your compiled files.
+See [OpenCloud Web / Getting Started](https://docs.opencloud.eu/clients/web/getting-started/) for more details.
+
+## Web UI Configuration
+
+*   Single configuration settings of the embedded web UI can be defined via `WEB_OPTION_xxx` environment variables.
+*   A json based configuration file can be used via the `WEB_UI_CONFIG_FILE` environment variable.
+*   If a json based configuration file is used, these configurations take precedence over single options set.
+
+### Web UI Options
+
+Besides theming, the behavior of the web UI can be configured via options. See the environment variables `WEB_OPTION_xxx`
+for more details.
+
+### Web UI Config File
+
+When defined via the `WEB_UI_CONFIG_FILE` environment variable, the configuration of the web UI can be made
+with a [json based](https://github.com/opencloud-eu/web/tree/master/config) file.
+
+### Embedding Web
+
+Web can be consumed by another application in a stripped down version called “Embed mode”.
+This mode is supposed to be used in the context of selecting or sharing resources.
+
+For more details see the developer documentation [OpenCloud Web / Embed Mode](https://docs.opencloud.eu/docs/dev/web/embed-mode).
+See the environment variables: `WEB_OPTION_MODE` and `WEB_OPTION_EMBED_TARGET` to configure the embedded mode.
+
+## Web Apps
+
+The administrator of the environment is capable of providing custom web applications to the users.
+This feature is useful for organizations that want to provide third party or custom apps to their users.
+
+It's important to note that the feature at the moment is only capable of providing static (js, mjs, e.g.) web applications
+and does not support injection of dynamic web applications (custom dynamic backends).
+
+### Loading Themes
+
+Web themes are loaded, if added in the OpenCloud source code, at build-time from
+`<opencloud_repo>/services/web/assets/themes`.
+This cannot be manipulated at runtime.
+
+Additionally, the administrator can provide custom themes by storing it in the path defined by the environment
+variable `WEB_ASSET_THEMES_PATH`.
+
+With the theme root directory defined, the system needs to know which theme to use.
+This can be done by setting the `WEB_UI_THEME_PATH` environment variable.
+
+The final theme is composed of the built-in and the custom theme provided by the
+administrator via `WEB_ASSET_THEMES_PATH` and `WEB_UI_THEME_PATH`.
+
+For example, OpenCloud by default contains a built-in OpenCloud theme.
+If the administrator provides a custom theme via the `WEB_ASSET_THEMES_PATH` directory like,
+`WEB_ASSET_THEMES_PATH/opencloud/themes.json`, this one will be used instead of the built-in one.
+
+Some theme keys are mandatory, like the `common.shareRoles` settings.
+Such mandatory keys are injected automatically at runtime if not provided.
+
+### Loading Applications
+
+Web applications are loaded, if added in the OpenCloud source code, at build-time from
+`<opencloud_repo>/services/web/assets/apps`. This cannot be manipulated at runtime.
+
+Additionally, the administrator can provide custom applications by storing them in the path defined by the environment
+variable `WEB_ASSET_APPS_PATH`.
+
+This environment variable defaults to the OpenCloud base data directory `$OC_BASE_DATA_PATH/web/assets/apps`,
+but can be redefined with any path set manually.
+
+The final list of available applications is composed of the built-in and the custom applications provided by the
+administrator via `WEB_ASSET_APPS_PATH`.
+
+For example, if OpenCloud contains a built-in extension named `image-viewer-dfx` and the administrator provides a custom application named `image-viewer-obj` via the `WEB_ASSET_APPS_PATH` directory, the user will be able to access both
+applications from the WebUI.
+
+### Application Structure
+
+* Applications always have to follow a strict structure.\
+Everything else is skipped and not considered as an application.
+   *   Each application must be in its own directory accessed via `WEB_ASSET_APPS_PATH`.
+   *   Each application directory must contain a `manifest.json` file.
+   *   Each application directory can contain a `config.json` file.
+
+* The `manifest.json` file contains the following fields:
+   *   `entrypoint` - required\
+       The entrypoint of the application like `index.js`, the path is relative to the parent directory.
+   *   `config` - optional\
+       A list of key-value pairs that are passed to the global web application configuration `apps.yaml`.
+
+### Application Configuration
+
+If a custom configuration is needed, the administrator must provide the required configuration inside the `$OC_BASE_DATA_PATH/config/apps.yaml` file.
+
+NOTE: An application manifest should _never_ be changed manually, see [Using Custom Assets](#using-custom-assets) for customisation.
+
+The `apps.yaml` file must contain a list of key-value pairs which gets merged with the `config` field. For example, if the `image-viewer-obj` application contains the following configuration:
+
+```json
+{
+  "entrypoint": "index.js",
+  "config": {
+    "maxWidth": 1280,
+    "maxHeight": 1280
+  }
+}
+```
+
+The `apps.yaml` file contains the following configuration:
+
+```yaml
+image-viewer-obj:
+  config:
+    maxHeight: 640
+    maxSize: 512
+```
+
+optional each application can have its own configuration file, which will be loaded by the WEB service.
+
+```json
+{
+  "config": {
+    "maxWidth": 320
+  }
+}
+```
+
+The Merge order is as follows: local.config overwrites > global.config overwrites > manifest.config.
+The result will be:
+
+```json
+{
+  "external_apps": [
+    {
+      "id": "image-viewer-obj",
+      "path": "index.js",
+      "config": {
+        "maxWidth": 320,
+        "maxHeight": 640,
+        "maxSize": 512
+      }
+    }
+  ]
+}
+```
+
+Besides the configuration from the `manifest.json` file,
+the `apps.yaml` or the `config.json` file can also contain the following fields:
+
+*   `disabled` - optional\
+    Defaults to `false`. If set to `true`, the application will not be loaded.
+
+### Using Custom Assets
+
+Besides the configuration and application registration, in the process of loading the application assets, the system uses a mechanism to load custom assets.
+
+This is useful for cases where just a single asset should be overwritten, like a logo or similar.
+
+Consider the following: OpenCloud is shipped with a default web app named `image-viewer-dfx` which contains a logo,
+but the administrator wants to provide a custom logo for that application.
+
+This can be achieved using the path defined via `WEB_ASSET_APPS_PATH` and adding a custom structure like `WEB_ASSET_APPS_PATH/image-viewer-dfx/`. Here you can add all custom assets to load like `logo.png`. On loading the web app, custom assets defined overwrite default ones.
+
+This also applies for the `manifest.json` file, if the administrator wants to provide a custom one.
+
+## Miscellaneous
+
+Please note that OpenCloud, in particular the web service, needs a restart to load new applications or changes to the `apps.yaml` file.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/webdav.yaml b/versioned_docs/version-7.x/_static/env-vars/webdav.yaml
new file mode 100644
index 000000000..1da16a7c4
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/webdav.yaml
@@ -0,0 +1,40 @@
+# Autogenerated
+# Filename: webdav.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9119
+  token: ""
+  pprof: false
+  zpages: false
+grpc_client_tls: null
+http:
+  addr: 127.0.0.1:9115
+  root: /
+  cors:
+    allow_origins:
+    - '*'
+    allow_methods:
+    - GET
+    - POST
+    - PUT
+    - PATCH
+    - DELETE
+    - OPTIONS
+    allow_headers:
+    - Authorization
+    - Origin
+    - Content-Type
+    - Accept
+    - X-Requested-With
+    - X-Request-Id
+    - Cache-Control
+    allow_credentials: true
+  tls:
+    enabled: false
+    cert: ""
+    key: ""
+disablePreviews: false
+opencloud_public_url: https://localhost:9200
+webdav_namespace: /users/{{.Id.OpaqueId}}
+reva_gateway: eu.opencloud.api.gateway
diff --git a/versioned_docs/version-7.x/_static/env-vars/webdav_configvars.md b/versioned_docs/version-7.x/_static/env-vars/webdav_configvars.md
new file mode 100644
index 000000000..7e938636e
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/webdav_configvars.md
@@ -0,0 +1,22 @@
+## Environment variables for the **webdav** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`WEBDAV_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`WEBDAV_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9119`|
+|`WEBDAV_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`WEBDAV_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`WEBDAV_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`WEBDAV_HTTP_ADDR`| 1.0.0 |string|`The bind address of the HTTP service.`|`127.0.0.1:9115`|
+|`WEBDAV_HTTP_ROOT`| 1.0.0 |string|`Subdirectory that serves as the root for this HTTP service.`|`/`|
+|`OC_CORS_ALLOW_ORIGINS`<br/>`WEBDAV_CORS_ALLOW_ORIGINS`| 1.0.0 |[]string|`A list of allowed CORS origins. See following chapter for more details: *Access-Control-Allow-Origin* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin. See the Environment Variable Types description for more details.`|`[*]`|
+|`OC_CORS_ALLOW_METHODS`<br/>`WEBDAV_CORS_ALLOW_METHODS`| 1.0.0 |[]string|`A list of allowed CORS methods. See following chapter for more details: *Access-Control-Request-Method* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Method. See the Environment Variable Types description for more details.`|`[GET POST PUT PATCH DELETE OPTIONS]`|
+|`OC_CORS_ALLOW_HEADERS`<br/>`WEBDAV_CORS_ALLOW_HEADERS`| 1.0.0 |[]string|`A list of allowed CORS headers. See following chapter for more details: *Access-Control-Request-Headers* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Headers. See the Environment Variable Types description for more details.`|`[Authorization Origin Content-Type Accept X-Requested-With X-Request-Id Cache-Control]`|
+|`OC_CORS_ALLOW_CREDENTIALS`<br/>`WEBDAV_CORS_ALLOW_CREDENTIALS`| 1.0.0 |bool|`Allow credentials for CORS.See following chapter for more details: *Access-Control-Allow-Credentials* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Credentials.`|`true`|
+|`OC_HTTP_TLS_ENABLED`| 1.0.0 |bool|`Activates TLS for the http based services using the server certifcate and key configured via OC_HTTP_TLS_CERTIFICATE and OC_HTTP_TLS_KEY. If OC_HTTP_TLS_CERTIFICATE is not set a temporary server certificate is generated - to be used with PROXY_INSECURE_BACKEND=true.`|`false`|
+|`OC_HTTP_TLS_CERTIFICATE`| 1.0.0 |string|`Path/File name of the TLS server certificate (in PEM format) for the http services.`|``|
+|`OC_HTTP_TLS_KEY`| 1.0.0 |string|`Path/File name for the TLS certificate key (in PEM format) for the server certificate to use for the http services.`|``|
+|`OC_DISABLE_PREVIEWS`<br/>`WEBDAV_DISABLE_PREVIEWS`| 1.0.0 |bool|`Set this option to 'true' to disable rendering of thumbnails triggered via webdav access. Note that when disabled, all access to preview related webdav paths will return a 404.`|`false`|
+|`OC_URL`<br/>`OC_PUBLIC_URL`| 1.0.0 |string|`URL, where OpenCloud is reachable for users.`|`https://localhost:9200`|
+|`WEBDAV_WEBDAV_NAMESPACE`| 1.0.0 |string|`CS3 path layout to use when forwarding /webdav requests`|`/users/{{.Id.OpaqueId}}`|
+|`OC_REVA_GATEWAY`| 1.0.0 |string|`CS3 gateway used to look up user metadata`|`eu.opencloud.api.gateway`|
diff --git a/versioned_docs/version-7.x/_static/env-vars/webdav_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/webdav_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/webdav_readme.md b/versioned_docs/version-7.x/_static/env-vars/webdav_readme.md
new file mode 100755
index 000000000..58bd0d4d3
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/webdav_readme.md
@@ -0,0 +1,35 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The webdav service, like the [frontend](../frontend) service, provides a HTTP API following the webdav protocol. It receives HTTP calls from requestors like clients and issues gRPC calls to other services executing these requests. After the called service has finished the request, the webdav service will render their responses in `xml` and sends them back to the requestor.
+
+
+## Table of Contents
+
+* [Endpoints Overview](#endpoints-overview)
+  * [Thumbnails](#thumbnails)
+  * [Search](#search)
+* [Scalability](#scalability)
+
+## Endpoints Overview
+
+Currently, the webdav service handles request for two functionalities, which are `Thumbnails` and `Search`.
+
+### Thumbnails
+
+The webdav service provides various `GET` endpoints to get the thumbnails of a file in authenticated and unauthenticated contexts. It also provides thumbnails for spaces on different endpoints. 
+
+See the [thumbnail](https://github.com/opencloud-eu/opencloud/tree/main/services/thumbnails) service for more information about thumbnails.
+
+### Search
+
+The webdav service provides access to the search functionality. It offers multiple `REPORT` endpoints for getting search results. 
+
+See the [search](https://github.com/opencloud-eu/opencloud/tree/main/services/search) service for more details about search functionality. 
+
+## Scalability
+
+The webdav service does not persist any data and does not cache any information. Therefore multiple instances of this service can be spawned in a bigger deployment like when using container orchestration with Kubernetes, without any extra configuration.
+
diff --git a/versioned_docs/version-7.x/_static/env-vars/webfinger.yaml b/versioned_docs/version-7.x/_static/env-vars/webfinger.yaml
new file mode 100644
index 000000000..afe7108c4
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/webfinger.yaml
@@ -0,0 +1,58 @@
+# Autogenerated
+# Filename: webfinger.yaml
+
+loglevel: error
+debug:
+  addr: 127.0.0.1:9279
+  token: ""
+  pprof: false
+  zpages: false
+http:
+  addr: 127.0.0.1:9275
+  root: /
+  cors:
+    allow_origins:
+    - https://localhost:9200
+    allow_methods: []
+    allow_headers: []
+    allow_credentials: false
+  tls:
+    enabled: false
+    cert: ""
+    key: ""
+instances:
+- claim: sub
+  regex: .+
+  href: '{{.OC_URL}}'
+  titles:
+    en: OpenCloud Instance
+  break: false
+relations:
+- http://openid.net/specs/connect/1.0/issuer
+- http://webfinger.opencloud/rel/server-instance
+idp: https://localhost:9200
+android_client_id: OpenCloudAndroid
+android_client_scopes:
+- openid
+- profile
+- email
+- offline_access
+desktop_client_id: OpenCloudDesktop
+desktop_client_scopes:
+- openid
+- profile
+- email
+- offline_access
+ios_client_id: OpenCloudIOS
+ios_client_scopes:
+- openid
+- profile
+- email
+- offline_access
+web_client_id: web
+web_client_scopes:
+- openid
+- profile
+- email
+opencloud_url: https://localhost:9200
+insecure: false
diff --git a/versioned_docs/version-7.x/_static/env-vars/webfinger_configvars.md b/versioned_docs/version-7.x/_static/env-vars/webfinger_configvars.md
new file mode 100644
index 000000000..3f51e38e0
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/webfinger_configvars.md
@@ -0,0 +1,30 @@
+## Environment variables for the **webfinger** service
+
+| Name | Introduction Version | Type | Description | Default Value |
+|---|---|---|---|:---|
+|`OC_LOG_LEVEL`<br/>`WEBFINGER_LOG_LEVEL`| 1.0.0 |string|`The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'.`|`error`|
+|`WEBFINGER_DEBUG_ADDR`| 1.0.0 |string|`Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed.`|`127.0.0.1:9279`|
+|`WEBFINGER_DEBUG_TOKEN`| 1.0.0 |string|`Token to secure the metrics endpoint.`|``|
+|`WEBFINGER_DEBUG_PPROF`| 1.0.0 |bool|`Enables pprof, which can be used for profiling.`|`false`|
+|`WEBFINGER_DEBUG_ZPAGES`| 1.0.0 |bool|`Enables zpages, which can be used for collecting and viewing in-memory traces.`|`false`|
+|`WEBFINGER_HTTP_ADDR`| 1.0.0 |string|`The bind address of the HTTP service.`|`127.0.0.1:9275`|
+|`WEBFINGER_HTTP_ROOT`| 1.0.0 |string|`Subdirectory that serves as the root for this HTTP service.`|`/`|
+|`OC_CORS_ALLOW_ORIGINS`<br/>`WEBFINGER_CORS_ALLOW_ORIGINS`| 1.0.0 |[]string|`A list of allowed CORS origins. See following chapter for more details: *Access-Control-Allow-Origin* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin. See the Environment Variable Types description for more details.`|`[https://localhost:9200]`|
+|`OC_CORS_ALLOW_METHODS`<br/>`WEBFINGER_CORS_ALLOW_METHODS`| 1.0.0 |[]string|`A list of allowed CORS methods. See following chapter for more details: *Access-Control-Request-Method* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Method. See the Environment Variable Types description for more details.`|`[]`|
+|`OC_CORS_ALLOW_HEADERS`<br/>`WEBFINGER_CORS_ALLOW_HEADERS`| 1.0.0 |[]string|`A list of allowed CORS headers. See following chapter for more details: *Access-Control-Request-Headers* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Headers. See the Environment Variable Types description for more details.`|`[]`|
+|`OC_CORS_ALLOW_CREDENTIALS`<br/>`WEBFINGER_CORS_ALLOW_CREDENTIALS`| 1.0.0 |bool|`Allow credentials for CORS.See following chapter for more details: *Access-Control-Allow-Credentials* at \https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Credentials.`|`false`|
+|`OC_HTTP_TLS_ENABLED`| 1.0.0 |bool|`Activates TLS for the http based services using the server certifcate and key configured via OC_HTTP_TLS_CERTIFICATE and OC_HTTP_TLS_KEY. If OC_HTTP_TLS_CERTIFICATE is not set a temporary server certificate is generated - to be used with PROXY_INSECURE_BACKEND=true.`|`false`|
+|`OC_HTTP_TLS_CERTIFICATE`| 1.0.0 |string|`Path/File name of the TLS server certificate (in PEM format) for the http services.`|``|
+|`OC_HTTP_TLS_KEY`| 1.0.0 |string|`Path/File name for the TLS certificate key (in PEM format) for the server certificate to use for the http services.`|``|
+|`WEBFINGER_RELATIONS`| 1.0.0 |[]string|`A list of relation URIs or registered relation types to add to webfinger responses. See the Environment Variable Types description for more details.`|`[http://openid.net/specs/connect/1.0/issuer http://webfinger.opencloud/rel/server-instance]`|
+|`OC_URL`<br/>`OC_OIDC_ISSUER`<br/>`WEBFINGER_OIDC_ISSUER`| 1.0.0 |string|`The identity provider href for the openid-discovery relation.`|`https://localhost:9200`|
+|`OC_OIDC_CLIENT_ID`<br/>`WEBFINGER_ANDROID_OIDC_CLIENT_ID`| 6.0.0 |string|`The OIDC client ID for Android app.`|`OpenCloudAndroid`|
+|`OC_OIDC_CLIENT_SCOPES`<br/>`WEBFINGER_ANDROID_OIDC_CLIENT_SCOPES`| 6.0.0 |[]string|`The OIDC client scopes the Android app should request.`|`[openid profile email offline_access]`|
+|`OC_OIDC_CLIENT_ID`<br/>`WEBFINGER_DESKTOP_OIDC_CLIENT_ID`| 6.0.0 |string|`The OIDC client ID for the OpenCloud desktop application.`|`OpenCloudDesktop`|
+|`OC_OIDC_CLIENT_SCOPES`<br/>`WEBFINGER_DESKTOP_OIDC_CLIENT_SCOPES`| 6.0.0 |[]string|`The OIDC client scopes the OpenCloud desktop application should request.`|`[openid profile email offline_access]`|
+|`OC_OIDC_CLIENT_ID`<br/>`WEBFINGER_IOS_OIDC_CLIENT_ID`| 6.0.0 |string|`The OIDC client ID for the IOS app.`|`OpenCloudIOS`|
+|`OC_OIDC_CLIENT_SCOPES`<br/>`WEBFINGER_IOS_OIDC_CLIENT_SCOPES`| 6.0.0 |[]string|`The OIDC client scopes the IOS app should request.`|`[openid profile email offline_access]`|
+|`OC_OIDC_CLIENT_ID`<br/>`WEB_OIDC_CLIENT_ID`<br/>`WEBFINGER_WEB_OIDC_CLIENT_ID`| 6.0.0 |string|`The OIDC client ID for the OpenCloud web client. The 'WEB_OIDC_CLIENT_ID' setting is only here for backwards compatibility and will be removed in a future release.`|`web`|
+|`OC_OIDC_CLIENT_SCOPES`<br/>`WEB_OIDC_SCOPE`<br/>`WEBFINGER_WEB_OIDC_CLIENT_SCOPES`| 6.0.0 |[]string|`The OIDC client scopes the OpenCloud web client should request. The 'WEB_OIDC_SCOPE' setting is only here for backwards compatibility and will be removed in a future release.`|`[openid profile email]`|
+|`OC_URL`<br/>`WEBFINGER_OPENCLOUD_SERVER_INSTANCE_URL`| 1.0.0 |string|`The URL for the legacy OpenCloud server instance relation (not to be confused with the product OpenCloud Server). It defaults to the OC_URL but can be overridden to support some reverse proxy corner cases. To shard the deployment, multiple instances can be configured in the configuration file.`|`https://localhost:9200`|
+|`OC_INSECURE`<br/>`WEBFINGER_INSECURE`| 1.0.0 |bool|`Allow insecure connections to the WEBFINGER service.`|`false`|
diff --git a/versioned_docs/version-7.x/_static/env-vars/webfinger_deprecation.md b/versioned_docs/version-7.x/_static/env-vars/webfinger_deprecation.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/versioned_docs/version-7.x/_static/env-vars/webfinger_readme.md b/versioned_docs/version-7.x/_static/env-vars/webfinger_readme.md
new file mode 100755
index 000000000..424ec264b
--- /dev/null
+++ b/versioned_docs/version-7.x/_static/env-vars/webfinger_readme.md
@@ -0,0 +1,139 @@
+<!-- Do not edit this file, it is autogenerated. Edit the service README.md instead -->
+
+## Abstract
+
+
+The webfinger service provides an RFC7033 WebFinger lookup of OpenCloud resources, relevant for a given user account at the /.well-known/webfinger enpoint.
+
+1. An [OpenID Connect Discovery](#openid-connect-discovery) for the IdP, based on the OpenCloud URL.
+2. An [Authenticated Instance Discovery](#authenticated-instance-discovery), based on the user account.
+
+These two request are only needed for discovery.
+
+
+## Table of Contents
+
+* [OpenID Connect Discovery](#openid-connect-discovery)
+* [Authenticated Instance Discovery](#authenticated-instance-discovery)
+* [Configure Different Instances Based on OpenidConnect UserInfo Claims](#configure-different-instances-based-on-openidconnect-userinfo-claims)
+
+## OpenID Connect Discovery
+
+Clients can make an unauthenticated `GET https://drive.opencloud.test/.well-known/webfinger?resource=https%3A%2F%2Fdrive.opencloud.test` request to discover the OpenID Connect Issuer in the `http://openid.net/specs/connect/1.0/issuer` relation:
+
+```json
+{
+    "subject": "https://drive.opencloud.test",
+    "links": [
+        {
+            "rel": "http://openid.net/specs/connect/1.0/issuer",
+            "href": "https://sso.example.org/cas/oidc/"
+        }
+    ]
+}
+```
+
+Here, the `resource` takes the instance domain URI, but an `acct:` URI works as well.
+
+## Authenticated Instance Discovery
+
+When using OpenID connect to authenticate requests, clients can look up the opencloud instances a user has access to.
+
+*   Authentication is necessary to prevent leaking information about existing users.
+*   Basic auth is not supported.
+
+The default configuration will simply return the `OC_URL` and direct clients to that domain:
+
+```json
+{
+    "subject": "acct:alan@drive.opencloud.test",
+    "links": [
+        {
+            "rel": "http://openid.net/specs/connect/1.0/issuer",
+            "href": "https://sso.example.org/cas/oidc/"
+        },
+        {
+            "rel": "http://webfinger.opencloud/rel/server-instance",
+            "href": "https://abc.drive.example.org",
+            "titles": {
+                "en": "OpenCloud Instance"
+            }
+        }
+    ]
+}
+```
+
+## Configure Different Instances Based on OpenidConnect UserInfo Claims
+
+A more complex example for configuring different instances could look like this:
+
+```yaml
+webfinger:
+  instances:
+  -  claim: email
+     regex: alan@example\.org
+     href: "https://{{.preferred_username}}.cloud.opencloud.test"
+     title:
+       "en": "OpenCloud Instance for Alan"
+       "de": "OpenCloud Instanz für Alan"
+     break: true
+  -  claim: "email"
+     regex: mary@example\.org
+     href: "https://{{.preferred_username}}.cloud.opencloud.test"
+     title:
+       "en": "OpenCloud Instance for Mary"
+       "de": "OpenCloud Instanz für Mary"
+     break: false
+  -  claim: "email"
+     regex: .+@example\.org
+     href: "https://example-org.cloud.opencloud.test"
+     title:
+       "en": "OpenCloud Instance for example.org"
+       "de": "OpenCloud Instanz für example.org"
+     break: true
+  -  claim: "email"
+     regex: .+@example\.com
+     href: "https://example-com.cloud.opencloud.test"
+     title:
+       "en": "OpenCloud Instance for example.com"
+       "de": "OpenCloud Instanz für example.com"
+     break: true
+  -  claim: "email"
+     regex: .+@.+\..+
+     href: "https://cloud.opencloud.test"
+     title:
+       "en": "OpenCloud Instance"
+       "de": "OpenCloud Instanz"
+     break: true
+```
+
+Now, an authenticated webfinger request for `acct:me@example.org` (when logged in as mary) would return two instances, based on her `email` claim, the regex matches and break flags:
+
+```json
+{
+    "subject": "acct:mary@example.org",
+    "links": [
+        {
+            "rel": "http://openid.net/specs/connect/1.0/issuer",
+            "href": "https://sso.example.org/cas/oidc/"
+        },
+        {
+            "rel": "http://webfinger.opencloud/rel/server-instance",
+            "href": "https://mary.cloud.opencloud.test",
+            "titles": {
+                "en": "OpenCloud Instance for Mary",
+                "de": "OpenCloud Instanz für Mary"
+            }
+        },
+        {
+            "rel": "http://webfinger.opencloud/rel/server-instance",
+            "href": "https://xyz.drive.example.org",
+            "titles": {
+                "en": "OpenCloud Instance for example.org",
+                "de": "OpenCloud Instanz für example.org"
+            }
+        }
+    ]
+}
+```
+
diff --git a/versioned_docs/version-7.x/admin/configuration/_category_.json b/versioned_docs/version-7.x/admin/configuration/_category_.json
new file mode 100644
index 000000000..1369e1162
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Configuration",
+  "position": 5
+}
diff --git a/versioned_docs/version-7.x/admin/configuration/authentication-and-user-management/_category_.json b/versioned_docs/version-7.x/admin/configuration/authentication-and-user-management/_category_.json
new file mode 100644
index 000000000..ea73b4218
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/authentication-and-user-management/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Authentication and Identity Management",
+  "position": 10
+}
diff --git a/versioned_docs/version-7.x/admin/configuration/authentication-and-user-management/external-idp.md b/versioned_docs/version-7.x/admin/configuration/authentication-and-user-management/external-idp.md
new file mode 100644
index 000000000..b167652b6
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/authentication-and-user-management/external-idp.md
@@ -0,0 +1,197 @@
+---
+sidebar_position: 1
+id: external-idp
+title: External OpenID Connect Identity Provider
+description: Integrating external OpenID Connect Identity Providers
+draft: false
+---
+
+# Integrating external OpenID Connect Identity Providers
+
+## Requirements
+
+OpenCloud is able to integrate with external OpenID Connect Identity Providers
+(IDP). However the implementation is currently somewhat opinionated and has
+certain requirements on the IDP. The project is working on loosening some
+of the requirements in order to allow OpenCloud to work with a broader range of
+identity providers.
+
+This is the list of minimal requirements that an IDP needs to fulfill in order
+to work with OpenCloud:
+
+- All clients provided by OpenCloud ([Web](https://github.com/opencloud-eu/web/),
+  [Desktop](https://github.com/opencloud-eu/desktop/), [Android](https://github.com/opencloud-eu/android/)
+  and [iOS](https://github.com/opencloud-eu/ios/)), are implemented as public clients using the
+  authorization code flow with PKCE. Therefore the IDP needs to support this flow.
+- All clients, except the Web client, use predefined client IDs. Therefore the IDP needs to
+  be able to create clients with predefined IDs.
+- All clients, except the Web client, use a hardcoded list of scopes they request from the IDP.
+  As certain features of OpenCloud (especially the automatic role assignment) rely on specific claims
+  being present in the access token or the UserInfo response, the IDP needs to be able to provide
+  additional claims in the Tokens even if the client does not explicitly request them via scopes.
+
+## OpenCloud Configuration
+
+The following environment variables are relevant when connecting OpenCloud to
+an external IDP. An example configuration for Keycloak is provided the
+[Keycloak integration](./keycloak.md) documentation.
+
+- `OC_OIDC_ISSUER`: Set this to the issuer URL of the external Identity Provider
+- `OC_EXCLUDE_RUN_SERVICES`: When using and external IDP the built-in Identity Provider
+  does not need to run. So add `idp` here to prevent the internal `idp` service from
+  starting.
+- `PROXY_OIDC_REWRITE_WELLKNOWN`: Set this to `true` to expose the Identity
+  Provider's `.well-known/openid-configuration` endpoint via the OpenCloud base
+  urls. This helps the oidc clients, that do not yet support discovery via
+  webfinger to locate the Identity Provider's configuration.
+- `PROXY_USER_OIDC_CLAIM` and `PROXY_USER_CS3_CLAIM`: These two variables
+  configure how the users mapped between the Identity Provider and OpenCloud.
+  `PROXY_USER_OIDC_CLAIM` defines the OIDC claim that OpenCloud uses to
+  uniquely identify a user. It is matched against the OpenCloud user attribute
+  defined in `PROXY_USER_CS3_CLAIM`. E.g. if `PROXY_USER_OIDC_CLAIM` is set to
+  `preferred_username` and `PROXY_USER_CS3_CLAIM` is set to `username` then an
+  OpenID Connect user, that has the `preferred_username` set to `alan` will map
+  to the OpenCloud user with username `alan`.
+- `PROXY_AUTOPROVISION_ACCOUNTS` and `GRAPH_USERNAME_MATCH`: When
+  `PROXY_AUTOPROVISION_ACCOUNTS` is set to `true`, OpenCloud will create a new
+  user account in the LDAP Database for every user who logs in via OpenID
+  Connect for the first time. Enabling this requires access to a writable LDAP
+  server. For smaller setups this can be the built-in LDAP server provided by
+  the `idm` service. If set to `false` all users logging in must already be
+  existing in the LDAP server. (The mapping between the OIDC and LDAP users
+  happens based on the aforementioned `PROXY_USER_OIDC_CLAIM` and
+  `PROXY_USER_CS3_CLAIM` settings. Set `GRAPH_USERNAME_MATCH` to `none` when
+  `PROXY_AUTOPROVISION_ACCOUNTS` is set to `true` to disable OpenCloud's
+  default restrictions on allowed characters in usernames.
+- `PROXY_ROLE_ASSIGNMENT_DRIVER` and `GRAPH_ASSIGN_DEFAULT_USER_ROLE`: For
+  details see below
+
+### Automatic Role Assignments
+
+:::note
+As the OpenCloud clients currently only request a hardcoded list of `scopes`,
+the automatic role-assignment currently requires the IDP to be able to provide
+additional claims in the Access Token and the UserInfo endpoint independent of
+the requested `scopes`. If your IDP does not support this, automatic role
+assignment will not work.
+:::
+
+When users login into OpenCloud, they get a user role assigned
+automatically. The automatic role assignment can be configured in different
+ways. The `PROXY_ROLE_ASSIGNMENT_DRIVER` environment variable (or the `driver`
+setting in the `role_assignment` section of the configuration file) select which
+mechanism to use for the automatic role assignment.
+
+When set to `default`, all users which do not have a role assigned at the time
+of first login will get the role 'user' assigned. This is also the
+default behavior if `PROXY_ROLE_ASSIGNMENT_DRIVER` is unset.
+
+When `PROXY_ROLE_ASSIGNMENT_DRIVER` is set to `oidc` the role assignment for a
+user will happen based on the values of an OpenID Connect Claim of that user.
+The name of the OpenID Connect Claim to be used for the role assignment can be
+configured via the `PROXY_ROLE_ASSIGNMENT_OIDC_CLAIM` environment variable. It
+is also possible to define a mapping of claim values to role names defined in
+OpenCloud via a `yaml` configuration. See the following `proxy.yaml` snippet
+for an example.
+
+```yaml
+role_assignment:
+  driver: oidc
+  oidc_role_mapper:
+    role_claim: opencloudRoles
+    role_mapping:
+      - role_name: admin
+        claim_value: myAdminRole
+      - role_name: spaceadmin
+        claim_value: mySpaceAdminRole
+      - role_name: user
+        claim_value: myUserRole
+      - role_name: user-light
+        claim_value: myGuestRole
+```
+
+This would assign the role `admin` to users with the value `myAdminRole` in the claim `opencloudRoles`.
+The role `user` to users with the values `myUserRole` in the claims `opencloudRoles` and so on.
+
+Claim values that are not mapped to a specific OpenCloud role will be ignored.
+
+Note: An OpenCloud user can only have a single role assigned. If the configured
+`role_mapping` and a user's claim values result in multiple possible roles for a user, the order in
+which the role mappings are defined in the configuration is important. The first role in the
+`role_mappings` where the `claim_value` matches a value from the user's roles claim will be assigned
+to the user. So if e.g. a user's `opencloudRoles` claim has the values `myUserRole` and
+`mySpaceAdminRole` that user will get the OpenCloud role `spaceadmin` assigned (because `spaceadmin`
+appears before `user` in the above sample configuration).
+
+If a user's claim values don't match any of the configured role mappings an error will be logged and
+the user will not be able to login.
+
+The default `role_claim` (or `PROXY_ROLE_ASSIGNMENT_OIDC_CLAIM`) is `roles`. The default `role_mapping` is:
+
+```yaml
+- role_name: admin
+  claim_value: opencloudAdmin
+- role_name: spaceadmin
+  claim_value: opencloudSpaceAdmin
+- role_name: user
+  claim_value: opencloudUser
+- role_name: user-light
+  claim_value: opencloudGuest
+```
+
+:::note
+When `PROXY_ROLE_ASSIGNMENT_DRIVER` is set to `oidc` it is recommended to set `GRAPH_ASSIGN_DEFAULT_USER_ROLE` to `false`.
+:::
+
+## Client Configuration
+
+OpenCloud requires several OIDC clients to be configured in the Identity Provider.
+
+### Web Client
+
+The web client is used for browser-based access to OpenCloud:
+
+- Client ID: `web`
+- Client Type: Public client
+- Redirect URIs:
+  - `https://your-domain.example.com/`
+  - `https://your-domain.example.com/oidc-callback.html`
+  - `https://your-domain.example.com/oidc-silent-redirect.html`
+- Post Logout Redirect URIs:
+  - `https://your-domain.example.com/`
+
+### Desktop Client
+
+The desktop client is used for the OpenCloud desktop application:
+
+- Client ID: `OpenCloudDesktop`
+- Client Type: Public client
+- Redirect URIs:
+  - `http://127.0.0.1`
+  - `http://localhost`
+
+### Mobile App Clients
+
+#### Android App
+
+- Client ID: `OpenCloudAndroid`
+- Client Type: Public client
+- Redirect URIs: `oc://android.opencloud.eu`
+- Post Logout Redirect URIs: `oc://android.opencloud.eu`
+
+#### iOS App
+
+- Client ID: `OpenCloudIOS`
+- Client Type: Public client
+- Redirect URIs: `oc://ios.opencloud.eu`
+- Post Logout Redirect URIs: `oc://ios.opencloud.eu`
+
+### Additional Clients
+
+#### Cyberduck File Transfer Client
+
+- Client ID: `Cyberduck`
+- Client Type: Public client
+- Redirect URIs:
+  - `x-cyberduck-action:oauth`
+  - `x-mountainduck-action:oauth`
diff --git a/versioned_docs/version-7.x/admin/configuration/authentication-and-user-management/index.md b/versioned_docs/version-7.x/admin/configuration/authentication-and-user-management/index.md
new file mode 100644
index 000000000..b60a155d1
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/authentication-and-user-management/index.md
@@ -0,0 +1,64 @@
+---
+title: 'Internal and External IDP'
+---
+
+# Internal and External IDP
+
+OpenCloud offers two ways to handle user authentication and identity management:
+
+1. **Internal IDP**:
+   - Built into OpenCloud
+   - Targeted at smaller installations (up to 500 users)
+   - Designed for standalone or small deployments
+
+2. **External IDP**:
+   - Keycloak as the recommended OIDC provider for larger installations
+   - Support for Azure AD, EntraID, ADFS through Keycloak
+   - Enterprise-focused solution
+
+## Your Use Cases
+
+### Choose the internal IDP if you need
+
+- A simple, lightweight and minimal OpenID Connect Provider
+- Small to medium deployments
+- Minimal resource footprint
+- Quick setup with basic features
+- Ideal for development environment
+- No Multifactor Authentication (MFA) and no migration path to other IDPs
+
+### Choose Keycloak if you need
+
+- Enterprise-grade IAM solution
+- Complex authorization requirements
+- Multifactor Authentication
+- Advanced user federation
+- Fine-grained permissions
+- Multiple authentication methods
+- Large-scale deployments
+- Commercial support options
+
+### Bottom Line
+
+Keycloak is a comprehensive, enterprise-ready IAM platform with extensive features including SSO, user federation, and support for multiple protocols like OpenID Connect, OAuth 2.0, and SAML. It offers more features but requires more resources and expertise, which makes it a better fit for larger or more complex environments.
+
+## Authentication with Keycloak
+
+For production environments, we recommend using Keycloak with LDAP integration. This setup provides a robust authentication system that can scale to enterprise needs.
+
+OpenCloud now supports two authentication modes when using Keycloak with LDAP:
+
+### Shared User Directory Mode
+
+In this mode, LDAP serves as a central user directory for both Keycloak and OpenCloud.
+This setup is suitable for scenarios where the LDAP server is not under the control of the OpenCloud admin and can be connected to KeyCloak and OpenCloud using standard attributes and a read-only bind user.
+
+For detailed configuration and setup instructions, see the [Keycloak Shared User Directory](./keycloak#shared-user-directory-mode) guide.
+
+### Autoprovisioning Mode
+
+In this mode, Keycloak is holding all users and OpenCloud autoprovisions new users during first login.
+This mode is suitable in scenarios where the OpenIDConnect provider is external and not under control of the OpenCloud admin. To mitigate that lack of control, OpenCloud will use an LDAP server which is fully under the control of the OpenCloud admin to store the users and groups and additional attributes.
+OpenCloud can disable users for login to actively prevent unwanted access to the system when the workflow with the external Identity Provider is slow or indirect. In this case, the LDAP server needs an OpenCloud Schema and write access for the LDAP bind user.
+
+For detailed configuration and setup instructions, see the [Keycloak with Autoprovisioning](./keycloak#autoprovisioning-mode) guide.
diff --git a/versioned_docs/version-7.x/admin/configuration/authentication-and-user-management/keycloak-user.md b/versioned_docs/version-7.x/admin/configuration/authentication-and-user-management/keycloak-user.md
new file mode 100644
index 000000000..1e265dba6
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/authentication-and-user-management/keycloak-user.md
@@ -0,0 +1,106 @@
+---
+sidebar_position: 4
+id: keycloak-user
+title: Adding user with Keycloak
+description: Adding user with Keycloak
+draft: false
+---
+
+# Creating New Users in Keycloak for OpenCloud
+
+This guide explains how to create new users in Keycloak for OpenCloud, including "User Light" without personal spaces. While OpenCloud currently does not have a built-in "invite external user" feature, this functionality can be replicated using Keycloak.
+
+## Background
+
+One of the most frequently requested features by administrators has been support for guest or external users. Previously, this was discussed as adding external users during the sharing process. These users were provisioned on the fly and received an invite link.
+
+Although OpenCloud does not natively support this method, similar functionality can be achieved using Keycloak for user management.
+
+## Assign Admin Permissions in Keycloak
+
+To manage users and groups for OpenCloud, you need a user with administrative privileges in the Keycloak realm.
+
+- Log in to Keycloak as an admin.
+- Navigate to the OpenCloud realm
+- Assign appropriate roles (such as `manage-user` and `view-users`) to the user you want to promote.
+
+Example: A user named `dennis` is assigned as a Realm Admin.
+
+<img src={require(".././img/keycloak/add-user/set-admin-roles.png").default} alt="Add admin roles to user" width="1920"/>
+
+Once assigned, the user can log in as a Realm Administrator and access user and group management.
+
+## Add New User with standard rights (no Space)
+
+With admin permissions, you can now create users and groups:
+
+- Login in Keycloak OpenCloud Realm with the user who has admin rights under `https://keycloak.YOUR.DOMAIN/admin/openCloud/console/#/openCloud`
+
+- Navigate to the "Users" section in the Keycloak Admin Console
+
+- Click Add User
+  <img src={require(".././img/keycloak/add-user/add-user.png").default} alt="Add user" width="1920"/>
+
+- Fill in the required user details (e.g., username, email)
+  <img src={require(".././img/keycloak/add-user/fill-out-userinfo.png").default} alt="Fill out user information" width="1920"/>
+
+- Optionally assign the user to one or more groups.
+
+- Click on "Create"
+
+- Set an inital password
+
+<img src={require(".././img/keycloak/add-user/set-password.png").default} alt="Set initial user password" width="1920"/>
+
+:::note
+In the opencloud-compose setup, the default user role is `OpenCloudGuest`.  
+This means new users will not receive a personal space by default.  
+You can change the default role in "Realm Settings" under "User Registration" in the Keycloak admin console.
+
+## First Login Experience for the "User Light"
+
+When a "User Light" logs in for the first time, they will:
+
+- Be prompted to change their password
+- Update their profile (name, email, etc.)
+- Verify their email address
+
+if this was set before.
+
+After successful login, they will not receive a personal space — fulfilling the guest user requirement.
+
+<img src={require(".././img/keycloak/add-user/guest-login.png").default} alt="Guest login" width="1920"/>
+
+## Optional: Enable Self Registration
+
+You can allow users to register themselves without manual creation.
+
+To enable self-registration:
+
+- Log in to Keycloak as an admin.
+- Go to the Login settings in the OpenCloud realm.
+- Enable the User Registration option.
+
+<img src={require(".././img/keycloak/add-user/enable-self-registration.png").default} alt="Enable self registration" width="1920"/>
+
+### Self Registration Flow
+
+- Users see a Register option on the login screen.
+
+<img src={require(".././img/keycloak/add-user/register-button.png").default} alt="Register Button" width="1920"/>
+
+- They complete the registration form.
+
+<img src={require(".././img/keycloak/add-user/fill-out-registration-form.png").default} alt="Fill out the registration form" width="1920"/>
+
+After loggin in, the user has now the "User Light" Role with no personal Space.
+
+## Summary
+
+By leveraging Keycloak:
+
+- You can create and manage guest users for OpenCloud.
+- Guest users can log in without receiving a personal space.
+- You can streamline the process with self-registration.
+
+This setup provides a flexible and scalable way to manage external and lightweight users in OpenCloud through Keycloak.
diff --git a/versioned_docs/version-7.x/admin/configuration/authentication-and-user-management/keycloak.md b/versioned_docs/version-7.x/admin/configuration/authentication-and-user-management/keycloak.md
new file mode 100644
index 000000000..a56b2ebcb
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/authentication-and-user-management/keycloak.md
@@ -0,0 +1,338 @@
+---
+sidebar_position: 3
+id: keycloak
+title: Keycloak Integration
+description: Keycloak Integration
+draft: false
+---
+
+# Keycloak Integration
+
+OpenCloud supports using Keycloak as an external identity provider, providing enterprise-grade identity management capabilities. This guide explains how to set up and configure Keycloak with OpenCloud.
+This guide is divided into three main sections:
+
+- [Keycloak Integration Overview](#opencloud-configuration-for-keycloak-general): A brief overview of the integration process.
+- [Shared User Directory Mode](#configuration-for-shared-directory-mode): Keycloak and OpenCloud share a common LDAP directory for user management.
+- [Autoprovisioning Mode](#configuration-for-autoprovisioning-mode): OpenCloud autoprovisions users in a separate LDAP directory managed by OpenCloud.
+
+## OpenCloud Configuration for Keycloak (General)
+
+When using Keycloak as the identity provider, you need to understand the general configuration settings if you want to configure your custom integration.
+
+You can also use one of our predefined Docker Compose setups, which are located in the `opencloud-compose` repository. These setups include all necessary configurations for Keycloak and OpenLDAP.
+
+### Server Configuration
+
+```env
+PROXY_AUTOPROVISION_ACCOUNTS=true|false # that depends on your setup
+PROXY_ROLE_ASSIGNMENT_DRIVER=oidc
+OC_OIDC_ISSUER=https://your-domain.example.com/realms/openCloud
+WEB_OPTION_ACCOUNT_EDIT_LINK_HREF=https://your-domain.example.com/realms/openCloud/account
+PROXY_OIDC_REWRITE_WELLKNOWN=true
+PROXY_USER_OIDC_CLAIM=preferred_username|sub|uuid # this depends on your setup
+# admin and demo accounts must be created in Keycloak
+OC_ADMIN_USER_ID: ""
+SETTINGS_SETUP_DEFAULT_ASSIGNMENTS: "false"
+GRAPH_ASSIGN_DEFAULT_USER_ROLE: "false"
+GRAPH_USERNAME_MATCH=none
+OC_EXCLUDE_RUN_SERVICES=idp,idm # it is not supported to run keycloak with the built-in idm
+```
+
+Look [OpenCloud external IDP configuration](./external-idp#opencloud-configuration) for some more details about these settings.
+
+### Client Configuration
+
+The [OIDC clients](./external-idp#client-configuration) required by OpenCloud are pre-configured in the Docker Compose setup and match the clients used by the built-in IdP.
+
+### Manual Client Configuration
+
+If you need to manually configure the clients in Keycloak:
+
+1. Log in to the Keycloak admin console
+2. Select the OpenCloud realm
+3. Navigate to Clients and click Create
+4. Configure each client according to the specifications above
+5. Ensure all clients have the appropriate scopes:
+   - web-origins
+   - profile
+   - roles
+   - groups
+   - basic
+   - email
+
+### Advanced Configuration
+
+#### Backchannel Logout
+
+OpenCloud supports Keycloak's backchannel logout feature, which allows Keycloak to notify OpenCloud when a user logs out. This ensures that all sessions are properly terminated:
+
+- Backchannel Logout URL: `https://your-domain.example.com/backchannel_logout`
+- Backchannel Logout Session Required: `true`
+
+## Shared User Directory Mode
+
+```mermaid
+graph TD
+    subgraph opencloud["OpenCloud Deployment"]
+        OpenCloud["OpenCloud Server"]
+        Keycloak("Keycloak<br>(OIDC Provider)")
+    end
+    subgraph existing["Existing Infrastructure"]
+        LDAP[("LDAP Server<br>(Shared User Directory)")]
+    end
+
+    OpenCloud -->|"User and Groups are looked up for sharing"| LDAP
+    OpenCloud -->|"Reads Roles from claims"| Keycloak
+    Keycloak -->|"Verify credentials"| LDAP
+    LDAP -->|"Import Users and Groups"| Keycloak
+
+    classDef service fill:#3498db,stroke:#2c3e50,stroke-width:2px,rx:10px,ry:10px;
+    classDef storage fill:#2ecc71,stroke:#27ae60,stroke-width:2px,rx:10px,ry:10px;
+    classDef readonly fill:#87CEFA,stroke:#4682B4,stroke-width:3px,rx:10px,ry:10px;
+    classDef general stroke-width:2px,rx:10px,ry:10px;
+
+    class OpenCloud,Keycloak service;
+    class LDAP storage;
+    class existing,directory readonly;
+    class opencloud general;
+```
+
+In this mode, a readable LDAP Directory with existing users serves as a central user directory for both Keycloak and OpenCloud.
+
+Key characteristics:
+
+- LDAP is the source of truth for user information
+- The LDAP server uses standard attributes (uid, cn, sn, givenName, mail)
+- A common unique identifier (e.g. `entryUUID` or `objectGUID`) guarantees stable user mapping even if users are changing
+- Both Keycloak and OpenCloud read user data directly from LDAP
+- User accounts must exist in LDAP before they can log in or receive shares
+- LDAP is configured as read-only for OpenCloud
+- OpenCloud can create custom groups only if a subtree of the read-only LDAP can be writable
+
+### LDAP Assumptions for Shared Directory Mode
+
+OpenCloud can work with any LDAP schema containing standard attributes:
+
+- User attributes: `uid`, `cn`, `sn`, `givenName`, `mail`
+- Groups are stored in a dedicated organizational unit
+- Default configuration sets LDAP as read-only
+
+Example LDAP Structure:
+
+```bash
+dc=example,dc=org              # Base DN
+├── ou=users                   # User organizational unit
+│   ├── uid=user1              # User entries
+│   └── uid=user2
+└── ou=groups                  # Group organizational unit
+    ├── cn=admins              # Group entries
+    ├── cn=users
+    └── ou=custom (optional)   # Optional custom groups tree, writable by OpenCloud
+        ├── cn=teamA           # Custom Group entries
+        └── cn=teamB
+```
+
+:::tip
+
+It is possible to use a writable subtree of the LDAP server for custom groups. This is useful if you want to create groups in OpenCloud that are not managed by Keycloak.
+
+This feature is optional and can be disabled by setting `GRAPH_LDAP_GROUP_CREATE_BASE_DN` to an empty string.
+
+:::
+
+### Configuration for Shared Directory Mode
+
+Keycloak and OpenCloud can be configured using environment variables:
+
+```bash
+# Basic Keycloak configuration
+KEYCLOAK_DOMAIN=keycloak.example.org
+KEYCLOAK_REALM=openCloud
+
+# OpenCloud OIDC configuration
+OC_OIDC_ISSUER=https://${KEYCLOAK_DOMAIN:-keycloak.opencloud.test}/realms/${KEYCLOAK_REALM:-openCloud}
+WEB_OPTION_ACCOUNT_EDIT_LINK_HREF=https://${KEYCLOAK_DOMAIN:-keycloak.opencloud.test}/realms/${KEYCLOAK_REALM:-openCloud}/account
+PROXY_OIDC_REWRITE_WELLKNOWN=true
+PROXY_USER_OIDC_CLAIM=uuid # this claim needs to be configured in the keycloak realm to use the keycloak user id
+PROXY_USER_CS3_CLAIM=userid
+# admin and demo accounts must be created in Keycloak
+OC_ADMIN_USER_ID=""
+SETTINGS_SETUP_DEFAULT_ASSIGNMENTS=false
+GRAPH_ASSIGN_DEFAULT_USER_ROLE=false
+GRAPH_USERNAME_MATCH=none
+
+# OpenCloud LDAP configuration
+OC_LDAP_URI=ldaps://ldap-server:1636
+OC_LDAP_SERVER_WRITE_ENABLED=false # assuming the external ldap main tree is not writable
+# Disable non writable attributes in the OpenCloud Admin UI
+FRONTEND_READONLY_USER_ATTRIBUTES="user.onPremisesSamAccountName,user.displayName,user.mail,user.passwordProfile,user.accountEnabled,user.appRoleAssignments"
+OC_LDAP_INSECURE=true
+OC_LDAP_BIND_DN=cn=admin,dc=opencloud,dc=eu
+OC_LDAP_BIND_PASSWORD=admin-password
+OC_LDAP_USER_BASE_DN=ou=users,dc=opencloud,dc=eu
+OC_LDAP_USER_SCHEMA_ID=entryUUID
+OC_LDAP_DISABLE_USER_MECHANISM=none
+OC_LDAP_GROUP_BASE_DN=ou=groups,dc=opencloud,dc=eu
+OC_LDAP_GROUP_SCHEMA_ID=entryUUID
+# Custom groups feature when a writable subtree is available
+GRAPH_LDAP_GROUP_CREATE_BASE_DN=ou=custom,ou=groups,dc=opencloud,dc=eu
+GRAPH_LDAP_SERVER_UUID=true
+
+```
+
+### Example Docker Compose Configuration - Shared Directory Mode
+
+OpenCloud provides complete example deployments using Docker Compose:
+
+1. Navigate to the `opencloud-compose` repository
+2. Edit the `.env` file to enable the Shared Directory Mode:
+
+For Shared Directory Mode:
+
+```bash
+# Enable services
+COMPOSE_FILE=docker-compose.yml:idm/ldap-keycloak.yml:traefik/opencloud.yml:traefik/ldap-keycloak.yml
+# Your public keycloak domain without protocol
+KEYCLOAK_DOMAIN=your-keycloak-domain.example.com
+# Admin user login name. Defaults to "kcadmin".
+KEYCLOAK_ADMIN=
+# Admin user login password. Defaults to "admin".
+KEYCLOAK_ADMIN_PASSWORD=
+```
+
+The Docker Compose file `idm/ldap-keycloak.yml` contains the complete configuration for each component.
+
+Keycloak is configured during startup by importing the `keycloak-realm.dist.json` file. This file contains the configuration for the OpenCloud realm, including client settings, roles, and user federation. This file is located in the `config/keycloak` directory of the `opencloud-compose` repository.
+
+:::warning
+
+Keycloak can import the realm configuration file only once during the first startup. If you need to change the configuration, you must delete the Keycloak container and volume and restart it. This will reset Keycloak to its initial state.
+
+:::
+
+## Autoprovisioning Mode
+
+In this mode, Keycloak is holding all users and OpenCloud autoprovisions new users during first login.
+This mode is suitable in scenarios where the OpenIDConnect provider is external and not under control of the OpenCloud admin. To mitigate that lack of control, OpenCloud will use an LDAP server which is fully under the control of the OpenCloud admin to store the users and groups and additional attributes.
+
+```mermaid
+graph TD
+    subgraph opencloud["OpenCloud Deployment"]
+        LDAP[("`LDAP Server
+            - managed by opencloud
+            - custom schema`")]
+        OpenCloud["`OpenCloud Server`"]
+        Stop((("Block <br>disabled<br>Users")))
+    end
+    subgraph existing["Existing Infrastructure"]
+        Keycloak("`Keycloak<br>(OIDC Provider)`")
+        UserDirectory[("`Federated Identity Provider
+        - Microsoft
+        - Google
+        - and others`")]
+    end
+
+    OpenCloud -->|"User and Groups are created during first user login"| LDAP
+    OpenCloud <-->|"User and Groups are looked up for sharing"| LDAP
+    OpenCloud -- "Reads Users, Attributes, Group memberships and Roles from OIDC claims" --> Stop --> Keycloak
+    UserDirectory -->|"Import Users and Groups"| Keycloak
+
+    classDef service fill:#3498db,stroke:#2c3e50,stroke-width:2px,rx:10px,ry:10px;
+    classDef storage fill:#2ecc71,stroke:#27ae60,stroke-width:2px,rx:10px,ry:10px;
+    classDef readonly fill:#87CEFA,stroke:#4682B4,stroke-width:3px,rx:10px,ry:10px;
+    classDef general stroke-width:2px,rx:10px,ry:10px;
+
+    class OpenCloud,Keycloak service;
+    class LDAP storage;
+    class existing,directory readonly;
+    class opencloud general;
+```
+
+- Keycloak manages the users, groups, and roles
+- The OpenCloud Clients and Sessions are configured in Keycloak
+- Simplified user management with "just-in-time" provisioning
+- Federation with external identity providers is supported (e.g., Google, GitHub, Facebook, Microsoft)
+- In this case, we need to provide an LDAP server which is fully controlled by OpenCloud and needs a custom [LDAP Schema](https://github.com/opencloud-eu/opencloud-compose/blob/main/config/ldap/schemas/10_opencloud_schema.ldif).
+
+### Configuration for Autoprovisioning Mode
+
+Keycloak, OpenCloud and OpenLDAP can be configured using environment variables:
+
+```bash
+# Basic Keycloak configuration
+KEYCLOAK_DOMAIN=keycloak.example.org
+KEYCLOAK_REALM=openCloud
+
+# OpenCloud OIDC configuration
+OC_OIDC_ISSUER=https://${KEYCLOAK_DOMAIN:-keycloak.opencloud.test}/realms/${KEYCLOAK_REALM:-openCloud}
+WEB_OPTION_ACCOUNT_EDIT_LINK_HREF=https://${KEYCLOAK_DOMAIN:-keycloak.opencloud.test}/realms/${KEYCLOAK_REALM:-openCloud}/account
+PROXY_OIDC_REWRITE_WELLKNOWN=true
+PROXY_USER_OIDC_CLAIM=sub
+PROXY_AUTOPROVISION_CLAIM_USERNAME=sub
+PROXY_USER_CS3_CLAIM=username
+# admin and demo accounts must be created in Keycloak
+OC_ADMIN_USER_ID=""
+SETTINGS_SETUP_DEFAULT_ASSIGNMENTS=false
+GRAPH_ASSIGN_DEFAULT_USER_ROLE=false
+GRAPH_USERNAME_MATCH=none
+
+# OpenCloud LDAP configuration
+OC_LDAP_URI=ldaps://ldap-server:1636
+OC_LDAP_SERVER_WRITE_ENABLED=true
+# Disable non writable attributes in the OpenCloud Admin UI
+FRONTEND_READONLY_USER_ATTRIBUTES="user.onPremisesSamAccountName,user.displayName,user.mail,user.passwordProfile,user.memberOf"
+OC_LDAP_INSECURE=true
+OC_LDAP_BIND_DN=cn=admin,dc=opencloud,dc=eu
+OC_LDAP_BIND_PASSWORD=admin-password
+OC_LDAP_USER_BASE_DN=ou=users,dc=opencloud,dc=eu
+OC_LDAP_DISABLE_USER_MECHANISM=none
+OC_LDAP_GROUP_BASE_DN=ou=groups,dc=opencloud,dc=eu
+```
+
+### Example Docker Compose Configuration - Autoprovisioning Mode
+
+OpenCloud provides complete example deployments using Docker Compose:
+
+1. Navigate to the `opencloud-compose` repository
+2. Edit the `.env` file to enable the Autoprovisioning Mode:
+
+For Autoprovisioning Mode:
+
+```bash
+# Enable services
+COMPOSE_FILE=docker-compose.yml:idm/external-idp.yml:traefik/opencloud.yml
+# Your public keycloak domain without protocol
+IDP_DOMAIN=your-idp-domain.example.com
+# The openCloud users need to be able to edit their account in the external IdP
+IDP_ACCOUNT_URL=https://your-idp-domain.example.com/realms/openCloud/account
+```
+
+The Docker Compose file `idm/external-idp.yml` contains the complete configuration for each OpenCloud component. The file `10_opencloud_ldap_schema.ldif` contains the OpenCloud LDAP schema and is loaded during the startup of the OpenLdap container. In this mode, your IdP setup is not part of the OpenCloud Deployment.
+
+:::warning
+
+Your external IdP configuration must match the settings described in the [Client Configuration](#client-configuration) section above.
+
+Your external IdP must provide the required claims for user provisioning and role assignment.
+
+Claims:
+
+- `sub`: Unique identifier for the user (used as username in OpenCloud)
+- `roles`: List of roles assigned to the user (used for role assignment in OpenCloud)
+- `name`: User's full name (optional, used for display purposes)
+- `preferred_username`: User's preferred username (optional, more intuitive during login)
+- `email`: User's email address (optional, used for notifications)
+- `groups`: List of groups the user belongs to (optional, used for group assignments in OpenCloud)
+
+:::
+
+## Troubleshooting
+
+Common issues and solutions:
+
+- User cannot log in:
+  - Check LDAP connectivity and user existence
+  - Check if each user has an OpenCloud Role assigned
+  - Verify that the client IDs and redirect URIs match exactly
+- Groups not synchronized: Verify group mappings in Keycloak
+- User creation fails (autoprovisioning mode): Ensure LDAP has write permissions in Autoprovisioning Mode
diff --git a/versioned_docs/version-7.x/admin/configuration/collabora/_category_.json b/versioned_docs/version-7.x/admin/configuration/collabora/_category_.json
new file mode 100644
index 000000000..d3a23ec15
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/collabora/_category_.json
@@ -0,0 +1,8 @@
+{
+  "label": "Collabora",
+  "position": 30,
+  "link": {
+    "type": "doc",
+    "id": "collabora"
+  }
+}
diff --git a/versioned_docs/version-7.x/admin/configuration/collabora/collabora-fonts.md b/versioned_docs/version-7.x/admin/configuration/collabora/collabora-fonts.md
new file mode 100644
index 000000000..c175632df
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/collabora/collabora-fonts.md
@@ -0,0 +1,44 @@
+---
+sidebar_position: 10
+id: collabora-fonts
+title: Collabora additional fonts
+description: How to add additional fonts to Collabora
+draft: false
+---
+
+# Installing Additional Fonts for Collabora
+
+By default, Collabora Online provides only a limited set of fonts.  
+To ensure proper document rendering — especially for Microsoft Office documents — you may want to install additional font packages such as `ttf-mscorefonts` or other TrueType/OpenType fonts on your server.
+
+## 1. Access the Server and Update System Packages
+
+Before installing new fonts, make sure your system packages are up to date:
+
+```bash
+apt update
+```
+
+## 2. Install Microsoft Core Fonts
+
+Install the Microsoft Core Fonts package to add common fonts such as Arial or Comic Sans MS:
+
+```bash
+apt install ttf-mscorefonts-installer
+```
+
+During the installation, you will be prompted to accept the EULA (End User License Agreement).
+
+<img src={require("../img/collabora/accept-eula.png").default} alt="Accept EULA" width="1920"/>
+
+## 3. Restart Collabora
+
+After the installation is complete, restart your docker-compose setup to apply the changes:
+
+```bash
+docker compose restart
+```
+
+Once restarted, Collabora will recognize the newly installed fonts, and they will be available when editing documents.
+
+<img src={require("../img/collabora/new-fonts.png").default} alt="New Fonts added" width="1920"/>
diff --git a/versioned_docs/version-7.x/admin/configuration/collabora/collabora-ms-office-formats.md b/versioned_docs/version-7.x/admin/configuration/collabora/collabora-ms-office-formats.md
new file mode 100644
index 000000000..5f2ce7243
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/collabora/collabora-ms-office-formats.md
@@ -0,0 +1,110 @@
+---
+sidebar_position: 20
+id: collabora-ms-office-formats
+title: Enable MS-Office formats
+description: How to enable MS-Office formats
+draft: false
+---
+
+## Enable Microsoft file formats in the New menu
+
+:::note
+Starting with version 5.2.0, OpenCloud no longer enables Microsoft file formats as default creation options in the New menu. To make them available again, you must define them explicitly in `app-registry.yaml`.
+:::
+
+### Create the configuration file
+
+Create an `app-registry.yaml` file in your OpenCloud configuration directory.
+
+This change cannot be applied in setups that use internal Docker volumes only, because the config directory is not available directly on the host.
+
+For production deployments, bind-mounted volumes are recommended, as they provide a predictable host path for configuration, persistence, and backups.
+
+If your deployment uses a bind mount for the OpenCloud config directory, place the file in the mapped config directory on the host system. The exact path depends on your Docker Compose setup and may differ from `config/opencloud`.
+
+Example:
+
+````bash
+/path/to/your/opencloud/config/app-registry.yaml
+
+Insert following content:
+
+```yaml
+app_registry:
+  mimetypes:
+    - mime_type: application/pdf
+      extension: pdf
+      name: PDF
+      description: PDF document
+      icon: ''
+      default_app: ''
+      allow_creation: false
+    - mime_type: application/vnd.oasis.opendocument.text
+      extension: odt
+      name: Document
+      description: OpenDocument text document
+      icon: ''
+      default_app: Collabora
+      allow_creation: true
+    - mime_type: application/vnd.oasis.opendocument.spreadsheet
+      extension: ods
+      name: Spreadsheet
+      description: OpenDocument spreadsheet document
+      icon: ''
+      default_app: Collabora
+      allow_creation: true
+    - mime_type: application/vnd.oasis.opendocument.presentation
+      extension: odp
+      name: Presentation
+      description: OpenDocument presentation document
+      icon: ''
+      default_app: Collabora
+      allow_creation: true
+    - mime_type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
+      extension: docx
+      name: Microsoft Word
+      description: Microsoft Word document
+      icon: ''
+      default_app: Collabora
+      allow_creation: true
+    - mime_type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
+      extension: xlsx
+      name: Microsoft Excel
+      description: Microsoft Excel document
+      icon: ''
+      default_app: Collabora
+      allow_creation: true
+    - mime_type: application/vnd.openxmlformats-officedocument.presentationml.presentation
+      extension: pptx
+      name: Microsoft PowerPoint
+      description: Microsoft PowerPoint document
+      icon: ''
+      default_app: Collabora
+      allow_creation: true
+````
+
+### Verify ownership and permissions
+
+:::important UID/GID and volume permissions
+Make sure that `app-registry.yaml` can be read by the user running the OpenCloud container. Incorrect ownership or permissions on mounted files can prevent OpenCloud from using the configuration.
+:::
+
+By default, OpenCloud uses:
+
+```bash
+UID=1000
+GID=1000
+```
+
+Adjust the file ownership and permissions if your container runs with different values.
+
+### Restart OpenCloud
+
+Restart your deployment after creating the file:
+
+```bash
+docker compose down
+docker compose up -d
+```
+
+After the restart, Microsoft formats such as Word, Excel, and PowerPoint are available again in the New menu.
diff --git a/versioned_docs/version-7.x/admin/configuration/collabora/index.md b/versioned_docs/version-7.x/admin/configuration/collabora/index.md
new file mode 100644
index 000000000..0674bb3bd
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/collabora/index.md
@@ -0,0 +1,22 @@
+---
+sidebar_position: 1
+id: collabora
+title: Collabora
+description: Configuration guides for Collabora integration in OpenCloud
+draft: false
+---
+
+# Collabora
+
+This section collects the most common Collabora configuration topics for OpenCloud.
+It is meant as a quick entry point for administrators who want to improve document compatibility and editing experience.
+
+## What you will find here
+
+- Add additional fonts so documents render more reliably across systems.
+- Enable Microsoft Office formats in the New menu when you want to create `.docx`, `.xlsx`, or `.pptx` files directly.
+
+## Guides
+
+- [Install additional fonts](./collabora-fonts)
+- [Enable MS-Office formats](./collabora-ms-office-formats)
diff --git a/versioned_docs/version-7.x/admin/configuration/default-language.md b/versioned_docs/version-7.x/admin/configuration/default-language.md
new file mode 100644
index 000000000..dceb9b419
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/default-language.md
@@ -0,0 +1,43 @@
+---
+sidebar_position: 100
+id: default-language
+title: Default Language
+description: Set the default language
+draft: false
+---
+
+# Set the default language
+
+By default, OpenCloud uses English (en) as its interface language, unless a different language is explicitly configured.
+OpenCloud relies on ISO 639-1 language codes for language selection.
+You can find the complete list of supported languages here: [Supported languages](../resources/faq#miscellaneous)
+
+## Edit the `.env` File
+
+Open the environment configuration file located in your `opencloud-compose` directory:
+
+```bash
+nano opencloud-compose/.env
+```
+
+Configure the default language using the following environment variable:
+
+```env
+# The default language used by services and the WebUI.
+# Uses ISO 639-1 language codes (e.g. "en", "de", "fr").
+# Defaults to English if not set.
+DEFAULT_LANGUAGE="language code"
+```
+
+## Restart Docker Services
+
+After saving the file, shut down and restart the Docker containers to apply the changes:
+
+```bash
+docker compose down
+docker compose up -d
+```
+
+## Result
+
+OpenCloud is now fully displayed in the language configured in the .env file.
diff --git a/versioned_docs/version-7.x/admin/configuration/frontend-update-check.md b/versioned_docs/version-7.x/admin/configuration/frontend-update-check.md
new file mode 100644
index 000000000..950e109cf
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/frontend-update-check.md
@@ -0,0 +1,49 @@
+---
+sidebar_position: 35
+id: frontend-check-updates
+title: Frontend Update check
+description: How to disable the frontend check for updates in OpenCloud.
+draft: false
+---
+
+# Disable frontend update check
+
+By default, OpenCloud performs a frontend check to verify if you are running the latest version.
+
+:::note
+
+When the frontend update check detects a security-critical upgrade, administrators may see a warning in the lower-left corner of the web interface. This warning indicates that the available upgrade should be reviewed and applied with priority.
+
+:::
+
+<img src={require("./img/frontend-update-check/check-true.png").default} alt="check is true" width="520"/>
+<img src={require("./img/frontend-update-check/check-true-critical.png").default} alt="critical check is true" width="520"/>
+
+## Edit the `.env` File
+
+Open the environment configuration file located in your `opencloud-compose` directory:
+
+```bash
+nano opencloud-compose/.env
+```
+
+Set the `FRONTEND_CHECK_FOR_UPDATES` environment variable to `false` to disable the frontend check for updates:
+
+```env
+FRONTEND_CHECK_FOR_UPDATES=false
+```
+
+## Restart Docker Services
+
+After saving the file, shut down and restart the Docker containers to apply the changes:
+
+```bash
+docker compose down
+docker compose up -d
+```
+
+## Result
+
+The frontend will no longer display a message about newer versions being available.
+
+<img src={require("./img/frontend-update-check/check-false.png").default} alt="check is false" width="520"/>
diff --git a/versioned_docs/version-7.x/admin/configuration/img/app-store.png b/versioned_docs/version-7.x/admin/configuration/img/app-store.png
new file mode 100644
index 000000000..51b8c9de6
Binary files /dev/null and b/versioned_docs/version-7.x/admin/configuration/img/app-store.png differ
diff --git a/versioned_docs/version-7.x/admin/configuration/img/collabora/accept-eula.png b/versioned_docs/version-7.x/admin/configuration/img/collabora/accept-eula.png
new file mode 100644
index 000000000..772aa08b3
Binary files /dev/null and b/versioned_docs/version-7.x/admin/configuration/img/collabora/accept-eula.png differ
diff --git a/versioned_docs/version-7.x/admin/configuration/img/collabora/new-fonts.png b/versioned_docs/version-7.x/admin/configuration/img/collabora/new-fonts.png
new file mode 100644
index 000000000..3ababdbc6
Binary files /dev/null and b/versioned_docs/version-7.x/admin/configuration/img/collabora/new-fonts.png differ
diff --git a/versioned_docs/version-7.x/admin/configuration/img/decomposeds3-with-minio.png b/versioned_docs/version-7.x/admin/configuration/img/decomposeds3-with-minio.png
new file mode 100644
index 000000000..d53e7ff04
Binary files /dev/null and b/versioned_docs/version-7.x/admin/configuration/img/decomposeds3-with-minio.png differ
diff --git a/versioned_docs/version-7.x/admin/configuration/img/frontend-update-check/check-false.png b/versioned_docs/version-7.x/admin/configuration/img/frontend-update-check/check-false.png
new file mode 100644
index 000000000..daa2f160c
Binary files /dev/null and b/versioned_docs/version-7.x/admin/configuration/img/frontend-update-check/check-false.png differ
diff --git a/versioned_docs/version-7.x/admin/configuration/img/frontend-update-check/check-true-critical.png b/versioned_docs/version-7.x/admin/configuration/img/frontend-update-check/check-true-critical.png
new file mode 100644
index 000000000..9752ff5b9
Binary files /dev/null and b/versioned_docs/version-7.x/admin/configuration/img/frontend-update-check/check-true-critical.png differ
diff --git a/versioned_docs/version-7.x/admin/configuration/img/frontend-update-check/check-true.png b/versioned_docs/version-7.x/admin/configuration/img/frontend-update-check/check-true.png
new file mode 100644
index 000000000..4be5cf580
Binary files /dev/null and b/versioned_docs/version-7.x/admin/configuration/img/frontend-update-check/check-true.png differ
diff --git a/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/add-user.png b/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/add-user.png
new file mode 100644
index 000000000..26d97b3c9
Binary files /dev/null and b/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/add-user.png differ
diff --git a/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/enable-self-registration.png b/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/enable-self-registration.png
new file mode 100644
index 000000000..850919055
Binary files /dev/null and b/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/enable-self-registration.png differ
diff --git a/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/fill-out-registration-form.png b/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/fill-out-registration-form.png
new file mode 100644
index 000000000..7b6a4b8d5
Binary files /dev/null and b/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/fill-out-registration-form.png differ
diff --git a/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/fill-out-userinfo.png b/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/fill-out-userinfo.png
new file mode 100644
index 000000000..1cf5f03ff
Binary files /dev/null and b/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/fill-out-userinfo.png differ
diff --git a/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/guest-login.png b/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/guest-login.png
new file mode 100644
index 000000000..1916c7a29
Binary files /dev/null and b/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/guest-login.png differ
diff --git a/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/register-button.png b/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/register-button.png
new file mode 100644
index 000000000..a5056e759
Binary files /dev/null and b/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/register-button.png differ
diff --git a/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/set-admin-roles.png b/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/set-admin-roles.png
new file mode 100644
index 000000000..9135e76d3
Binary files /dev/null and b/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/set-admin-roles.png differ
diff --git a/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/set-password.png b/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/set-password.png
new file mode 100644
index 000000000..026944e24
Binary files /dev/null and b/versioned_docs/version-7.x/admin/configuration/img/keycloak/add-user/set-password.png differ
diff --git a/versioned_docs/version-7.x/admin/configuration/img/login-page.png b/versioned_docs/version-7.x/admin/configuration/img/login-page.png
new file mode 100644
index 000000000..0a8306f29
Binary files /dev/null and b/versioned_docs/version-7.x/admin/configuration/img/login-page.png differ
diff --git a/versioned_docs/version-7.x/admin/configuration/index.md b/versioned_docs/version-7.x/admin/configuration/index.md
new file mode 100644
index 000000000..06a6f016f
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/index.md
@@ -0,0 +1,24 @@
+---
+sidebar_position: 0
+id: admin-configuration
+title: Configuration
+description: Overview of OpenCloud administration configuration topics
+---
+
+# Configuration
+
+Use these guides to tune OpenCloud behavior, integrations, and default settings.
+
+## In this section
+
+- [Authentication and Identity Management](./authentication-and-user-management/) - Internal and external IDP setup
+- [Storage](./storage/) - Storage drivers and backend setup
+- [Collabora](./collabora/) - Collabora integration and document compatibility
+- [Default Language](./default-language.md)
+- [Frontend Update Check](./frontend-update-check.md)
+- [Link Password Policy](./link-password-policy.md)
+- [Logging](./logging.md)
+- [Mail Notifications](./mail-notifications.md)
+- [Radicale Integration](./radicale-integration.md)
+- [Set Default Quota](./set-default-quota.md)
+- [Web Applications](./web-applications.md)
diff --git a/versioned_docs/version-7.x/admin/configuration/link-password-policy.md b/versioned_docs/version-7.x/admin/configuration/link-password-policy.md
new file mode 100644
index 000000000..3b7212037
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/link-password-policy.md
@@ -0,0 +1,107 @@
+---
+sidebar_position: 90
+id: link-password-policy
+title: Public Links - Password Enforcement and Configuration
+description: Remove the password enforcement and configure the passwords requirements for public links
+draft: false
+---
+
+# Public Links: Password Enforcement and Policy
+
+OpenCloud provides two related controls for passwords on public links:
+
+1. Password enforcement for public links (whether a password is required at all).
+2. Password policy (how strong a password must be, if a password is used/required).
+
+This guide shows how to configure both via `opencloud-compose/.env`.
+
+## Configure Password Enforcement for Public Links
+
+By default, OpenCloud requires a password for public shares. You can disable that requirement globally and (optionally) still require passwords for writable public links.
+
+### Disable the password requirement for all public links
+
+```env
+OC_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD=false
+```
+
+Require a password for writable public links only
+
+```env
+OC_SHARING_PUBLIC_WRITEABLE_SHARE_MUST_HAVE_PASSWORD=true
+```
+
+This setting only applies when `OC_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD` is set to false.
+
+## Configure Password Policy for Public Link Passwords
+
+OpenCloud can enforce strong(er) passwords by requiring occurrences of characters across different classes. You can individually configure the minimum number of:
+
+- lower-case characters
+
+- upper-case characters
+
+- digits
+
+- special characters
+
+that must appear in a valid password (and also set a minimum length).
+
+Add or adjust these variables in your .env file:
+
+### Enable/disable password policy checks
+
+- true = policy disabled (no complexity requirements enforced)
+- false = policy enabled (requirements below are enforced)
+
+```env
+OC_PASSWORD_POLICY_DISABLED=false
+```
+
+### Minimum password length
+
+```env
+OC_PASSWORD_POLICY_MIN_CHARACTERS=8
+```
+
+### Minimum character-class requirements
+
+```env
+OC_PASSWORD_POLICY_MIN_LOWERCASE_CHARACTERS=1
+OC_PASSWORD_POLICY_MIN_UPPERCASE_CHARACTERS=1
+OC_PASSWORD_POLICY_MIN_DIGITS=1
+OC_PASSWORD_POLICY_MIN_SPECIAL_CHARACTERS=1
+```
+
+### Optional: Path to a 'banned passwords list' file
+
+```env
+OC_PASSWORD_POLICY_BANNED_PASSWORDS_LIST=""
+```
+
+The password policy only applies when a password is set/required for a public link.
+
+More information is available in the [developer documentation on password policy](../../dev/server/services/frontend/information#passwords).
+
+## Edit the .env File
+
+Open the environment configuration file located in your opencloud-compose directory:
+
+```bash
+nano opencloud-compose/.env
+```
+
+Add or modify the variables from the sections above as needed, then save the file.
+
+## Restart Docker Services
+
+After saving the file, shut down and restart the Docker containers to apply the changes:
+
+```bash
+docker compose down
+docker compose up -d
+```
+
+:::note
+This change applies globally to all public shares created after the restart.
+:::
diff --git a/versioned_docs/version-7.x/admin/configuration/logging.md b/versioned_docs/version-7.x/admin/configuration/logging.md
new file mode 100644
index 000000000..5d389bd99
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/logging.md
@@ -0,0 +1,51 @@
+---
+sidebar_position: 100
+id: logging
+title: Logging
+description: Logging in OpenCloud
+draft: false
+---
+
+# Logging in OpenCloud
+
+Logging helps monitor OpenCloud’s health and diagnose issues. Log output varies by level, from minimal to detailed. By default, logs are written to `stderr`. In Docker deployments, logs are accessible via `docker logs`.
+
+## Log Levels
+
+Set the global log level in your `.env` file using `LOG_LEVEL`, which maps to `OC_LOG_LEVEL`. The default is `error`.
+
+If you want to change the log level for individual services, define the corresponding service-specific variables in the `environment:` section of the relevant service in `docker-compose.yaml`, for example `PROXY_LOG_LEVEL=info` or `SHARING_LOG_LEVEL=info`.
+
+## The log levels are
+
+### FATAL
+
+Critical issues that cause the application to shut down — such as config errors or missing dependencies.
+
+### ERROR
+
+Severe problems that block proper operation and require admin attention.
+
+### WARN
+
+Unexpected conditions that don’t stop the app but may need investigation.
+
+### INFO
+
+Routine events that confirm expected behavior and operation.
+
+### DEBUG
+
+Highly detailed messages for diagnosing problems. Use cautiously in production due to verbosity.
+
+## Request Correlation
+
+### X-Request-ID
+
+OpenCloud supports tracing using the `X-Request-ID` header. Clients send a UUID v4 with each request, which is included in backend logs for correlation.
+
+To manually test with `curl`, add:
+
+```bash
+--header "X-Request-ID: <your-id>"
+```
diff --git a/versioned_docs/version-7.x/admin/configuration/mail-notifications.md b/versioned_docs/version-7.x/admin/configuration/mail-notifications.md
new file mode 100644
index 000000000..ecaa62673
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/mail-notifications.md
@@ -0,0 +1,66 @@
+---
+sidebar_position: 40
+id: mail-notifications
+title: Mail Notifications
+description: How to activate mail notifications in OpenCloud
+draft: false
+---
+
+# Mail notifications in OpenCloud
+
+This guide shows how to configure your OpenCloud instance to send notification E-Mails by modifying the `.env` file in your OpenCloud setup
+
+## Open the .env File
+
+Edit the file with your preferred text editor:
+
+```bash
+nano .env
+```
+
+Or use vim, code, or gedit as you prefer.
+
+## Add or modify these Environment Variables
+
+Adjust the following lines in your `.env` file according to your SMTP provider and requirements.  
+Note: `SMTP_TRANSPORT_ENCRYPTION` and `SMTP_INSECURE` may vary depending on your setup.
+
+SMTP Settings:
+
+```env
+SMTP_HOST=YOUR_SMTP_HOST
+SMTP_PORT=1025
+SMTP_SENDER=noreply@your.text
+SMTP_USERNAME=YOUR_USERNAME
+SMTP_PASSWORD=YOUR_PASSWORD
+SMTP_TRANSPORT_ENCRYPTION=none
+SMTP_INSECURE=true
+SMTP_AUTHENTICATION=auto
+```
+
+See section [Environment Variables](../../dev/server/services/notifications/env-vars.mdx) in the developers documentation for possible values for these variables. Note, that the environment variables are prefixed with `NOTIFICATIONS_`, so `NOTIFICATIONS_SMTP_AUTHENTICATION` shows possible values for `SMTP_AUTHENTICATION` in the `.env` file.
+
+Per default the `notifications` service is disabled. To send out notifications, the service must be enabled via:
+
+```env
+START_ADDITIONAL_SERVICES="notifications"
+```
+
+:::warning
+In the .env file, values should be written without quotation marks. Do not use 'single quotes' or "double quotes" — just enter the plain value.
+:::
+
+## Save and exit
+
+For nano, press Ctrl + O to save and Ctrl + X to exit.
+
+## Restart OpenCloud
+
+Apply the changes by restarting the OpenCloud services:
+
+```bash
+docker compose down
+docker compose up -d
+```
+
+OpenCloud is now successfully configured to deliver notification emails, including those triggered by actions such as file sharing.
diff --git a/versioned_docs/version-7.x/admin/configuration/radicale-integration.md b/versioned_docs/version-7.x/admin/configuration/radicale-integration.md
new file mode 100644
index 000000000..b0f8877a0
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/radicale-integration.md
@@ -0,0 +1,73 @@
+---
+sidebar_position: 50
+id: radicale-integration
+title: Calendar and Contacts Integration with Radicale
+description: How to enable Calendar and Contacts integration via Radicale in OpenCloud
+draft: false
+---
+
+# Integration with Radicale
+
+OpenCloud is able to act as an authenticating reverse proxy for the open-source
+CalDAV and CardDAV Server [Radicale](https://radicale.org). With that, users
+get a calender- and contacts server out of the box with OpenCloud that can be
+used with a wide selection of desktop- and mobile clients without hassle.
+
+The `opencloud-compose` deployment example already contains all the required pieces to
+setup the integration. This guide explains the required steps to achieve that.
+
+:::note
+The calendar and contacts feature is - until further notice - intended for
+non-customers, i.e. please note that it is not covered under our enterprise
+license, and we do not provide professional support for it. This means that
+this feature is maintained and supported on best effort without warranty.
+:::
+
+## Setting up Calendar and Contacts Integration with Radicale
+
+To use this feature you need at least OpenCloud Version 2.3.0. Earlier releases lack
+some of the required features. This guide assumes that you already have a running
+deployment based on the `opencloud-compose` deployment example.
+
+### Configure the `.env` file to deploy Radicale
+
+In the root directory of the `opencloud-compose` deployment example,
+add the radicale component to the `COMPOSE_FILE` variable in your `.env` file or add it directly to the startup command:
+
+```bash
+COMPOSE_FILE=docker-compose.yml:traefik/opencloud.yml:radicale/radicale.yml
+```
+
+or `docker compose -f docker-compose.yml -f traefik/opencloud.yml -f radicale/radicale.yml up`
+
+### Update the deployment
+
+```bash
+docker compose up -d
+```
+
+This will launch an additional container (called `radicale`) using the
+`opencloudeu/radicale` container image and reconfigure the OpenCloud instance
+to automatically forward all authenticated traffic on
+`https://<your.opencloud.domain>/caldav` and
+`https://<your.opencloud.admin>/carddav` to the radicale container adding
+information about the authenticated users.
+
+Radicale is configured to automatically create default calendar and address book for every authenticated user.
+
+## Accessing the Calendar and Address Book
+
+Users should now be able to access their address book and calendar with any
+capable CalDAV/CardDAV software (OpenCloud does currently not provide any UI
+to access them).
+
+As very few clients currently support authentication via OpenID Connect you can use
+the "App Token" feature in the user's settings page to generate an application specific
+password that can be used for authentication in most existing CalDAV/CardDAV clients.
+
+As OpenCloud implements support for the `.well-known/carddav` and `.well-known/caldav`
+endpoint. Many clients are able to automatically discover existing calendars and
+address books. So the only thing that is needed for those clients to work is
+to set `https://<your.opencloud.domain>` as the target URL for calendars and
+address books together with the OpenCloud username as the username and the
+generated app token as the password for authentication.
diff --git a/versioned_docs/version-7.x/admin/configuration/set-default-quota.md b/versioned_docs/version-7.x/admin/configuration/set-default-quota.md
new file mode 100644
index 000000000..a73a86027
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/set-default-quota.md
@@ -0,0 +1,77 @@
+---
+sidebar_position: 30
+id: default-user-quota
+title: Set default user quota
+description: How to set default user quota
+draft: false
+---
+
+# Set Default Quota per User Role
+
+You can define default storage quotas for specific user roles in OpenCloud by configuring the proxy service. This ensures that any newly created user with a given role automatically receives the specified quota.
+
+## Define Role-Based Quotas in `proxy.yaml`
+
+To configure quotas, edit the `opencloud.proxy.yaml` file and add the `role_quotas` section with role IDs and the desired quota in bytes:
+
+```bash
+nano opencloud-compose/config/opencloud/proxy.yaml
+```
+
+Example configuration:
+
+```yaml
+role_quotas:
+  'd7beeea8-8ff4-406b-8fb6-ab2dd81e6b11': 1073741824
+```
+
+This assigns a 1 GiB quota to all new users with the "User" role.
+
+## Role IDs
+
+Use the following role IDs to configure different quotas:
+
+- User:  
+  `d7beeea8-8ff4-406b-8fb6-ab2dd81e6b11`
+
+- SpaceAdmin:  
+  `2aadd357-682c-406b-8874-293091995fdd`
+
+- Admin:  
+  `71881883-1768-46bd-a24d-a356a2afdf7f`
+
+:::note
+Quota values are defined in bytes.
+:::
+
+## Mount the Configuration in Docker
+
+To apply the configuration, mount the updated `proxy.yaml` into your Docker container.
+
+1. Open the `docker-compose.yaml` file:
+
+```bash
+nano opencloud-compose/docker-compose.yaml
+```
+
+2. Add the following line under the `volumes` section for the proxy container:
+
+```yaml
+- ./config/opencloud/proxy.yaml:/etc/opencloud/proxy.yaml
+```
+
+## Apply the Changes
+
+Restart the OpenCloud container to apply the new configuration:
+
+```bash
+docker compose up -d
+```
+
+## Result
+
+All newly created users who receive a role defined in the `role_quotas` section will automatically have the specified quota assigned.
+
+:::info
+This configuration does **not** affect existing users. Only new users will receive the default quota.
+:::
diff --git a/versioned_docs/version-7.x/admin/configuration/storage/_category_.json b/versioned_docs/version-7.x/admin/configuration/storage/_category_.json
new file mode 100644
index 000000000..5475fd5c5
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/storage/_category_.json
@@ -0,0 +1,8 @@
+{
+  "label": "Storage",
+  "position": 20,
+  "link": {
+    "type": "doc",
+    "id": "storage"
+  }
+}
diff --git a/versioned_docs/version-7.x/admin/configuration/storage/cephfs.md b/versioned_docs/version-7.x/admin/configuration/storage/cephfs.md
new file mode 100644
index 000000000..097069e0c
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/storage/cephfs.md
@@ -0,0 +1,7 @@
+---
+sidebar_position: 2
+id: storage-cephfs
+title: 'CephsFS'
+description: CephsFS
+draft: true
+---
diff --git a/versioned_docs/version-7.x/admin/configuration/storage/decomposeds3.md b/versioned_docs/version-7.x/admin/configuration/storage/decomposeds3.md
new file mode 100644
index 000000000..cbe7e83e2
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/storage/decomposeds3.md
@@ -0,0 +1,90 @@
+---
+sidebar_position: 3
+id: storage-decomposeds3
+title: 'Decomposeds3'
+description: Decomposeds3 Storage Driver
+draft: false
+---
+
+# Decomposeds3 Storage Driver
+
+Decomposeds3 is a storage driver for OpenCloud that uses MinIO — an S3-compatible object storage — to store files efficiently. This setup combines the scalability of S3 with seamless integration into OpenCloud.
+
+:::warning
+
+This setup includes **No Migration Path** from existing storage solutions. If you are already using another storage backend, you will need to migrate your data manually.
+
+:::
+
+## Configure an S3 Bucket
+
+1. **Access your S3 Service**: Log in to your S3-compatible service (e.g., Hetzner S3, MinIO, AWS S3).
+2. **Create a Bucket**: Create a new bucket named `opencloud` (or any name you prefer).
+3. **Set Permissions**: Ensure the bucket has the necessary permissions for read and write operations
+4. **Note the Endpoint and Credentials**: Make a note of the endpoint URL, access key, and secret key for your S3 service.
+5. **CORS Configuration**: If your S3 service requires CORS configuration, ensure that it allows requests from your OpenCloud domain.
+6. **Region**: Note the region where your bucket is created, as it may be required for configuration.
+
+## Setup OpenCloud
+
+Navigate to the folder containing the Docker Compose configuration:
+
+```bash
+cd opencloud-compose
+```
+
+Open the `.env` file and fill the required configuration variables:
+
+```bash
+nano .env
+```
+
+Now we need all the information about the S3 bucket we created earlier. Modify the following lines in your `.env` file:
+
+:::tip
+
+The `DECOMPOSEDS3_*` variables used below are specific to [opencloud's docker-compose deployment method](https://github.com/opencloud-eu/opencloud-compose). If deploying outside of the recommended docker-compose configuration, the proper environment variables variables are `STORAGE_USERS_DECOMPOSEDS3_*`. See the [storage-users](../../../dev/server/services/storage-users) documentation for more details.
+
+:::
+
+```yaml
+# Configure the S3 storage endpoint. Defaults to "http://minio:9000" for testing purposes.
+DECOMPOSEDS3_ENDPOINT=https//your-s3-endpoint.example.com
+# S3 region. Defaults to "default".
+DECOMPOSEDS3_REGION=eu-central-1
+# S3 access key. Defaults to "opencloud"
+DECOMPOSEDS3_ACCESS_KEY=<your-access-key>
+# S3 secret. Defaults to "opencloud-secret-key"
+DECOMPOSEDS3_SECRET_KEY=<your-secret-key>
+# S3 bucket. Defaults to "opencloud"
+DECOMPOSEDS3_BUCKET=opencloud
+```
+
+Add `storage/decomposeds3.yml` to the `COMPOSE_FILE` variable
+or include it directly in the startup command:
+
+```bash
+docker compose -f docker-compose.yml -f storage/decomposeds3.yml up
+```
+
+Start all containers in the background:
+
+```bash
+docker compose up -d
+```
+
+## Login
+
+Open your browser and log in.
+
+After logging in, you should see the OpenCloud interface:
+
+<img src={require("./../img/login-page.png").default} alt="Login Page" width="1920"/>
+
+<img src={require("./../img/decomposeds3-with-minio.png").default} alt="OpenCloud with decomposeds3 and MinIO" width="1920"/>
+
+## Troubleshooting
+
+If you run into any issues or errors, check the following resource:
+
+- [Common Issues & Help](../../resources/common-issues)
diff --git a/versioned_docs/version-7.x/admin/configuration/storage/index.md b/versioned_docs/version-7.x/admin/configuration/storage/index.md
new file mode 100644
index 000000000..5e06f6faa
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/storage/index.md
@@ -0,0 +1,16 @@
+---
+sidebar_position: 0
+id: storage
+title: Storage
+description: Overview of OpenCloud storage configuration options
+draft: false
+---
+
+# Storage
+
+Use these guides to configure the storage backend for your OpenCloud deployment.
+
+## In this section
+
+- [PosixFS](./posixfs.md) - Use a regular filesystem as the OpenCloud storage backend
+- [DecomposedS3](./decomposeds3.md) - Use S3-compatible object storage with MinIO
diff --git a/versioned_docs/version-7.x/admin/configuration/storage/posixfs.md b/versioned_docs/version-7.x/admin/configuration/storage/posixfs.md
new file mode 100644
index 000000000..6651acef1
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/storage/posixfs.md
@@ -0,0 +1,118 @@
+---
+sidebar_position: 1
+id: storage-posix
+title: 'PosixFS'
+description: PosixFX Storage Driver
+draft: false
+---
+
+# PosixFS Storage Driver
+
+PosixFS is a storage driver that saves OpenClouds files and folders in a folder structure how the user sees that in the web interface or other clients. That is a difference to the previously used driver DecomposedFS, which stores files in a technical folder structure that has limited meaning for admins.
+
+PosixFS Driver supports two different modes:
+
+- The _non collaborative mode_ where the filesystem tree in use is exclusively granted to OpenCloud
+- The _collaborative mode_ where modifications of the underlying file tree are permitted by other processes than OpenCloud
+
+## General Notes
+
+The following general notes apply to both modes of the driver.
+
+### Metadata
+
+To enable OpenCloud to operate without a database, additional metadata is stored using the extended file attributes of each file. If the total size of this metadata exceeds the limitations imposed by the underlying file system, it is automatically moved to a separate metadata file. In such cases, only a reference to this metadata file remains in the extended attributes. This entire process is handled transparently by OpenCloud.
+
+### Access Model
+
+To ensure reliable operation in _non-collaborative mode_, the underlying file system used by the PosixFS driver must not be modified while OpenCloud is running. The assigned file system tree must be exclusively reserved for access by OpenCloud.
+All files and directories must be owned by the same user and group under which the OpenCloud process is running. File and directory permissions must allow OpenCloud to read, write, and traverse the entire tree.
+
+These conditions are automatically fulfilled as long as the root directory of the assigned tree is writable.
+
+#### Assimilation
+
+When OpenCloud starts up, it scans the assigned file system tree for newly added or modified files and directories. During this process, metadata is updated and internal caches are built accordingly. This is referred to as the _assimilation_ of new resources.
+
+It is important to note that assimilation does not trigger post-upload checks, such as virus scanning. Since the files are already in their final location within the file system, such checks would be ineffective at this stage and are therefore skipped.
+
+However, indexing for the search service does take place for assimilated resources.
+
+### Startup
+
+When OpenCloud with PosixFS starts up, it is running over the entire file system to warm up the caches. This might take some time.
+
+### Backup
+
+With PosixFS backup and restore is easy. The entire OpenCloud filesystem tree can be snapshotted regularly and restored as needed. It depends on the filesystem type how that has to be done in detail.
+
+### Migration
+
+PosixFS in this so called _non collaborative mode_ is the default for new installations of OpenCloud. There is currently no way to migrate OpenCloud installations with DecomposedFS backend to PosixFS.
+
+If that is needed, data needs to be copied into a new installation of OpenCloud.
+
+## PosixFS Non Collaborative Mode
+
+This describes special aspects of the non collaborative mode.
+
+### External Access
+
+When OpenCloud is shut down, limited manipulation of the underlying file system tree is possible for certain administration tasks such as
+
+- adding files and folders
+- removing files and folders
+- renaming files and folders
+
+:::warning
+
+Whenever files are manipulated externally to OpenCloud, it is important to remember to
+
+- shut down OpenCloud before starting
+- do not lose the extended file attributes of individual files
+- set the file- and folder permissions correctly
+
+:::
+
+### Configuration
+
+The PosixFS storage driver is part of the default OpenCloud bundle.
+
+Involved configuration settings (environment variables) to enable PosixFS are:
+
+- `STORAGE_USERS_DRIVER` defaults to `posix` from version `2.0.0`, in older versions it needs to be explicitly set
+- `STORAGE_USERS_ID_CACHE_STORE` needs to be set to `nats-js-kv`
+- `STORAGE_USERS_POSIX_ROOT` can be omitted for default, or set the storage root directory
+
+## PosixFS Collaborative Mode
+
+This section describes the collaborative mode of the PosixFS driver, which allows the file system to be modified while OpenCloud is running. Changes made in this mode are reflected in real time in OpenCloud clients.
+
+### Usage
+
+Collaborative mode should always be used with caution. It is intended only for well-defined use cases that are carefully planned, configured, and tested. Operation must take place in a controlled environment.
+
+Compared to non-collaborative mode, collaborative mode requires significantly more system resources to monitor the file system. Server hardware must be appropriately sized to handle this increased load.
+
+### External Access
+
+External access to files is permitted under specific conditions. File changes are detected and assimilated in real time.
+
+The following guidelines are critical for smooth and reliable operation:
+
+- Creating new files and folders is the preferred method of external modification.
+- Do not use symbolic links.
+- Moving files across OpenCloud spaces is not supported and will not be detected as such.
+- Editing or deleting large numbers of files may cause errors in tree size calculation.
+- Continuously monitor server system resources to identify potential bottlenecks.
+- Carefully configure components such as Apache Tika to optimize indexing performance.
+
+It is essential to maintain correct file ownership and permissions when modifying the file system externally. Files must be created with the correct user and permissions from the outset. Retroactive changes are discouraged, as assimilation may already be in progress.
+
+### Configuration
+
+In addition to the configuration required for non-collaborative mode, the following setting must be enabled for local file systems such as XFS, ext4, and others:
+
+```env
+STORAGE_USERS_POSIX_WATCH_FS=true
+```
diff --git a/versioned_docs/version-7.x/admin/configuration/web-applications.md b/versioned_docs/version-7.x/admin/configuration/web-applications.md
new file mode 100644
index 000000000..d3d6783e4
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/configuration/web-applications.md
@@ -0,0 +1,66 @@
+---
+sidebar_position: 60
+id: web-applications
+title: Web Apps
+description: How to enable web applications in OpenCloud
+draft: false
+---
+
+# Web Applications
+
+Administrators have the ability to provide additional web applications to their users. This feature is especially useful for organizations that want to integrate third-party tools or provide internally developed apps within the OpenCloud environment.
+
+## Installing a Web Application
+
+You can install a web application in just a few steps:
+
+### Open the App Store
+
+Use the Application Switcher in the top navigation bar of OpenCloud and navigate to the App Store.
+
+<img src={require("./img/app-store.png").default} alt="App Store" width="1920"/>
+
+### Download the Application
+
+Find and download the application you want to install.
+
+### Extract and copy
+
+Unzip the downloaded archive and copy the extracted folder into the web application directory.  
+By default, this path is:
+
+```bash
+opencloud-compose/config/opencloud/apps
+```
+
+:::note
+If you are adding an app to an already running system, verify whether the `/web/assets/apps` directory exists inside your `$OC_DATA_DIR`.
+If it does not exist, create it manually.
+:::
+
+### Restart OpenCloud
+
+Restart the OpenCloud stack using the following command:
+
+```bash
+docker compose restart
+```
+
+### Access in OpenCloud
+
+Once the app is copied to the correct location, it will automatically appear in the OpenCloud interface.
+
+## Configure a Web Application
+
+Some OpenCloud apps require additional configuration — for example, the External Sites app.
+
+This particular app can be configured by creating the file config.json in the web apps directory:
+
+```bash
+/web/assets/apps/external-sites/config.json
+```
+
+:::note
+Configuration details vary between apps.
+For specific setup instructions, please refer to the [official documentation](https://github.com/opencloud-eu/web-extensions/tree/main) of the respective app.
+:::
diff --git a/versioned_docs/version-7.x/admin/datasheet.md b/versioned_docs/version-7.x/admin/datasheet.md
new file mode 100644
index 000000000..192fbfeb1
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/datasheet.md
@@ -0,0 +1,72 @@
+---
+sidebar_position: 3
+id: datasheet
+title: Datasheet
+description: Datasheet
+draft: false
+---
+
+## Deployment Options
+
+| Category                              | Details                                                                                                                                                                                                                                                                                                                                |
+| :------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Types                                 | <ul><li>On-Premises</li><li>Managed Service: Available through partners</li><li>SaaS: Available through partners</li></ul>                                                                                                                                                                                                             |
+| Container (recommended)               | <ul><li>Docker Compose or Podman</li><li>Kubernetes Helm Charts (available with a [enterprise subscription](https://opencloud.eu/en/product/service-and-support) ) </li></ul>                                                                                                                                                          |
+| Bare-Metal (not officially supported) | <ul><li>OpenCloud can run as a single binary. However, integrating additional services like Collabora, Apache Tika for search, or antivirus is not documented. Bare-metal deployments are not officially supported by OpenCloud. They are great for quick evaluation but are undocumented and have a minimalist feature set.</li></ul> |
+
+## Backup
+
+| Category        | Details                                                                                                                                      |
+| :-------------- | :------------------------------------------------------------------------------------------------------------------------------------------- |
+| Backup strategy | <ul><li>Snapshots: Backups can be easily done solely through storage snapshots, eliminating the need for complex database backups.</li></ul> |
+
+## Security
+
+| Category             | Details                                                                                                                                 |
+| :------------------- | :-------------------------------------------------------------------------------------------------------------------------------------- |
+| Encryption           | <ul><li>Transport Encryption: TLS</li><li>Server-Side Encryption: S3 SSE</li></ul>                                                      |
+| Access management    | <ul><li>RBAC (Role-Based Access Control)</li><li>2FA / MFA</li><li>SSO (LDAP, SAML, OAuth)</li></ul>                                    |
+| Auditing & Logging   | <ul><li>Detailed logs, audit trails, monitoring APIs</li></ul>                                                                          |
+| File Firewall        | <ul><li>Prevent upload of restricted filetypes based on a allow- or denylist.</li></ul>                                                 |
+| Antivirus            | <ul><li>ClamAV (default)</li><li>ICAP: Integrate 3rd party anti-virus scanner via Internet Content Adaptation Protocol (ICAP)</li></ul> |
+| Data Loss Prevention | <ul><li>Collabora Secure View</li></ul>                                                                                                 |
+
+## Identity Management
+
+| Category   | Details                                                                                                                                                                                                                      |
+| :--------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Integrated | <ul><li>Integrated user and group management (LibreIDM) for up to 500 users. Designed for standalone or small-sized deployments that do not rely on third-party identity services, usually for friends and family.</li></ul> |
+| External   | <ul><li>OpenID Connect (OIDC): Integration of external identity providers via Keycloak.</li><li>Integration of Azure AD, EntraID, ADFS</li></ul>                                                                             |
+
+## Compliance
+
+| Regulation                            | Details                                                                                                                                                                                                 |
+| :------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| EU-GDPR                               | <ul><li>Compliant</li></ul>                                                                                                                                                                             |
+| WCAG 2.1 / BITV 2.0 Web Accessibility | <ul><li>Compliant. To prevent accessibility regressions, we treat any accessibility violation as a bug and continuously fix these issues as part of our daily software development lifecycle.</li></ul> |
+
+## High Availability
+
+| Category              | Details                                                                                                                                                                                                          |
+| :-------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Redundancy & Failover | <ul><li>Supported in clustered environments to ensure high availability and system reliability.</li><li>Automatic failover mechanisms help minimize downtime in case of hardware or software failures.</li></ul> |
+
+## Integrations
+
+| Category                | Details                                                                                                                                                             |
+| :---------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Plugins & Extensibility | <ul><li>Web: Extension system for adding custom functionality.</li><li>Server: Microservices architecture for modular and scalable server-side extensions</li></ul> |
+
+## APIs
+
+| API      | Description                                                                                                                                                                      |
+| :------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| WebDAV   | <ul><li>Standard file API for remote file transfer over HTTP/HTTPS using TUS for resumable, interruption-tolerant transfers.</li></ul>                                           |
+| GraphAPI | <ul><li>Microsoft Graph API for managing cloud storage and collaboration spaces.</li></ul>                                                                                       |
+| gRPC     | <ul><li>High-performance RPC framework for microservice communication.</li></ul>                                                                                                 |
+| OCS      | <ul><li>API for programmatic file/folder sharing and management.</li></ul>                                                                                                       |
+| OCM      | <ul><li>Open Cloud Mesh API for federated file and folder sharing between different file cloud platforms like Cernbox, ownCloud, Nextcloud or Seafile .</li></ul>                |
+| SSE      | <ul><li>Server-sent event stream for real-time client notifications.</li></ul>                                                                                                   |
+| WOPI     | <ul><li>Microsoft API for integrating Office apps with third-party storage, e.g., Collabora.</li></ul>                                                                           |
+| KQL      | <ul><li>Keyword Query Language (KQL) is a search language to perform advanced searches by filtering and querying structured data, metadata, and documents efficiently.</li></ul> |
+| ICAP     | <ul><li>Network protocol for offloading content scanning (e.g., antivirus).</li></ul>                                                                                            |
diff --git a/versioned_docs/version-7.x/admin/features.md b/versioned_docs/version-7.x/admin/features.md
new file mode 100644
index 000000000..1872ea1e6
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/features.md
@@ -0,0 +1,435 @@
+---
+sidebar_position: 2
+id: features
+title: Features
+description: Features
+draft: false
+---
+
+## Key Features at a Glance
+
+- Seamless File Synchronization: Access your files across all devices.
+- Secure & Flexible File Sharing: Share files with granular roles, expiration dates, and password protection.
+- Spaces - Collaborative Team Folders: Ensure continuity even if team members leave.
+- Real-Time Collaboration: Work on documents simultaneously with Collabora Web Office.
+- Advanced Search & Organization: Use full-text search, tags, and filters for quick access.
+- Unlimited Storage & Uploads: No file size restrictions.
+- Privacy-First Design: Zero-Knowledge principle ensures admins can't access user content.
+- Cross-Client Availability: Works on Windows, Mac, Linux, Android, iOS, and Web.
+
+## File Management
+
+**Functions for storage, access and organization of files.**
+
+Full control over storage and access. Seamless operation across all devices.
+
+### Access from Anywhere
+
+Files and folders can be opened, synchronized, and shared from any location and device—via browser, desktop client (Windows, macOS, Linux), or mobile apps (iOS, Android).
+
+### Synchronization Across Devices
+
+Changes are synchronized automatically across all connected devices, in real time via the respective OpenCloud client.
+
+### Offline Access
+
+Users can mark files or folders for offline use to open and edit them without an internet connection. Changes are automatically synced once connectivity is restored.
+
+### Files On-Demand
+
+Files can be viewed directly in the device’s File Explorer and are stored efficiently, as they are only downloaded when needed. Large folder structures are immediately accessible without full synchronization, reducing network load and sync overhead. Available on Windows desktop operating systems and mobile clients.
+
+### Advanced Search
+
+Files can be found quickly—by title or full text. The search provides live suggestions and supports filtering by file type, modification date, tag, or storage location.
+
+### Favorites
+
+Mark frequently used files and folders for quick access. Favorites are stored server-side, collected on a dedicated Favorites page, and visible in file lists and search results.
+
+### Versioning and Recovery
+
+Every change is automatically saved as a version and can be restored at any time. Administrators can define how many versions to keep and the rules for deleting older versions.
+
+### No Limit on File Size, Count, or Type
+
+OpenCloud supports storing any number of files in any format and size.
+
+### Folders and Tags
+
+Files can be organized in hierarchical folder structures or with tags. Tags serve as a cross-project taxonomy, while folders typically represent team or project structures.
+
+### Open Files with Native Applications
+
+Files in OpenCloud can be opened directly with local programs, edited, and saved back—without manual exporting or importing. Files remain in their original OpenCloud location and keep their permissions, version history, etc.
+
+### Resuming Interrupted Uploads
+
+Uploads interrupted by connection issues are automatically resumed. Transfers use the TUS protocol (Resumable Uploads), ensuring even very large files can be uploaded without data loss.
+
+### Automatic Upload
+
+New or changed files are automatically uploaded as soon as a connection is available. Users and administrators can define which folders sync automatically, exclude certain file types, and configure parallel uploads. Transfers run in the background and adapt to connection quality and system resources.
+
+### Integration as a Network Drive
+
+OpenCloud can be integrated as a network drive in standard operating systems and behaves like a local drive. This uses WebDAV or the native desktop client.
+
+### Document Scanning via Camera
+
+Using the mobile app, documents can be captured with the camera, automatically cropped, and saved as PDFs in OpenCloud.
+
+### Unlimited Storage Space
+
+There are no system-side limits on the number or size of stored files. Available capacity depends on the deployed server or storage infrastructure.
+
+### Integrated Preview
+
+Documents, images, videos, and audio files can be viewed directly in the browser, desktop client, and mobile apps. Common formats are supported. On mobile devices, previews use native viewers or Collabora integration.
+
+### Personal Storage
+
+Each user has a private storage area visible only to them by default. Files can be organized, shared, or moved to Spaces from here—ensuring clear separation between personal and shared work areas.
+
+### Customizable Storage Limits (Quotas)
+
+Administrators can assign storage limits per user or Space to allocate storage efficiently.
+
+## Usability & User Experience
+
+**Simple and blazing fast to use for all user groups.**
+
+Intuitive usage without training. Accessibility for all users. Consistent, brand-compliant user experience.
+
+### Fast User Interface
+
+The application remains responsive even in folders with many files and avoids unnecessary page reloads. Asynchronous updates keep lists and detail views usable without interruptions.
+
+### Drag & Drop, Multi-Selection, Copy/Paste
+
+Files can be moved via drag & drop, multiple files can be selected at once, and actions like copy/paste can be performed using keyboard shortcuts—just like in a desktop file manager. Everyday file operations thus become faster and feel familiar.
+
+### Accessible User Interface
+
+The OpenCloud web interface is optimized according to the European Accessibility Act (EAA) and WCAG 2.1/BITV 2.0 guidelines for users with visual, motor, or cognitive impairments. It provides clear keyboard navigation, understandable labels, sufficient color contrast, and full screen-reader and focus support—helping organizations meet legal and procurement requirements.
+
+### Email Notifications
+
+Users receive email notifications about events such as new shares or membership changes in a Space.
+
+### Customizable View Modes
+
+Files can be displayed in list, tile, or compact views. Columns, visible elements, and items per page can be configured to keep large directories tidy.
+
+### Color Scheme Selection
+
+Users can switch between light and dark modes to improve readability under different lighting conditions and reduce eye strain.
+
+### Responsive Design
+
+The interface adjusts automatically to screen sizes from smartphones to 8K monitors. Navigation and file views remain fully usable without separate desktop or mobile apps.
+
+### Consistent Look & Feel
+
+Web, desktop, and mobile apps follow a unified interaction concept. Consistent navigation patterns and icons reduce onboarding time and user errors.
+
+### Individual Branding
+
+Administrators can create or customize design themes, including color palettes, logos, backgrounds, and UI elements. A fully accessible theme can be automatically generated from a single corporate color or defined manually. This allows OpenCloud to seamlessly match an organization’s corporate design.
+
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+## Collaboration & Productivity
+
+**Collaborative work in real time and structured team organization:** Real-time collaboration without additional software. Structured workflows and a unified work environment.
+
+### Workspaces for Teams and Projects (“Spaces”)
+
+Spaces are independent work areas that go beyond simple folders. They bundle files, permissions, and responsibilities for projects or departments and can be managed separately—with dedicated owners, rules, and storage limits. This creates a clear separation between personal storage, team/project files, and organization-wide content.
+
+### Delegated Space Administration
+
+Project or team leads can manage individual Spaces without requiring global admin rights. Member and permission management can thus be decentralized.
+
+### Internal Sharing
+
+Files and folders can be shared with users or groups within the organization. Access rights such as read, edit, or upload can be precisely controlled to ensure secure collaboration.
+
+### External Sharing
+
+Content can be shared securely with customers, service providers, suppliers, or authorities via password-protected links or guest accounts (soon).
+
+### Federation – Sharing Across Sites or Organizations
+
+Enables secure collaboration between multiple OpenCloud instances, e.g., across branches or subsidiaries. Files are shared directly across servers without creating duplicates. Authentication and access rights are centrally managed.
+
+### Web Office
+
+Through Collabora Online integration, office documents can be opened and collaboratively edited directly within the web interface—without local installation. Users can comment, co-edit in real time, and rely on full compatibility with Microsoft Office and OpenDocument formats.
+
+### Real-Time Editing
+
+Multiple users can work on the same files simultaneously. Changes sync immediately, and automatic locking mechanisms prevent version conflicts—ensuring smooth co-editing.
+
+### Calendar and Contacts
+
+Integration with CalDAV and CardDAV enables teams to manage shared calendars and contact lists directly in OpenCloud. Appointments and deadlines can be linked to files, and shared contacts can be centrally maintained. Compatible with Apple Calendar, Outlook, Thunderbird, Evolution, and others. Note that this feature is not Supported in the enterprise licence.
+
+## Compliance & Data Protection
+
+**Protects data and fulfills all legal requirements.**
+
+Maximum data security and transparent processing. Trusted for regulated industries.
+
+### Zero-Knowledge Principle
+
+Administrators can manage Spaces (e.g., cleanup, quota changes) but cannot access its content. This ensures full confidentiality: even admins cannot view user data.
+
+### Compliance with Data Protection and Security Policies
+
+OpenCloud meets key international standards such as GDPR, ISO 27001, CCPA, HIPAA, FERPA, SOC 2, and CRA through features like encryption, audit logs, and access controls. Actual certifiability depends on the operational model: self-hosted deployments fall under the operator’s responsibility, while the enterprise Licence follows auditable, policy-compliant processes. OpenCloud integrates with existing compliance or GRC systems and provides exportable audit data.
+
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+### §20 GDPR Personal Data Export
+
+Includes features that support GDPR compliance (e.g., personal data export according to §20 GDPR.).
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+### S3 Server-Side Encryption
+
+Files can be encrypted automatically on S3 storage. The key resides on the server and protects against physical access or unauthorized access to drives or backups. Combined with TLS in transit, this provides consistent security but does not prevent admin-level access inside the application (unlike end-to-end encryption).
+
+### Metadata Encryption
+
+Sensitive metadata such as file names or tags can also be stored encrypted, preventing third parties from inferring content based on file structure or names.
+
+### Ransomware Protection
+
+Files encrypted by an infected user can be restored to their pre-attack state, keeping data safe and available.
+
+### Audit Logs and Change Tracking
+
+All security-relevant actions—uploads, shares, deletions, login attempts—are logged. File and metadata changes can be traced down to user level for full transparency.
+
+### Virus Protection
+
+Incoming and synchronized files are scanned automatically for malware. OpenCloud uses ICAP interfaces (e.g., for ClamAV, Sophos, Kaspersky) and integrates with existing security gateways.
+
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+### File Firewall
+
+Prevents unsafe file uploads by blocking defined file types (e.g., executables, macros). Admins centrally manage allow/deny lists and apply them to users and Spaces.
+
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+### Protected Preview with Watermarks
+
+Documents can be displayed with dynamic watermarks to deter screenshots or unauthorized sharing. Watermarks may include username, timestamp, or organization ID for traceability. Based on “Secure View” using Collabora or OnlyOffice.
+
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+## Identity and Access Management (IAM)
+
+**Central, secure management of users, roles, and permissions.**
+
+Centralized user and group management. Secure access across organizational boundaries. Integration with existing identity systems.
+
+### Password Policies and Generator
+
+Enforces strong passwords with rules for complexity and expiration. A “Banned Password List” blocks weak patterns (e.g., “Password123”). An integrated generator creates compliant passwords.
+
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+### Two-Factor Authentication (2FA/MFA)
+
+Adds a second authentication factor beyond the password. Enforced via the connected identity provider (e.g., Keycloak). Supports TOTP, push notifications, and FIDO2/U2F tokens.
+
+### Role-Based Access Control (RBAC)
+
+User rights are assigned centrally via roles reflecting the organizational structure. RBAC simplifies management in complex environments and enables fine-grained control (e.g., link creation rules, password enforcement, preset expiration dates).
+
+### Biometric Unlock (Touch & Face ID)
+
+The mobile app can be unlocked using fingerprint or facial recognition, improving security.
+
+### Multiple Accounts per Client
+
+Users can use multiple accounts in parallel on desktop and mobile clients, making it easy to switch between work, tenant, and private contexts.
+
+### LDAP
+
+OpenCloud supports LDAP systems such as OpenLDAP, FreeIPA, or Univention Directory via secure bindings with filter support.
+
+### Active Directory
+
+The enterprise Licence supports integration with Microsoft Active Directory and Azure Entra ID, including optional managed connectivity for paying customers.
+
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+### Single Sign-On (SSO)
+
+Users log in with their central company account. Supported protocols include OpenID Connect, LDAP, SAML 2.0, and OAuth 2.0.
+
+### External Identity Providers (IdP)
+
+OpenCloud integrates with leading IdPs such as Keycloak, Azure AD, EntraID, or ADFS—ideal for environments with existing directory infrastructures.
+
+### Share Links
+
+Content can be shared externally via link, optionally protected with a password and expiration date. Links are quick and simple but offer limited traceability compared to guest accounts.
+
+### Guest Accounts (soon)
+
+External users receive personal, password-protected accounts. Their access is fully attributable and auditable, with policies for expiration, 2FA/MFA, and individual revocation—ideal for compliance-sensitive use cases.
+
+### Session Management
+
+Administrators can monitor, terminate, or limit user sessions to prevent unauthorized access, especially on shared or remote devices.
+
+## Operation & Deployment
+
+**Reliable, scalable, and professional operation.**
+
+High stability, minimal downtime, secure deployment, and scalable architecture.
+
+### Snapshots and Backups
+
+Automated snapshots enable restoring whole instances or individual user areas. Backups can be scheduled and stored locally or externally. Because metadata is stored directly with the files, elements such as versions and tags remain intact during restores or migrations—without dependency on database states.
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+### Security Advisories
+
+Enterprise Licence customers receive early security notifications about new vulnerabilities, including risk assessments and scheduled patch plans.
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+### Kubernetes Deployment
+
+OpenCloud can be deployed as containerized microservices in Kubernetes clusters using Helm charts for installation, scaling, and upgrades. Automated orchestration enables load balancing, self-healing, zero-downtime deployments, and dynamic scaling.
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+### Scalable Enterprise Storage Systems
+
+Integrates storage systems like CephFS, GPFS (IBM Spectrum Scale), or S3-compatible backends to support petabyte-scale volumes with high performance and redundancy.
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+### Performance and Load Optimization
+
+Optimized for scalability and speed through parallel transfers and distributed I/O. Monitoring with Prometheus and Grafana enables continuous analysis and scaling.
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+### Multi-Tenancy
+
+Multiple organizational units can be hosted on the same instance—ideal for corporations, public authorities, or service providers.
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+### Metadata Stored in Files
+
+All metadata, including tags and version information, is stored securely within the system and remains consistent across storage environments.
+
+### High Availability and Failover
+
+Redundant nodes can take over operations automatically in case of component failure, preventing downtime.
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+### Long-Term Support (LTS)
+
+Enterprise customers receive long-term supported versions with security updates and bug fixes—suitable for critical and compliance-sensitive environments.
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+### Installation and Security Check
+
+Before deployment or upgrades, OpenCloud runs configuration and security checks and provides an assessment with recommendations.
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+### Mass Rollouts
+
+Clients can be preconfigured with a server address for simplified mass deployment, reducing helpdesk requests.
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+### Guaranteed Upgrade Support
+
+Supports smooth upgrades across major and minor versions with migration paths for data and accounts. The enterprise Licence provides validated scripts, compatibility checks, and rollback options.
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+### Service Level Agreements (SLA)
+
+The Enterprise Licence includes SLAs with defined response and resolution times, priority support, escalation management, and security notifications—ensuring professional operation.
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+### On-Demand Support
+
+During planned changes or upgrades, an OpenCloud engineer is available live for immediate troubleshooting and guidance.
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+### Air-Gapped Operation
+
+OpenCloud can run in isolated networks without internet access. Installation, updates, and extensions occur via internal repositories or offline media. External integrations (e.g., Web Office) can also be hosted on-premises to keep all data within the isolated environment.
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+## Integrations & Interfaces
+
+**Open APIs and extensions for seamless integration and automation.**
+
+Third-party extensibility and custom development. Open architecture for automation and data exchange.
+
+### Plugin Architecture
+
+OpenCloud’s functionality can be extended or customized. The documented developer interface offers hooks, events, and a modular framework for server-side extensions.
+
+### Client SDKs
+
+SDKs for Desktop, Mobile, and Web encapsulate OpenCloud’s server interfaces, allowing developers to build client-side applications or integrations without implementing API calls manually. Supported languages include Objective-C, TypeScript, PHP, Go, and C++.
+
+### Headless and Microservices Architecture
+
+OpenCloud uses a modern headless architecture that separates UI from backend services. Individual services can be operated, scaled, or developed independently.
+
+### File and Collaboration APIs
+
+OpenCloud supports WebDAV for file access and sync, WOPI for office integration, OCS for user and app communication, and OCM for federated sharing across compatible systems.
+
+### Native REST API
+
+Provides automation-friendly access to nearly all OpenCloud features—user and rights management, file operations, integration into external systems, and more.
+
+### Federation API
+
+Allows connecting multiple OpenCloud or compatible platforms (e.g., Nextcloud, ownCloud).
+
+### GraphAPI
+
+Used for communication between clients and the server, inspired by Microsoft Graph.
+
+### Security, Compliance, and Monitoring APIs
+
+The Enterprise Licence includes extended APIs for security checks, compliance monitoring, and real-time reporting. ICAP enables external antivirus/DLP integration, KQL supports compliance data analysis, and SSE provides live notifications and monitoring.
+:::info supported within the [enterprise licence](https://opencloud.eu/en/product/service-and-support)
+:::
+
+### Custom File Types
+
+Admins and developers can define custom file types and metadata structures to adapt OpenCloud to industry-specific needs (e.g., medical, legal, industrial). Managed via the plugin system and REST APIs.
diff --git a/versioned_docs/version-7.x/admin/getting-started/_category_.json b/versioned_docs/version-7.x/admin/getting-started/_category_.json
new file mode 100644
index 000000000..4bd4025bc
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/getting-started/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Getting Started",
+  "position": 4
+}
diff --git a/versioned_docs/version-7.x/admin/getting-started/container/_category_.json b/versioned_docs/version-7.x/admin/getting-started/container/_category_.json
new file mode 100644
index 000000000..df36e478c
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/getting-started/container/_category_.json
@@ -0,0 +1,8 @@
+{
+  "label": "Container",
+  "position": 2,
+  "link": {
+    "type": "doc",
+    "id": "admin-getting-started-container"
+  }
+}
diff --git a/versioned_docs/version-7.x/admin/getting-started/container/docker-compose/_category_.json b/versioned_docs/version-7.x/admin/getting-started/container/docker-compose/_category_.json
new file mode 100644
index 000000000..1f12f757c
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/getting-started/container/docker-compose/_category_.json
@@ -0,0 +1,9 @@
+{
+  "label": "Docker Compose",
+  "position": 1,
+  "description": "Deploy OpenCloud using Docker Compose with Traefik or an external reverse proxy",
+  "link": {
+    "type": "doc",
+    "id": "docker-compose-overview"
+  }
+}
diff --git a/versioned_docs/version-7.x/admin/getting-started/container/docker-compose/docker-compose-base.md b/versioned_docs/version-7.x/admin/getting-started/container/docker-compose/docker-compose-base.md
new file mode 100644
index 000000000..027b3c115
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/getting-started/container/docker-compose/docker-compose-base.md
@@ -0,0 +1,288 @@
+---
+sidebar_position: 1
+id: docker-compose-base
+title: Default Setup with Traefik
+description: Full-blown featureset including web office.
+draft: false
+---
+
+# OpenCloud with Docker Compose + Integrated Traefik
+
+Install an internet-facing OpenCloud instance with automatic SSL certificates using Docker Compose's integrated Traefik reverse proxy.
+
+This is the recommended deployment path for most new OpenCloud installations. Traefik automatically manages Let's Encrypt SSL certificates, eliminating the need to manage a separate reverse proxy.
+
+This installation guide is written for Ubuntu and Debian systems. The software can also be installed on other Linux distributions, but commands and package managers may differ.
+
+:::note Not using Traefik?
+If you already have an external reverse proxy (Nginx, HAProxy, etc.) or prefer to manage it separately, see [Deploy Behind External Proxy](./docker-external-proxy.md) instead.
+:::
+
+## Prerequisites
+
+- Four domains pointing to your server:
+  - `cloud.YOUR.DOMAIN` → OpenCloud frontend
+  - `collabora.YOUR.DOMAIN` → Collabora Online Server
+  - `wopiserver.YOUR.DOMAIN` → WOPI server for document editing
+  - `traefik.YOUR.DOMAIN` → Traefik dashboard
+
+  Alternatively, you can use a wildcard domain (`*.YOUR.DOMAIN`)
+
+- A hosted server (e.g., Hetzner, AWS, or your own VPS) with Linux and SSH access
+
+## Connect to Your Server
+
+Log into your server via SSH:
+
+```bash
+ssh root@YOUR.SERVER.IP
+```
+
+## Install Docker
+
+Update your system and install Docker.
+
+First, perform an update and upgrade:
+
+```bash
+apt update && apt upgrade -y
+```
+
+Install Docker following the [official Docker guide](https://docs.docker.com/engine/install/ubuntu/#install-using-the-repository)
+
+Once Docker is installed, enable and start the service:
+
+```bash
+systemctl enable docker && systemctl start docker
+```
+
+## Clone the OpenCloud Repository
+
+Download the necessary configuration files:
+
+```bash
+git clone https://github.com/opencloud-eu/opencloud-compose.git
+```
+
+## Configure the .env File for Staging Certificates
+
+Before requesting real SSL certificates, it is recommended to test the setup using Let's Encrypt's staging environment.
+
+### Navigate to the OpenCloud configuration folder
+
+```bash
+cd opencloud-compose
+```
+
+### Create environment file
+
+```bash
+cp .env.example .env
+```
+
+:::note
+The repository includes .env.example as a template with default settings and documentation. Your actual .env file is excluded from version control (via .gitignore) to prevent accidentally committing sensitive information like passwords and domain-specific settings.
+:::
+
+## Modify these settings
+
+### Edit the `.env` file with the editor of your choice
+
+In our example we use nano
+
+```bash
+nano .env
+```
+
+### Disable insecure mode
+
+```bash
+# INSECURE=true
+```
+
+### Set your domain names
+
+```bash
+TRAEFIK_DOMAIN=traefik.YOUR.DOMAIN
+OC_DOMAIN=cloud.YOUR.DOMAIN
+COLLABORA_DOMAIN=collabora.YOUR.DOMAIN
+WOPISERVER_DOMAIN=wopiserver.YOUR.DOMAIN
+```
+
+### Set your admin password
+
+```bash
+INITIAL_ADMIN_PASSWORD=YourSecurePassword
+```
+
+### Set your email for SSL certification
+
+```bash
+TRAEFIK_ACME_MAIL=your@email.com
+```
+
+### Use Let's Encrypt staging certificates (for testing)
+
+```bash
+TRAEFIK_ACME_CASERVER=https://acme-staging-v02.api.letsencrypt.org/directory
+```
+
+### Set the deployment option
+
+Set the `COMPOSE_FILE` variable based on the components you want to deploy.
+
+For an OpenCloud deployment without Collabora, use:
+
+```bash
+COMPOSE_FILE=docker-compose.yml:traefik/opencloud.yml
+```
+
+To deploy OpenCloud with Collabora, use:
+
+```bash
+COMPOSE_FILE=docker-compose.yml:weboffice/collabora.yml:traefik/opencloud.yml:traefik/collabora.yml:radicale/radicale.yml
+```
+
+Save the file and exit the editor.
+
+## Start OpenCloud
+
+Launch OpenCloud using Docker Compose:
+
+```bash
+docker compose up -d
+```
+
+This will start all required services in the background.
+
+## Verify TLS Certificates
+
+After starting OpenCloud, verify that SSL certificates were issued correctly and switch from staging to production certificates when ready.
+
+### Verify Staging Certificates
+
+By default, the setup uses Let's Encrypt staging certificates for testing. These are not trusted by browsers but prove that the DNS and certificate generation workflow is correct.
+
+Open the following URL:
+
+```bash
+https://cloud.YOUR.DOMAIN
+```
+
+Because the setup currently uses Let's Encrypt staging certificates, your browser will show a security warning. This is expected and normal for the staging environment.
+
+The same warning may appear for the other configured domains.
+
+### Example in Chrome
+
+Click on the lock icon to view certificate details:
+
+<img src={require("./../../img/docker-compose/certificate-details.png").default} alt="Certificate Details" width="500"/>
+
+Expand the certificate information to confirm it was issued by "Let's Encrypt Staging":
+
+<img src={require("./../../img/docker-compose/certificate-viewer.png").default} alt="Certificate Details" width="500"/>
+
+<img src={require("./../../img/docker-compose/subordinate-ca's.png").default} alt="Certificate Details Subordinate CA" width="500"/>
+
+:::success Staging Certificate Success
+If you see "Let's Encrypt Staging" as the issuer, the certificate generation is working correctly. You can now safely switch to production certificates.
+:::
+
+## Switch to Production Certificates
+
+Once the staging certificate works correctly, you can switch to production SSL certificates from Let's Encrypt.
+
+### Stop Docker Compose
+
+```bash
+docker compose down
+```
+
+### Remove old staging certificates
+
+Delete the previously generated staging certificates:
+
+```bash
+rm -r certs
+```
+
+:::warning
+If you changed volume names or paths in your `.env` file, adjust this command to match your certificate directory.
+:::
+
+### Disable staging mode in `.env`
+
+Open the environment file:
+
+```bash
+nano .env
+```
+
+Comment out or remove the staging server line:
+
+```bash
+# TRAEFIK_ACME_CASERVER=https://acme-staging-v02.api.letsencrypt.org/directory
+```
+
+Save the file.
+
+### Restart OpenCloud with production certificates
+
+Start the containers again:
+
+```bash
+docker compose up -d
+```
+
+Traefik will now request trusted production certificates from Let's Encrypt.
+
+### Wait for certificate generation
+
+Certificate generation may take a few moments. Check the logs:
+
+```bash
+docker compose logs traefik
+```
+
+Look for messages indicating successful certificate generation.
+
+### Verify production certificates
+
+After a short moment, visiting your domain should show a secure HTTPS connection:
+
+<img src={require("./../../img/docker-compose/status-secure.png").default} alt="Secure Connection" width="1920"/>
+
+The lock icon should show "Secure" (green lock) with "Let's Encrypt Authority X3" or similar as the issuer.
+
+## Log into OpenCloud
+
+Once certificates are verified:
+
+1. Open your domain in a browser:
+
+```bash
+https://cloud.YOUR.DOMAIN
+```
+
+2. Log in with your admin credentials:
+   - Username: `admin`
+   - Password: (the password you configured in the `.env` file)
+
+<img src={require("./../../img/docker-compose/login.png").default} alt="OpenCloud Login" width="1920"/>
+
+## Further Configuration
+
+- [Volume Permissions](./volume-permissions.md) – Ownership, UID/GID mapping, and bind-mount permissions
+- [Production Setup Considerations](./production-considerations.md) – Persistent storage, backups, and production best practices
+- [Configure Keycloak](./keycloak-deployment.md) (optional) – Add Keycloak for enterprise identity management
+- [Configure Authentication](../../../configuration/authentication-and-user-management/) – User management and identity provider integration
+
+## Troubleshooting
+
+If you encounter issues:
+
+1. Check Docker logs: `docker compose logs`
+2. Verify domain DNS records point to your server
+3. Ensure firewall allows HTTP (80) and HTTPS (443)
+4. See [Common Issues & Help](../../../resources/common-issues.md)
diff --git a/versioned_docs/version-7.x/admin/getting-started/container/docker-compose/docker-external-proxy.md b/versioned_docs/version-7.x/admin/getting-started/container/docker-compose/docker-external-proxy.md
new file mode 100644
index 000000000..9bf05a23f
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/getting-started/container/docker-compose/docker-external-proxy.md
@@ -0,0 +1,293 @@
+---
+sidebar_position: 3
+id: external-proxy
+title: Behind External Proxy
+description: How to run OpenCloud behind an external Nginx proxy with Certbot (manual setup).
+draft: false
+---
+
+# Running OpenCloud Behind an External Proxy (Nginx + Certbot Setup)
+
+This guide walks you through setting up OpenCloud behind an external Nginx reverse proxy with Let's Encrypt certificates using `certbot certonly --webroot`.
+
+:::note Using Traefik Instead?
+If you don't have an existing reverse proxy or prefer to let Traefik manage certificates automatically, see [Docker Compose with Integrated Traefik](./docker-compose-base.md) instead.
+:::
+
+## Requirements
+
+- A public server with a static IP
+- Proper DNS records for your domain:
+  - `cloud.YOUR.DOMAIN`
+  - `collabora.YOUR.DOMAIN`
+  - `wopiserver.YOUR.DOMAIN`
+- Installed software:
+  - [Docker & Docker Compose](https://docs.docker.com/engine/install/)
+  - `nginx`
+  - `certbot`
+
+## Connect to Your Server
+
+Log into your server via SSH:
+
+```bash
+ssh root@YOUR.SERVER.IP
+```
+
+## Install Docker
+
+Update your system and install Docker.
+
+## Install Nginx & Certbot
+
+Now install Nginx & Certbot
+
+## Create a Webroot Directory for Certbot
+
+```bash
+sudo mkdir -p /var/www/certbot
+sudo chown -R www-data:www-data /var/www/certbot
+```
+
+## Temporary Nginx Config for HTTP Challenge
+
+Create a temporary config to allow HTTP validation:
+
+```bash
+sudo nano /etc/nginx/sites-available/certbot-challenge
+```
+
+Paste the following config and adjust the URLs:
+
+```nginx
+server {
+    listen 80;
+    server_name cloud.YOUR.DOMAIN collabora.YOUR.DOMAIN wopiserver.YOUR.DOMAIN;
+
+    root /var/www/certbot;
+
+    location /.well-known/acme-challenge/ {
+        allow all;
+        try_files $uri =404;
+    }
+}
+```
+
+Enable and reload Nginx:
+
+```bash
+sudo ln -s /etc/nginx/sites-available/certbot-challenge /etc/nginx/sites-enabled/
+sudo nginx -t && sudo systemctl reload nginx
+```
+
+## Obtain SSL Certificates
+
+Use `certbot` to get your TLS certificates with adjusted URLs:
+
+```bash
+sudo certbot certonly --webroot \
+  -w /var/www/certbot \
+  -d cloud.YOUR.DOMAIN \
+  -d collabora.YOUR.DOMAIN \
+  -d wopiserver.YOUR.DOMAIN \
+  --email your@email.com \
+  --agree-tos \
+  --no-eff-email
+```
+
+Your certificates will be saved under:
+
+- `/etc/letsencrypt/live/cloud.YOUR.DOMAIN/fullchain.pem`
+- `/etc/letsencrypt/live/cloud.YOUR.DOMAIN/privkey.pem`
+
+## Configure and start OpenCloud
+
+Clone the OpenCloud Compose repo and set your environment:
+
+```bash
+git clone https://github.com/opencloud-eu/opencloud-compose.git
+cd opencloud-compose
+cp .env.example .env
+nano .env
+```
+
+Set the following environment variables:
+
+```env
+# INSECURE=true
+
+COMPOSE_FILE=docker-compose.yml:weboffice/collabora.yml:external-proxy/opencloud.yml:external-proxy/collabora.yml
+
+OC_DOMAIN=cloud.YOUR.DOMAIN
+
+INITIAL_ADMIN_PASSWORD=YOUR.SECRET.PASSWORD
+
+COLLABORA_DOMAIN=collabora.YOUR.DOMAIN
+
+WOPISERVER_DOMAIN=wopiserver.YOUR.DOMAIN
+```
+
+The initial Admin password is mandatory for security reasons.
+
+Start the docker compose setup
+
+```bash
+docker compose up -d
+```
+
+## Further Configuration
+
+For production deployments, review [Production Considerations](./production-considerations.md) for:
+
+- Persistent volumes and data recovery
+- Using the appropriate stable branch
+- Permission and ownership best practices
+
+## Set Up the Final Nginx Reverse Proxy
+
+### Remove the temporary certbot config
+
+```bash
+sudo rm /etc/nginx/sites-enabled/certbot-challenge
+```
+
+### Create a new proxy config
+
+```bash
+sudo nano /etc/nginx/sites-available/opencloud
+```
+
+Paste the following configuration and adjust the URLs:
+
+```nginx
+# Redirect HTTP to HTTPS
+server {
+    listen 80;
+    server_name cloud.YOUR.DOMAIN collabora.YOUR.DOMAIN wopiserver.YOUR.DOMAIN;
+
+    location /.well-known/acme-challenge/ {
+        root /var/www/certbot;
+    }
+
+    location / {
+        return 301 https://$host$request_uri;
+    }
+}
+
+# OpenCloud
+server {
+    listen 443 ssl http2;
+    server_name cloud.YOUR.DOMAIN;
+
+    ssl_certificate /etc/letsencrypt/live/cloud.YOUR.DOMAIN/fullchain.pem;
+    ssl_certificate_key /etc/letsencrypt/live/cloud.YOUR.DOMAIN/privkey.pem;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;
+    # Increase max upload size (required for Tus — without this, uploads over 1 MB fail)
+    client_max_body_size 10M;
+
+    # Disable buffering - essential for SSE
+    proxy_buffering off;
+    proxy_request_buffering off;
+
+    # Extend timeouts for long connections
+    proxy_read_timeout 3600s;
+    proxy_send_timeout 3600s;
+    keepalive_requests 100000;
+    keepalive_timeout 5m;
+    http2_max_concurrent_streams 512;
+
+    # Prevent nginx from trying other upstreams
+    proxy_next_upstream off;
+
+    location / {
+        proxy_pass http://127.0.0.1:9200;
+        proxy_set_header Host $host;
+        proxy_set_header X-Real-IP $remote_addr;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header X-Forwarded-Proto $scheme;
+    }
+}
+
+# Collabora
+server {
+  listen 443 ssl http2;
+  server_name collabora.YOUR.DOMAIN;
+
+  ssl_certificate /etc/letsencrypt/live/cloud.YOUR.DOMAIN/fullchain.pem;
+  ssl_certificate_key /etc/letsencrypt/live/cloud.YOUR.DOMAIN/privkey.pem;
+  add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;
+  # Increase max upload size to collabora editor
+  client_max_body_size 10M;
+
+  location / {
+      proxy_pass http://127.0.0.1:9980;
+      proxy_set_header Host $host;
+  }
+
+  location ~ ^/cool/(.*)/ws$ {
+      proxy_pass http://127.0.0.1:9980;
+      proxy_set_header Upgrade $http_upgrade;
+      proxy_set_header Connection "Upgrade";
+      proxy_set_header Host $host;
+  }
+
+}
+
+# WOPI Server
+server {
+  listen 443 ssl http2;
+  server_name wopiserver.YOUR.DOMAIN;
+
+  ssl_certificate /etc/letsencrypt/live/cloud.YOUR.DOMAIN/fullchain.pem;
+  ssl_certificate_key /etc/letsencrypt/live/cloud.YOUR.DOMAIN/privkey.pem;
+  add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;
+
+  location / {
+      proxy_pass http://127.0.0.1:9300;
+      proxy_set_header Host $host;
+      proxy_set_header X-Real-IP $remote_addr;
+      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+      proxy_set_header X-Forwarded-Proto $scheme;
+  }
+}
+```
+
+:::info Version Differences
+Starting from nginx 1.25.0, the `http2` directive syntax changed from: `listen 443 ssl http2;` to `listen 443 ssl; http2 on;`
+:::
+
+:::note
+We enabled HTTP/2 and increased keep-alive limits to prevent large syncs from failing and ensure stable client connections, since nginx closes connections after ~1,000 requests by default.
+:::
+
+Thanks to [mitexleo](https://github.com/mitexleo) for the Ngnix example configuration on GitHub and [zerox80](https://github.com/zerox80) for the adjustments
+
+Enable and reload Nginx:
+
+```bash
+sudo ln -s /etc/nginx/sites-available/opencloud /etc/nginx/sites-enabled/
+sudo nginx -t && sudo systemctl reload nginx
+```
+
+## Test Certificate Renewal
+
+```bash
+sudo certbot renew --dry-run
+```
+
+Your OpenCloud instance is now running securely behind a fully configured external Nginx reverse proxy with HTTPS.
+
+## Timeout Considerations
+
+When using a reverse proxy other than the documented Nginx example, make sure that request and response timeouts are configured for long-running uploads.
+
+Slow uploads or large file uploads can take longer than the default timeout of some reverse proxies. If the timeout is too low, uploads may fail with `502 Bad Gateway` after about 60 seconds.
+
+For custom reverse proxy setups, configure the equivalent of the relevant Nginx options, such as:
+
+- `proxy_read_timeout`
+- `proxy_send_timeout`
+- `proxy_request_buffering off`
+- `proxy_buffering off`
+
+The exact option names depend on the reverse proxy in use.
diff --git a/versioned_docs/version-7.x/admin/getting-started/container/docker-compose/index.md b/versioned_docs/version-7.x/admin/getting-started/container/docker-compose/index.md
new file mode 100644
index 000000000..ae32f49c0
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/getting-started/container/docker-compose/index.md
@@ -0,0 +1,46 @@
+---
+sidebar_position: 1
+id: docker-compose-overview
+title: Docker Compose Overview
+description: Choose your Docker Compose deployment architecture for OpenCloud
+---
+
+# Docker Compose Deployment
+
+This section guides you through deploying OpenCloud using Docker Compose. We support two main deployment architectures, suitable for different infrastructure scenarios.
+
+## Choose Your Deployment Path
+
+### 1. Integrated Traefik (Recommended for most users)
+
+Use the built-in Traefik reverse proxy and automatic Let's Encrypt SSL certificates. This is the standard, recommended path for new deployments.
+
+Best for:
+
+- Standalone servers
+- No existing reverse proxy infrastructure
+- Simple, self-contained setup
+
+[Get Started with Integrated Traefik →](./docker-compose-base.md)
+
+### 2. Behind External Proxy
+
+Use this setup if you want to run OpenCloud behind your own reverse proxy instead of the integrated Traefik setup.
+
+The guide includes the required OpenCloud settings and an example Nginx configuration.
+
+Best for:
+
+- Existing reverse proxy environments
+- Custom TLS handling
+- Separate proxy management
+
+[Deploy Behind External Proxy →](./docker-external-proxy.md)
+
+## Further Configuration
+
+After choosing and completing your deployment:
+
+- [Production Setup Considerations](./production-considerations.md) – Persistent storage, backups, image versions
+- [Verify TLS Certificates](./docker-compose-base.md#verify-tls-certificates) – Validate your SSL setup
+- [Configure Authentication](../../../configuration/authentication-and-user-management/) – Users, authentication, and optional Keycloak integration
diff --git a/versioned_docs/version-7.x/admin/getting-started/container/docker-compose/keycloak-deployment.md b/versioned_docs/version-7.x/admin/getting-started/container/docker-compose/keycloak-deployment.md
new file mode 100644
index 000000000..a5af53dc1
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/getting-started/container/docker-compose/keycloak-deployment.md
@@ -0,0 +1,151 @@
+---
+sidebar_position: 6
+id: docker-compose-keycloak-deployment
+title: Keycloak Integration
+description: Add Keycloak identity management to your Docker Compose OpenCloud deployment
+draft: false
+---
+
+# Keycloak Integration with Docker Compose
+
+This guide explains how to enable Keycloak as an identity provider (IdP) for your Docker Compose OpenCloud deployment. This provides enterprise-grade user and access management.
+
+:::note
+This page covers deployment setup only. For detailed Keycloak configuration, user management, and integration patterns, see the [Keycloak Configuration Guide](../../../configuration/authentication-and-user-management/keycloak.md).
+:::
+
+## Prerequisites
+
+- An existing OpenCloud Docker Compose deployment
+- Understanding of [Keycloak as an identity provider](../../../configuration/authentication-and-user-management/keycloak.md)
+
+## Enable Keycloak in `.env`
+
+Edit your environment configuration file:
+
+```bash
+cd opencloud-compose
+nano .env
+```
+
+Add or uncomment the following lines to enable Keycloak with integrated LDAP:
+
+```bash
+# Enable Keycloak + LDAP services
+COMPOSE_FILE=docker-compose.yml:idm/ldap-keycloak.yml:traefik/opencloud.yml:traefik/ldap-keycloak.yml
+
+# Keycloak domain (without https://)
+KEYCLOAK_DOMAIN=keycloak.YOUR.DOMAIN
+
+# Keycloak admin credentials
+KEYCLOAK_ADMIN=admin
+KEYCLOAK_ADMIN_PASSWORD=ChangeMeToASecurePassword
+```
+
+### Available Docker Compose configurations
+
+The `opencloud-compose` repository provides several idm (Identity Management) options:
+
+| Configuration           | Use Case                                                       |
+| ----------------------- | -------------------------------------------------------------- |
+| `idm/ldap-keycloak.yml` | Keycloak with integrated OpenLDAP (recommended for new setups) |
+| `idm/keycloak.yml`      | Keycloak standalone without LDAP                               |
+| `idm/openldap.yml`      | OpenLDAP only (for external IdP integration)                   |
+
+Choose the configuration that matches your authentication infrastructure.
+
+## Start OpenCloud with Keycloak
+
+After updating `.env`, start the deployment:
+
+```bash
+docker compose up -d
+```
+
+Docker will pull and start the Keycloak container along with OpenCloud services.
+
+### Wait for services to initialize
+
+Keycloak may take a minute or two to start. Monitor the logs:
+
+```bash
+docker compose logs keycloak
+```
+
+Look for messages indicating Keycloak is ready to accept connections.
+
+## Access Keycloak
+
+Once running, access the Keycloak admin console:
+
+```bash
+https://keycloak.YOUR.DOMAIN
+```
+
+Log in with the credentials you set in `.env`:
+
+- Username: `admin` (or your `KEYCLOAK_ADMIN` value)
+- Password: Your `KEYCLOAK_ADMIN_PASSWORD`
+
+## Next Steps
+
+### 1. Configure Keycloak for OpenCloud
+
+The Docker Compose setup auto-imports a base configuration for OpenCloud via `keycloak-realm.dist.json`. However, you'll likely need to:
+
+- Create users and assign roles
+- Configure authentication flows
+- Set up LDAP federation (if using `ldap-keycloak.yml`)
+- Configure OIDC client settings
+
+See [Keycloak Configuration & Integration Guide](../../../configuration/authentication-and-user-management/keycloak.md) for detailed instructions.
+
+### 2. Create Users in Keycloak
+
+Follow the guide [Adding Users with Keycloak](../../../configuration/authentication-and-user-management/keycloak-user.md) to:
+
+- Assign admin roles
+- Create users with standard or guest permissions
+- Enable self-registration
+
+### 3. Update OpenCloud Configuration
+
+Configure OpenCloud to use Keycloak as the identity provider. This typically involves setting OIDC-related environment variables. See the [Keycloak Integration documentation](../../../configuration/authentication-and-user-management/keycloak.md) for details.
+
+## Troubleshooting
+
+### Keycloak won't start
+
+Check container logs:
+
+```bash
+docker compose logs keycloak
+```
+
+Common issues:
+
+- Insufficient disk space or memory
+- Port conflicts (Keycloak uses port 8080 internally)
+- Database connection issues
+
+### Can't access Keycloak admin console
+
+Verify:
+
+1. The domain `keycloak.YOUR.DOMAIN` resolves to your server
+2. Traefik has successfully assigned SSL certificates (check via `docker compose logs traefik`)
+3. Keycloak container is running: `docker compose ps keycloak`
+
+### LDAP federation issues
+
+If using `idm/ldap-keycloak.yml`:
+
+1. Verify OpenLDAP is running: `docker compose ps openldap`
+2. Check Keycloak logs for LDAP connection errors
+3. Verify LDAP user federation is configured correctly in Keycloak admin console
+
+## See Also
+
+- [Full Keycloak Integration Guide](../../../configuration/authentication-and-user-management/keycloak.md) – Configuration, modes, and advanced setup
+- [User Management with Keycloak](../../../configuration/authentication-and-user-management/keycloak-user.md) – Creating users and managing roles
+- [Production Considerations](./production-considerations.md) – Backup and production best practices
diff --git a/versioned_docs/version-7.x/admin/getting-started/container/docker-compose/production-considerations.md b/versioned_docs/version-7.x/admin/getting-started/container/docker-compose/production-considerations.md
new file mode 100644
index 000000000..efe7f30ad
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/getting-started/container/docker-compose/production-considerations.md
@@ -0,0 +1,84 @@
+---
+sidebar_position: 4
+id: docker-compose-production-considerations
+title: Production Considerations
+description: Best practices and recommendations for production OpenCloud deployments with Docker Compose
+---
+
+# Production Setup Considerations
+
+This guide outlines essential best practices and configurations for running OpenCloud in a production environment with Docker Compose.
+
+:::caution Production Setup Recommended
+By default, OpenCloud stores configuration and data inside internal Docker volumes.  
+This works fine for local development or quick evaluations — but is not suitable for production environments.
+:::
+
+## Mount Persistent Volumes
+
+For production deployments, you should mount persistent local directories for configuration and data. This ensures:
+
+- Data durability – Configuration and data persist across container restarts
+- Easier backups and recovery – Access files directly from the host
+- Full control over storage location and permissions – Meet organizational compliance requirements
+
+### Update your `.env` file with custom paths
+
+Edit your environment configuration to specify local mount points:
+
+```bash
+nano .env
+```
+
+Add or uncomment these variables:
+
+```bash
+OC_CONFIG_DIR=/your/local/path/opencloud/config
+OC_DATA_DIR=/your/local/path/opencloud/data
+```
+
+Replace `/your/local/path/opencloud` with your desired location (e.g., `/opt/opencloud` or `/mnt/data/opencloud`).
+
+### Ensure proper folder ownership and permissions
+
+Create the directories and set correct ownership for the container user (UID/GID 1000:1000 by default):
+
+```bash
+sudo mkdir -p /your/local/path/opencloud/{config,data}
+sudo chown -R 1000:1000 /your/local/path/opencloud
+sudo chmod -R 0700 /your/local/path/opencloud
+```
+
+If these variables are not set, Docker will use internal volumes. These volumes may be removed when containers are deleted, which means your configuration and data may be lost. This setup is therefore not recommended for production use.
+
+:::caution Security Warning
+
+The user with UID 1000 on your host system will have full access to these mounted directories. This means that any local user account with this ID can read, modify, or delete OpenCloud config and data files.
+
+This can pose a security risk in shared or multi-user environments. Make sure to implement proper user and permission management and consider isolating access to these directories.
+
+For more details on volume permissions, see [Volume Permissions and UID/GID Management](./volume-permissions.md).
+
+:::
+
+## Use the appropriate repository branch
+
+By default, the `main` branch of the `opencloud-compose` repository tracks the rolling release.
+
+For production deployments, use the current `stable-*` branch instead, for example:
+
+```bash
+git checkout stable-4.0
+```
+
+Stable branch names change over time as new stable releases become available. Moving from one stable-\* branch to another is an update and should be handled accordingly.
+
+## Backup and Recovery Strategy
+
+With persistent volumes in place, you should implement a backup and recovery strategy for your OpenCloud deployment:
+
+- Regular backups of `OC_CONFIG_DIR` and `OC_DATA_DIR`
+- Off-site or remote storage for disaster recovery
+- Regular verification and testing of restore procedures
+
+For detailed backup guidance, see the [Backup documentation](../../../maintenance/backup.md).
diff --git a/versioned_docs/version-7.x/admin/getting-started/container/docker-compose/volume-permissions.md b/versioned_docs/version-7.x/admin/getting-started/container/docker-compose/volume-permissions.md
new file mode 100644
index 000000000..25f240565
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/getting-started/container/docker-compose/volume-permissions.md
@@ -0,0 +1,111 @@
+---
+sidebar_position: 7
+id: docker-compose-volume-permissions
+title: Volume Permissions
+description: Configure filesystem permissions for OpenCloud Docker volumes
+---
+
+# Volume Permissions
+
+OpenCloud runs as a non-root user inside the container and requires read and write access to the mounted configuration and data directories.
+
+When using bind mounts, ensure that the directories referenced by `OC_CONFIG_DIR` and `OC_DATA_DIR` are writable by the container user.
+
+## Recommended permissions
+
+Create the directories on the host and assign them to UID and GID `1000`:
+
+```bash
+sudo mkdir -p /your/local/path/opencloud/{config,data}
+sudo chown -R 1000:1000 /your/local/path/opencloud
+sudo chmod -R 0700 /your/local/path/opencloud
+```
+
+To verify the ownership on the host, run:
+
+```bash
+ls -ln /your/local/path/opencloud/
+```
+
+## Rootless Docker and UID Mapping
+
+When Docker runs in rootless mode, bind-mounted directories do not always use the same ownership mapping you see in a regular Docker setup.
+
+The OpenCloud container still runs as UID and GID `1000` inside the container, but rootless Docker maps that identity into the subordinate UID and GID range configured for your host user. As a result, a host directory owned by `1000:1000` may not be writable inside the container.
+
+### Check subordinate IDs
+
+You can inspect the subordinate UID and GID ranges on the host with:
+
+```bash
+grep "^$(whoami):" /etc/subuid
+grep "^$(whoami):" /etc/subgid
+```
+
+If the output looks like this:
+
+```text
+youruser:100000:65536
+youruser:100000:65536
+```
+
+then container UID `1000` maps to host UID `101000`.
+
+### Adjust ownership
+
+In that case, set the bind-mounted directories to the mapped host UID and GID:
+
+```bash
+sudo chown -R 101000:101000 /your/local/path/opencloud
+sudo chmod -R 0700 /your/local/path/opencloud
+```
+
+### Verify access inside the container
+
+Do not rely only on host-side ownership values in rootless mode. Verify that the OpenCloud container can actually read and write the mounted directories:
+
+```bash
+docker compose exec opencloud sh
+ls -la /etc/opencloud
+ls -la /var/lib/opencloud
+touch /var/lib/opencloud/.write-test
+```
+
+If those commands succeed, the permissions are configured correctly.
+
+### Prefer a simpler setup
+
+If you do not want to manage mapped host UID and GID values manually, consider using Docker named volumes instead of bind mounts for rootless setups.
+
+## Troubleshooting
+
+If OpenCloud reports permission errors, verify the mounted directories from both the host and the container.
+
+### Check on the host
+
+```bash
+ls -ln /your/local/path/opencloud/
+```
+
+### Check inside the container
+
+```bash
+docker compose exec opencloud ls -la /etc/opencloud
+docker compose exec opencloud ls -la /var/lib/opencloud
+```
+
+If needed, re-apply ownership and permissions on the host:
+
+```bash
+sudo chown -R 1000:1000 /your/local/path/opencloud
+sudo chmod -R 0700 /your/local/path/opencloud
+```
+
+## Further reading
+
+For more information about Docker storage, see the official Docker documentation:
+
+- [Volumes](https://docs.docker.com/storage/volumes/)
+- [Bind mounts](https://docs.docker.com/engine/storage/bind-mounts/)
+
+For backup recommendations, see [Backup and recovery](../../../maintenance/backup.md).
diff --git a/versioned_docs/version-7.x/admin/getting-started/container/docker.md b/versioned_docs/version-7.x/admin/getting-started/container/docker.md
new file mode 100644
index 000000000..45da011f8
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/getting-started/container/docker.md
@@ -0,0 +1,79 @@
+---
+sidebar_position: 1
+id: docker
+title: Docker
+description: Classic docker setup.
+draft: false
+---
+
+# Docker
+
+Spin up a temporary local instance of OpenCloud using Docker
+
+## Prerequisites
+
+- Linux, Mac or Windows Subsystem for Linux [(WSL)](https://learn.microsoft.com/en-us/windows/wsl/install)
+- [Docker](https://docs.docker.com/compose/install/)
+
+## Create Required Directories for Bind Mounts
+
+```bash
+mkdir -p $HOME/opencloud/opencloud-config
+mkdir -p $HOME/opencloud/opencloud-data
+```
+
+## Pull OpenCloud Image
+
+```bash
+docker pull opencloudeu/opencloud-rolling:latest
+```
+
+## Initialize OpenCloud (First-time Setup)
+
+```bash
+docker run --rm -it \
+    -v $HOME/opencloud/opencloud-config:/etc/opencloud \
+    -v $HOME/opencloud/opencloud-data:/var/lib/opencloud \
+    -e IDM_ADMIN_PASSWORD=admin \
+    opencloudeu/opencloud-rolling:latest init
+```
+
+You can set your own password using `IDM_ADMIN_PASSWORD=your_password`. If not set, a password will be auto-generated
+
+<img src={require("./../img/quick-guide/docker-opencloud-init.png").default} alt="Admin general" width="1920"/>
+
+## Start OpenCloud
+
+```bash
+docker run \
+    --name opencloud \
+    --rm \
+    -d \
+    -p 9200:9200 \
+    -v $HOME/opencloud/opencloud-config:/etc/opencloud \
+    -v $HOME/opencloud/opencloud-data:/var/lib/opencloud \
+    -e OC_INSECURE=true \
+    -e PROXY_HTTP_ADDR=0.0.0.0:9200 \
+    -e OC_URL=https://localhost:9200 \
+    opencloudeu/opencloud-rolling:latest
+```
+
+## Login
+
+Login with your browser:
+
+- [https://localhost:9200](https://localhost:9200)
+- user: admin
+- password: admin
+
+<img src={require("./../img/quick-guide/quick-login.png").default} alt="Admin general" width="1920"/>
+
+## Conclusion
+
+Your OpenCloud server is now running and ready to use 🚀
+
+## Troubleshooting
+
+If you encounter any issues or errors, try finding a solution here:
+
+- [Common Issues & Help](../../resources/common-issues)
diff --git a/versioned_docs/version-7.x/admin/getting-started/container/index.md b/versioned_docs/version-7.x/admin/getting-started/container/index.md
new file mode 100644
index 000000000..80b87af5b
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/getting-started/container/index.md
@@ -0,0 +1,15 @@
+---
+sidebar_position: 0
+id: admin-getting-started-container
+title: Container
+description: Overview of container-based OpenCloud deployment guides
+---
+
+# Container Deployments
+
+Use the container guides if you want to run OpenCloud with Docker or Docker Compose.
+
+## In this section
+
+- [Docker](./docker.md) - Run OpenCloud with a plain Docker setup
+- [Docker Compose](./docker-compose/index.md) - Use Docker Compose with Traefik or an external proxy
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/cd-opencloud-subdirectory.png b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/cd-opencloud-subdirectory.png
new file mode 100755
index 000000000..29c9ba457
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/cd-opencloud-subdirectory.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/cd-opencloud.png b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/cd-opencloud.png
new file mode 100755
index 000000000..b59d16119
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/cd-opencloud.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/corepack-enable.png b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/corepack-enable.png
new file mode 100755
index 000000000..3fd2cea92
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/corepack-enable.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/git-clone.png b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/git-clone.png
new file mode 100755
index 000000000..0eb9aaa0b
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/git-clone.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/install-corepack.png b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/install-corepack.png
new file mode 100755
index 000000000..98b728128
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/install-corepack.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/install-git.png b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/install-git.png
new file mode 100755
index 000000000..147d64ddc
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/install-git.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/install-golang.png b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/install-golang.png
new file mode 100755
index 000000000..62d92feea
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/install-golang.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/install-npm.png b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/install-npm.png
new file mode 100755
index 000000000..bd9cf3a2f
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/install-npm.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/localhost-warnung.png b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/localhost-warnung.png
new file mode 100755
index 000000000..ff8a45fb3
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/localhost-warnung.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/login.png b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/login.png
new file mode 100755
index 000000000..326d15d83
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/login.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/opencloud-init.png b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/opencloud-init.png
new file mode 100755
index 000000000..bc5740622
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/opencloud-init.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/opencloud-server.png b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/opencloud-server.png
new file mode 100755
index 000000000..5583b427d
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/bare-metal/opencloud-server.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/assign-role.png b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/assign-role.png
new file mode 100644
index 000000000..958157dab
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/assign-role.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/certificate-details.png b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/certificate-details.png
new file mode 100644
index 000000000..43a55d060
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/certificate-details.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/certificate-viewer.png b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/certificate-viewer.png
new file mode 100644
index 000000000..073b90d6c
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/certificate-viewer.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/credentials.png b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/credentials.png
new file mode 100644
index 000000000..bacb58deb
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/credentials.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/fill-in-userdata.png b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/fill-in-userdata.png
new file mode 100644
index 000000000..84ca42637
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/fill-in-userdata.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/filter-by-realm-roles.png b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/filter-by-realm-roles.png
new file mode 100644
index 000000000..385450362
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/filter-by-realm-roles.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/keycloak-dashboard.png b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/keycloak-dashboard.png
new file mode 100644
index 000000000..e57acb112
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/keycloak-dashboard.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/keycloak-login.png b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/keycloak-login.png
new file mode 100644
index 000000000..fa4c020f8
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/keycloak-login.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/login.png b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/login.png
new file mode 100644
index 000000000..0baae2580
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/login.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/realm-roles.png b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/realm-roles.png
new file mode 100644
index 000000000..f6e867be2
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/realm-roles.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/role-mapping.png b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/role-mapping.png
new file mode 100644
index 000000000..018e08d0a
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/role-mapping.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/set-password.png b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/set-password.png
new file mode 100644
index 000000000..382249f54
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/set-password.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/status-secure.png b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/status-secure.png
new file mode 100644
index 000000000..e0625c57c
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/status-secure.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/subordinate-ca's.png b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/subordinate-ca's.png
new file mode 100644
index 000000000..318c99ee7
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/subordinate-ca's.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/top-left-dropdown.png b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/top-left-dropdown.png
new file mode 100644
index 000000000..d8cdbd9a6
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/top-left-dropdown.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/users-section.png b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/users-section.png
new file mode 100644
index 000000000..7ee111639
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/docker-compose/users-section.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/quick-guide/collabora-accept-self-signed-cert.png b/versioned_docs/version-7.x/admin/getting-started/img/quick-guide/collabora-accept-self-signed-cert.png
new file mode 100644
index 000000000..1faad6a7e
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/quick-guide/collabora-accept-self-signed-cert.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/quick-guide/docker-opencloud-init.png b/versioned_docs/version-7.x/admin/getting-started/img/quick-guide/docker-opencloud-init.png
new file mode 100644
index 000000000..61e5b83ea
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/quick-guide/docker-opencloud-init.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/quick-guide/quick-docker-compose-up.png b/versioned_docs/version-7.x/admin/getting-started/img/quick-guide/quick-docker-compose-up.png
new file mode 100644
index 000000000..44ba2bb7c
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/quick-guide/quick-docker-compose-up.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/quick-guide/quick-login.png b/versioned_docs/version-7.x/admin/getting-started/img/quick-guide/quick-login.png
new file mode 100644
index 000000000..0baae2580
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/quick-guide/quick-login.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/change-env-for-storage.png b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/change-env-for-storage.png
new file mode 100644
index 000000000..adf3dc575
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/change-env-for-storage.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/docker-compose-check.png b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/docker-compose-check.png
new file mode 100644
index 000000000..8bb71e91b
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/docker-compose-check.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/docker-user-check.png b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/docker-user-check.png
new file mode 100644
index 000000000..1cca06867
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/docker-user-check.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/error-mounting.png b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/error-mounting.png
new file mode 100644
index 000000000..102f05fb6
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/error-mounting.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/find-external-hd.png b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/find-external-hd.png
new file mode 100644
index 000000000..d98d3d821
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/find-external-hd.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/format-drive.png b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/format-drive.png
new file mode 100644
index 000000000..3fc6190fe
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/format-drive.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/ip-router.png b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/ip-router.png
new file mode 100644
index 000000000..e3f74d769
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/ip-router.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/noip.png b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/noip.png
new file mode 100644
index 000000000..f27367b19
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/noip.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/oc-domain.png b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/oc-domain.png
new file mode 100644
index 000000000..abddfa643
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/oc-domain.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/portforwarding.png b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/portforwarding.png
new file mode 100644
index 000000000..a46f439b0
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/portforwarding.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/reachable-via-URL.png b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/reachable-via-URL.png
new file mode 100644
index 000000000..9fd80f336
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/reachable-via-URL.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/ssh-activate.png b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/ssh-activate.png
new file mode 100644
index 000000000..704ea0e1a
Binary files /dev/null and b/versioned_docs/version-7.x/admin/getting-started/img/raspberrypi/ssh-activate.png differ
diff --git a/versioned_docs/version-7.x/admin/getting-started/index.md b/versioned_docs/version-7.x/admin/getting-started/index.md
new file mode 100644
index 000000000..208537467
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/getting-started/index.md
@@ -0,0 +1,16 @@
+---
+sidebar_position: 0
+id: admin-getting-started
+title: Getting Started
+description: Overview of the OpenCloud getting started guides for administrators
+---
+
+# Getting Started
+
+Use this section to install and deploy OpenCloud in the environment that fits your setup best.
+
+## In this section
+
+- [Requirements](./requirements.md) - Check prerequisites before you install OpenCloud
+- [Container Deployments](./container/index.md) - Run OpenCloud in Docker or Docker Compose
+- [Other Deployment Options](./other/index.md) - Bare metal and Raspberry Pi installations
diff --git a/versioned_docs/version-7.x/admin/getting-started/kubernetes.md b/versioned_docs/version-7.x/admin/getting-started/kubernetes.md
new file mode 100644
index 000000000..27b5b0209
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/getting-started/kubernetes.md
@@ -0,0 +1,7 @@
+---
+sidebar_position: 8
+id: kubernetes
+title: Kubernetes
+description: Kubernetes
+draft: true
+---
diff --git a/versioned_docs/version-7.x/admin/getting-started/other/_category_.json b/versioned_docs/version-7.x/admin/getting-started/other/_category_.json
new file mode 100644
index 000000000..f82a569ef
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/getting-started/other/_category_.json
@@ -0,0 +1,8 @@
+{
+  "label": "Other",
+  "position": 3,
+  "link": {
+    "type": "doc",
+    "id": "admin-getting-started-other"
+  }
+}
diff --git a/versioned_docs/version-7.x/admin/getting-started/other/bare-metal.md b/versioned_docs/version-7.x/admin/getting-started/other/bare-metal.md
new file mode 100644
index 000000000..0160169dd
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/getting-started/other/bare-metal.md
@@ -0,0 +1,131 @@
+---
+sidebar_position: 5
+id: bare-metal
+title: Bare-Metal
+description: Manual, minimalist setup with essential features.
+draft: false
+---
+
+# Bare-Metal
+
+User Guide for Installing OpenCloud Bare-Metal
+
+Follow the steps below to install and configure OpenCloud on your system.<br/>
+This example is on Linux Ubuntu 24.04 distribution!
+
+:::danger[Disclaimer]
+Bare-metal deployments are not officially supported by OpenCloud. They are great for quick evaluation but are undocumented and have a minimalist feature set. If you choose this setup, you are on your own. With great power comes great responsibility.
+:::
+
+## Install Git and clone the repository
+
+- Open a terminal.
+
+- Update your package list:
+
+  ```bash
+  sudo apt update && apt upgrade
+  ```
+
+- Install Git using the following command:
+
+  ```bash
+  sudo apt install git
+  ```
+
+  <img src={require("./../img/bare-metal/install-git.png").default} alt="install git" width="1920"/>
+
+- Clone the OpenCloud repository:
+
+  ```bash
+  git clone https://github.com/opencloud-eu/opencloud.git
+  ```
+
+  <img src={require("./../img/bare-metal/git-clone.png").default} alt="git clone" width="1920"/>
+
+## Install the required packages
+
+- Download and install Go by following the official guide: 🔗[**go.dev/doc/install**](https://go.dev/doc/install)
+
+- Install npm (Node Package Manager):
+
+  ```bash
+  sudo apt install npm -y
+  ```
+
+  <img src={require("./../img/bare-metal/install-npm.png").default} alt="install npm" width="1920"/>
+
+- Install corepack globally:
+
+  ```bash
+  sudo npm install -g corepack
+  ```
+
+  <img src={require("./../img/bare-metal/install-corepack.png").default} alt="install corepack" width="1920"/>
+
+- Enable `pnpm` using corepack:
+
+  ```bash
+  corepack enable pnpm
+  ```
+
+  <img src={require("./../img/bare-metal/corepack-enable.png").default} alt="corepack enable" width="1920"/>
+
+## Build process and OpenCloud initialization
+
+- Navigate to the OpenCloud directory:
+
+  ```bash
+  cd opencloud
+  ```
+
+  <img src={require("./../img/bare-metal/cd-opencloud.png").default} alt="cd opencloud" width="1920"/>
+
+- Run the build generate process:
+
+  ```bash
+  make clean generate
+  make -C opencloud build
+  ```
+
+- Navigate into the opencloud subdirectory that was just built:
+
+  ```bash
+  cd opencloud
+  ```
+
+- Initialize OpenCloud with insecure configuration and set an admin password:
+
+  ```bash
+  ./bin/opencloud init --insecure true --admin-password admin
+  ```
+
+  <img src={require("./../img/bare-metal/opencloud-init.png").default} alt="opencloud init" width="1920"/>
+
+- Start the OpenCloud server:
+
+  ```bash
+  ./bin/opencloud server
+  ```
+
+  <img src={require("./../img/bare-metal/opencloud-server.png").default} alt="opencloud server" width="1920"/>
+
+## Login
+
+Login with your browser:
+
+- [https://localhost:9200](https://localhost:9200)
+- user: **admin**
+- password: **admin**
+
+<img src={require("./../img/bare-metal/login.png").default} alt="login" width="1920"/>
+
+## Conclusion
+
+Your OpenCloud server is now running and ready to use 🚀
+
+## Troubleshooting
+
+If you encounter any issues or errors, try finding a solution here
+
+- [Common Issues & Help](../../resources/common-issues)
diff --git a/versioned_docs/version-7.x/admin/getting-started/other/index.md b/versioned_docs/version-7.x/admin/getting-started/other/index.md
new file mode 100644
index 000000000..bbe4f07f7
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/getting-started/other/index.md
@@ -0,0 +1,15 @@
+---
+sidebar_position: 0
+id: admin-getting-started-other
+title: Other
+description: Alternative OpenCloud deployment guides
+---
+
+# Other Deployment Options
+
+These guides cover deployments outside the standard container-based setup.
+
+## In this section
+
+- [Bare Metal](./bare-metal.md) - Install OpenCloud directly on a server (not officially supported)
+- [Raspberry Pi](./raspberry-pi.md) - Run OpenCloud on a Raspberry Pi
diff --git a/versioned_docs/version-7.x/admin/getting-started/other/raspberry-pi.md b/versioned_docs/version-7.x/admin/getting-started/other/raspberry-pi.md
new file mode 100644
index 000000000..615117c56
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/getting-started/other/raspberry-pi.md
@@ -0,0 +1,282 @@
+---
+sidebar_position: 6
+id: raspberry-pi
+title: Raspberry Pi
+description: OpenCLoud on a Raspberry Pi
+draft: false
+---
+
+# OpenCloud on a Raspberry Pi
+
+:::note
+The installation of OpenCloud on a Raspberry Pi is intended for private or non-production use only.  
+It is not recommended for enterprise or critical environments due to the hardware's limited resources and potential performance constraints.
+:::
+
+## Hardware requirements
+
+- Minimum Raspberry Pi 4B with at least 4 GB RAM connected via LAN or WLAN
+- Micro SD card with at least 32 GB storage space
+- External hard disk or USB stick (optional) for additional storage space
+
+## Install operating system
+
+- Install Raspberry Pi OS  
+  A very detailed and understandable guide is available at:  
+  [Raspberry Pi Getting Started](https://pimylifeup.com/raspberry-pi-getting-started/)
+
+- SSH must be enabled if you want to access the machine remotely.
+
+  This is usually required when your Raspberry Pi is running without a connected keyboard and display.
+
+- If the Raspberry Pi is to be connected to WLAN, the login data for the WLAN must be entered.
+
+## Connecting with SSH
+
+Start the Raspberry Pi with the SD card and connect via SSH.  
+The IP for this can be viewed in your router.
+
+<img src={require("./../img/raspberrypi/ip-router.png").default} alt="find ip from raspberry-pi in router" width="500"/>
+
+### Establish connection via SSH
+
+```bash
+ssh pi@YOUR-IP
+```
+
+After the first login, you should change the password for security reasons:
+
+```bash
+passwd
+```
+
+## Installing Docker and Docker Compose
+
+Detailed installation instructions for Docker can be found here:  
+[Install Docker on Raspberry Pi](https://pimylifeup.com/raspberry-pi-docker/)
+
+- Perform update and upgrade:
+
+```bash
+sudo apt update && sudo apt upgrade -y
+```
+
+- Install Docker via script:
+
+```bash
+curl -fsSL test.docker.com -o get-docker.sh && sh get-docker.sh
+```
+
+- Add current user to the Docker group:
+
+```bash
+sudo usermod -aG docker ${USER}
+```
+
+- Check if it's working:
+
+```bash
+groups ${USER}
+```
+
+<img src={require("./../img/raspberrypi/docker-user-check.png").default} alt="Check docker user" width="500"/>
+
+- Reboot the Raspberry Pi:
+
+```bash
+sudo shutdown -r now
+```
+
+## Clone OpenCloud repository
+
+```bash
+git clone https://github.com/opencloud-eu/opencloud-compose.git
+```
+
+## Start the Docker Compose setup
+
+```bash
+cd opencloud-compose
+```
+
+Copy the `.env.example` file:
+
+```bash
+cp .env.example .env
+```
+
+Edit the `.env` file:
+
+```bash
+nano .env
+```
+
+Activate the minimal OpenCloud setup by un-commenting this line:
+
+```bash
+COMPOSE_FILE=docker-compose.yml:traefik/opencloud.yml
+```
+
+Look for the following line and set here your admin password:
+
+```bash
+INITIAL_ADMIN_PASSWORD=YourSecurePassword
+```
+
+Then start Docker:
+
+```bash
+docker compose up
+```
+
+Now OpenCloud is running locally on your Raspberry Pi, and you can adjust it to your needs.
+
+We will describe how to mount an external disk or USB stick and make OpenCloud available outside the local network using No-IP.
+
+## Mount external hard disk or USB stick
+
+### Find your external drive
+
+```bash
+lsblk
+```
+
+<img src={require("./../img/raspberrypi/find-external-hd.png").default} alt="find the external hd" width="500"/>
+
+### Format the drive to ext4
+
+```bash
+sudo mkfs.ext4 /dev/sda1 -L DATA
+```
+
+<img src={require("./../img/raspberrypi/format-drive.png").default} alt="format drive" width="500"/>
+
+### Add fstab entry for auto-mounting
+
+Open `fstab`:
+
+```bash
+sudo nano /etc/fstab
+```
+
+Add this line:
+
+```bash
+LABEL=DATA /mnt/data ext4 auto,defaults 0 0
+```
+
+### Create the mount point and set permissions
+
+```bash
+sudo mkdir -p /mnt/data
+sudo chown -R 1000:1000 /mnt/data
+```
+
+### Mount the drive
+
+```bash
+sudo mount -a
+```
+
+If an error occurs:
+
+<img src={require("./../img/raspberrypi/error-mounting.png").default} alt="error mounting" width="500"/>
+
+Run:
+
+```bash
+systemctl daemon-reload
+```
+
+And try mounting again.
+
+## Mount external storage in Docker
+
+Stop Docker:
+
+```bash
+docker compose down
+```
+
+Open the `.env` file:
+
+```bash
+cd opencloud-compose
+nano .env
+```
+
+Set the `OC_DATA_DIR` variable to your mounted storage path, e.g.:
+
+```env
+OC_DATA_DIR=/mnt/data
+```
+
+<img src={require("./../img/raspberrypi/change-env-for-storage.png").default} alt="change env for storage" width="500"/>
+
+Restart Docker:
+
+```bash
+docker compose up
+```
+
+## Make OpenCloud externally available
+
+### Create DynDNS hostname
+
+Register at [No-IP](https://www.noip.com/) and create a hostname, e.g. `opencloud.webhop.me`.
+
+<img src={require("./../img/raspberrypi/noip.png").default} alt="noip hostname input" width="500"/>
+
+### Configure DynDNS in your router
+
+Use your router’s web interface to:
+
+- Locate the Dynamic DNS settings
+- Select **No-IP** as provider
+- Enter your No-IP credentials
+- Use the created hostname (e.g. `opencloud.webhop.me`)
+- Save and test the settings
+
+More help: [No-IP Support](https://www.noip.com/support/knowledgebase/how-to-configure-ddns-in-router)
+
+### Configure port forwarding
+
+1. Ensure your Raspberry Pi always has the same IP address:
+   - Either via static IP or DHCP assignment in the router
+
+2. In your router settings, look for **Port Forwarding**, **NAT**, or **Port Sharing**
+
+3. Forward the following ports to your Raspberry Pi:
+
+- TCP Port 80 (HTTP)
+- TCP Port 443 (HTTPS)
+
+<img src={require("./../img/raspberrypi/portforwarding.png").default} alt="portforwarding in router" width="500"/>
+
+### Update OC_DOMAIN
+
+SSH into your Pi and update the domain:
+
+```bash
+cd opencloud-compose
+docker compose down
+nano .env
+```
+
+Edit the `OC_DOMAIN` value:
+
+```env
+OC_DOMAIN=opencloud.webhop.me
+```
+
+<img src={require("./../img/raspberrypi/oc-domain.png").default} alt="change the OC_DOMAIN variable" width="500"/>
+
+Restart Docker:
+
+```bash
+docker compose up
+```
+
+Now your OpenCloud should be reachable via your URL.
+
+<img src={require("./../img/raspberrypi/reachable-via-URL.png").default} alt="reachable-via-URL" width="1920"/>
diff --git a/versioned_docs/version-7.x/admin/getting-started/requirements.md b/versioned_docs/version-7.x/admin/getting-started/requirements.md
new file mode 100644
index 000000000..02d5e84ed
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/getting-started/requirements.md
@@ -0,0 +1,14 @@
+---
+sidebar_position: 1
+id: requirements
+title: Requirements
+description: Runs on anything from a Raspberry Pi to a data center.
+draft: false
+---
+
+| Category                | Details                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| :---------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Server Operating System | <ul><li>Production: Linux</li><li>Testing and development: MacOS or Windows WSL</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| Database                | <ul><li>None (OpenCloud stores files exclusively on the storage to minimize complexity and ensure maximum reliability)</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| Storage                 | <ul><li>The `posix` and `decomposed` storage drivers require:<ul><li>a fully POSIX compliant filesystem <ul><li> local e.g. ext4, XFS, ZFS</li><li>network e.g. CephFS, GPFS, NFS v4.2 or later</li></ul></li><li>atomic read after write consistency for directory metadata (NFS mount option `noac`)</li></ul></li><li>`decomposeds3` additionally requires an S3 bucket</li><li>`posix` requires extended attributes (offloading metadata >1KB into dedicated files)</li></ul>                                                                                                                                                                                                                                                                                 |
+| Hardware requirements   | Minimum (Minimal bare-metal Deployment - Up to 10 Users) <ul><li>eg. Raspberry Pi 3</li><li>1 GHz (Single-core)</li><li>512 MB Ram</li><li>Storage: depends on data usage</li></ul> Medium (Deployment - Up to 1,000 Users) <ul><li>2 GHz (Dual-core)</li><li>8 GB Ram</li><li>Storage: depends on data usage</li></ul> General: <ul><li>Disk Performance (IOPS): Input/output operations per second (IOPS) should be unrestricted for maintaining optimal performance.</li><li>The server requirements vary based on load factors such as requests per second, number of client devices per user, file volume, post-processing tasks, and additional apps like Collabora. Proper sizing depends on these variables and should be adjusted accordingly.</li></ul> |
diff --git a/versioned_docs/version-7.x/admin/index.md b/versioned_docs/version-7.x/admin/index.md
new file mode 100644
index 000000000..567ac18f7
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/index.md
@@ -0,0 +1,42 @@
+---
+sidebar_position: 1
+title: Welcome
+description: Welcome
+draft: false
+---
+
+# Welcome to OpenCloud Admin Docs
+
+Welcome to OpenCloud, your self-hosted file sharing platform: Secure, simple and reliable. This documentation helps you to get started, configure, and maintain OpenCloud.
+
+## Quick start
+
+```bash
+curl -L https://opencloud.eu/install | /bin/bash
+```
+
+## What’s Inside?
+
+- Getting Started – Set up and deploy OpenCloud
+- Configuration – Customize and integrate with existing systems and storage
+- Maintenance – Learn how to update, backup and migrate
+
+## Explore the Admin Docs
+
+- [Getting Started](./getting-started/index.md) - Install and deploy OpenCloud
+- [Configuration](./configuration/index.md) - Tune OpenCloud behavior and integrations
+- [Maintenance](./maintenance/index.md) - Backups, exports, migration, and uninstall
+- [Resources](./resources/index.md) - Troubleshooting, lifecycle, and FAQ
+
+## Documentation Versions
+
+Our documentation is versioned to ensure you always find the right information for your software version.
+
+- Rolling Version: Reflects the current development state. Changes are continuously added, but the documentation may be incomplete, as new features might not yet be documented. Ideal if you are using a pre-release or development build.
+- Stable Release Versions: Documentation for officially released versions — frozen, reviewed, and unchanged since publication.
+
+You can switch between the Rolling version and specific Release versions using the version menu in the top right corner.
+
+## Need Help?
+
+Check our [GitHub Discussion](https://github.com/orgs/opencloud-eu/discussions), or [Matrix Channel](https://matrix.to/#/#opencloud:matrix.org). Let’s get started!
diff --git a/versioned_docs/version-7.x/admin/maintenance/_category_.json b/versioned_docs/version-7.x/admin/maintenance/_category_.json
new file mode 100644
index 000000000..bdb37be91
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/maintenance/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Maintenance",
+  "position": 6
+}
diff --git a/versioned_docs/version-7.x/admin/maintenance/backup.md b/versioned_docs/version-7.x/admin/maintenance/backup.md
new file mode 100644
index 000000000..71bfa6ca0
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/maintenance/backup.md
@@ -0,0 +1,91 @@
+---
+sidebar_position: 2
+id: backup
+title: Backup
+description: Backup
+draft: false
+---
+
+# Backup
+
+Regular backups are essential to ensure that your OpenCloud instance can be restored in case of issues
+
+## General considerations
+
+### Storage Options
+
+OpenCloud supports two different storage setups:
+
+- Pure POSIX Setup: All data (configuration, blobs, and metadata) is stored on a POSIX-compliant filesystem.
+
+- Distributed Setup: Blobs are stored on an S3-compliant storage, while configuration and metadata remain on a POSIX-compliant filesystem
+
+To determine which filesystems are supported, see: Filesystems and Shared Storage
+
+## Backup strategies
+
+### Consistent Backup Requirement
+
+To create a consistent backup, the OpenCloud instance must be stopped before starting the backup process. After the backup is complete, the instance can be restarted
+
+There are two recommended approaches:
+
+- Snapshot-based backup (recommended)
+  - If your storage system supports snapshots, creating a backup only takes a few seconds
+
+  - Snapshots should be copied to secondary storage or used by backup software for additional security
+
+- Backup software approach
+
+- If snapshots are not available, you can use any backup software of your choice
+- For more details on data locations, refer to the Default Paths documentation
+
+## Required backup components
+
+- Configuration data
+
+- System data (shares the root path with metadata if not defined separately)
+
+- Metadata (varies depending on the storage setup)
+
+- Blobs (stored with metadata on POSIX or separately on S3)
+
+- ⚠️ If the search index is not backed up, it must be recreated after restoration.
+
+- Additionally, consider backing up:
+
+- The OpenCloud binary or container used
+
+- The configuration files
+
+- This ensures compatibility when restoring and prevents issues caused by software version mismatches
+
+## Pure POSIX setup
+
+If all data (configuration, blobs, and metadata) is stored on a POSIX-compliant filesystem
+
+- Stop the OpenCloud instance
+
+- Create a backup of all data sets
+
+- If everything is on one filesystem, this is straightforward
+
+- If separate filesystems are used for configuration and blobs/metadata, back up each one individually
+
+- Restart the OpenCloud instance after the backup is complete
+
+## Distributed setup
+
+If blobs are stored on S3, while configuration and metadata remain on a POSIX-compliant filesystem
+
+- Stop the OpenCloud instance
+
+- Back up the configuration and metadata
+
+- Back up the S3 bucket according to the guidelines of your S3 provider
+
+- Restart the OpenCloud instance after the backup is complete
+
+:::note
+With these backup strategies, you can ensure that your OpenCloud instance remains secure and restorable in case of issues
+:::
diff --git a/versioned_docs/version-7.x/admin/maintenance/dataexport.md b/versioned_docs/version-7.x/admin/maintenance/dataexport.md
new file mode 100644
index 000000000..21081de57
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/maintenance/dataexport.md
@@ -0,0 +1,29 @@
+---
+sidebar_position: 5
+id: dataexport
+title: Data Export
+description: Information about data export.
+draft: false
+---
+
+# Data Export
+
+## Files
+
+OpenCloud stores files by default in the file system under the path `/var/lib/opencloud/`. Any other path that is local to the server instance running the OpenCloud backend can be configured as alternative path using the environment variable `OC_BASE_DATA_PATH`.
+
+Files and folders are stored in a folder structure underneath that base path in folder `data/storage/users/`.
+
+Files are by default stored in the original format and not encrypted.
+
+## Metadata
+
+File metadata is stored in the file system with every file. It is either in the extended file attributes (user namespace) or in a separate metadata file. That file is in the [MessagePack](https://msgpack.org) format and can be read with the CLI tools for that file type.
+
+## Configuration
+
+Configuration files are written as yaml files by default under `$HOME/.config/OpenCloud`.
+
+## Other
+
+Other, non-file-related metadata such as links is also stored under the general data base path, in JSON format.
diff --git a/versioned_docs/version-7.x/admin/maintenance/img/generate-pass-nc.png b/versioned_docs/version-7.x/admin/maintenance/img/generate-pass-nc.png
new file mode 100644
index 000000000..e9ef59940
Binary files /dev/null and b/versioned_docs/version-7.x/admin/maintenance/img/generate-pass-nc.png differ
diff --git a/versioned_docs/version-7.x/admin/maintenance/img/init-diff.png b/versioned_docs/version-7.x/admin/maintenance/img/init-diff.png
new file mode 100644
index 000000000..94b6f0a05
Binary files /dev/null and b/versioned_docs/version-7.x/admin/maintenance/img/init-diff.png differ
diff --git a/versioned_docs/version-7.x/admin/maintenance/index.md b/versioned_docs/version-7.x/admin/maintenance/index.md
new file mode 100644
index 000000000..368acdd30
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/maintenance/index.md
@@ -0,0 +1,18 @@
+---
+sidebar_position: 0
+id: admin-maintenance
+title: Maintenance
+description: Overview of OpenCloud maintenance tasks
+---
+
+# Maintenance
+
+Use these guides to keep your OpenCloud installation updated, backed up, and manageable over time.
+
+## In this section
+
+- [Upgrade](./upgrade/index.md)
+- [Backup](./backup.md)
+- [Migrate](./migrate.md)
+- [Uninstall](./uninstall.md)
+- [Data Export](./dataexport.md)
diff --git a/versioned_docs/version-7.x/admin/maintenance/migrate.md b/versioned_docs/version-7.x/admin/maintenance/migrate.md
new file mode 100644
index 000000000..7b9fe2fe3
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/maintenance/migrate.md
@@ -0,0 +1,229 @@
+---
+sidebar_position: 3
+id: migrate
+title: Migrate
+description: Guide to migrating data using rclone.
+draft: false
+---
+
+import Tabs from '@theme/Tabs'
+import TabItem from '@theme/TabItem'
+
+# Migrate
+
+Migrate Personal Space Data to OpenCloud Using rclone
+
+This guide will help you migrate personal space data from `NextCloud` and `oCIS` to `OpenCloud` using `rclone`. Follow these steps carefully to ensure a smooth migration!
+
+## Generate users token using CLI or API
+
+<Tabs>
+<TabItem value="opencloud" label="OpenCloud">
+
+## Run OpenCloud with the following configuration
+
+Modify `.env` file:
+
+```bash
+START_ADDITIONAL_SERVICES="auth-app"
+```
+
+Enable `auth-app` service:
+
+```bash
+PROXY_ENABLE_APP_AUTH="true"
+```
+
+### Generate user token using CLI
+
+Access the OpenCloud container:
+
+```bash
+docker exec -it opencloud-compose-opencloud-1 sh
+```
+
+Generate an authentication token for a user (e.g., `alan`) with expiration (`h`, `m`, `s`):
+
+```bash
+opencloud auth-app create --user-name=alan --expiration=72h
+```
+
+## Generate user token using API
+
+Requires additional configuration! Start the server with:
+
+```bash
+AUTH_APP_ENABLE_IMPERSONATION=true
+```
+
+Then generate a token via API:
+
+```bash
+curl -vk -XPOST 'https://opencloud_url/auth-app/tokens?expiry=72h&userName=alan' -uadmin:admin
+```
+
+</TabItem>
+
+<TabItem value="ocis" label="oCIS">
+
+### Run oCIS with the following configuration
+
+Modify `.env` file:
+
+```bash
+START_ADDITIONAL_SERVICES="auth-app"
+```
+
+Enable `auth-app` service:
+
+```bash
+PROXY_ENABLE_APP_AUTH="true"
+```
+
+## Generate user token using CLI
+
+Access the oCIS container:
+
+```bash
+docker exec -it ocis_full-ocis-1 sh
+```
+
+Generate an authentication token for a user (e.g., `einstein`) with expiration (`h`, `m`, `s`):
+
+```bash
+ocis auth-app create --user-name=einstein --expiration=72h
+```
+
+## Generate user token using API
+
+Requires additional configuration! Start the server with:
+
+```bash
+AUTH_APP_ENABLE_IMPERSONATION=true
+```
+
+Then generate a token via API:
+
+```bash
+curl -vk -XPOST 'https://ocis_url/auth-app/tokens?expiry=72h&userName=einstein' -uadmin:admin
+```
+
+</TabItem>
+
+<TabItem value="nc" label="Nextcloud">
+
+### Go to `Settings` → `Security`
+
+Create a new App Password
+
+![Generate App Password](./img/generate-pass-nc.png)
+
+</TabItem>
+</Tabs>
+
+## Install rclone
+
+Download and install rclone by following the official guide: [rclone.org/install](https://rclone.org/install/)
+
+## Encrypt Authentication Tokens
+
+```bash
+rclone obscure <token>
+```
+
+## Create the rclone Configuration
+
+Edit the rclone configuration file:
+
+```bash
+nano ~/.config/rclone/rclone.conf
+```
+
+- Example Configuration
+
+```bash
+[opencloud-admin]
+type = webdav
+url = https://opencloud_url/remote.php/webdav
+vendor = opencloud
+owncloud_exclude_shares = true
+user = admin
+pass = sQOM4mn2DdR9ihRGkyAMcd50W6mniaSqSfx2qVOdBJs
+description = opencloud-admin
+
+[opencloud-alan]
+type = webdav
+url = https://opencloud_url/remote.php/webdav
+vendor = opencloud
+owncloud_exclude_shares = true
+user = alan
+pass = sQOM4mn2DdR9ihRGkyAMcd50W6mniaSqSfx2qVOdBJs
+description = opencloud-alan
+
+[ocis-admin]
+type = webdav
+url = https://ocis_url/remote.php/webdav
+vendor = ocis
+owncloud_exclude_shares = true
+user = admin
+pass = Sav5354nRTgBHyItQeCZp9tCBidX2BxbuMx_dDLwxqs
+description = ocis-admin
+
+[ocis-einstein]
+type = webdav
+url = https://ocis_url/remote.php/webdav
+vendor = ocis-einstein
+owncloud_exclude_shares = true
+user = einstein
+pass = dcYsf3PNvBxaIi7MMq-bqg74KMWWWS8p3uFT-WD17SA
+description = ocis-einstein
+
+[nc-admin]
+type = webdav
+url = http://nc_url/remote.php/webdav
+vendor = nc
+owncloud_exclude_shares = true
+user = admin
+pass = IBSkhC1wCDdS2Gt9iBV-C9IqlGek
+description = nc-admin
+
+[nc-bob]
+type = webdav
+url = http://localhost:8080/remote.php/webdav
+vendor = nc-bob
+owncloud_exclude_shares = true
+user = bob
+pass = ufOK3zPDjR4meEwwy3cWUVA18Lf8TpubBRyPL5m9KC508PkMiEVAXTxg6olu
+description = nc-bob
+
+```
+
+## Copy Data to OpenCloud
+
+Use `rclone copy` to transfer data from `oCIS` and `Nextcloud` to `OpenCloud`:
+
+```bash
+rclone copy ocis-admin:/ opencloud-admin:/ --no-check-certificate -P  # Copy oCIS admin personal space to OpenCloud admin space
+rclone copy ocis-einstein:/ opencloud-alan:/ --no-check-certificate -P  # Copy oCIS bob's personal space to OpenCloud admin space
+rclone copy nc-bob:/ opencloud-alan:/ --no-check-certificate -P  # Copy Nextcloud admin personal space to OpenCloud admin space
+
+```
+
+## Migration Results and Limitations
+
+Congratulations! You have successfully migrated personal space data to OpenCloud!
+
+- Successfully Migrated
+  - Personal space files
+
+- Not Migrated
+  - Shared files
+  - Public links
+  - Project spaces
+  - Trash-bin contents
+  - File versions
+  - Metadata
+
+## Security Step: Delete Tokens
+
+Once the migration is complete, please delete tokens to prevent unauthorized access!
diff --git a/versioned_docs/version-7.x/admin/maintenance/uninstall.md b/versioned_docs/version-7.x/admin/maintenance/uninstall.md
new file mode 100644
index 000000000..d77503808
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/maintenance/uninstall.md
@@ -0,0 +1,85 @@
+---
+sidebar_position: 4
+id: uninstall
+title: Uninstall
+description: Guide to uninstall OpenCloud.
+draft: false
+---
+
+# Uninstall OpenCloud with Docker Compose
+
+:::warning
+This guide will completely remove all OpenCloud data. Make sure to back up any important files before proceeding.
+:::
+
+## Stop and Remove Docker Containers
+
+Navigate to your `opencloud-compose` directory (where your `docker-compose.yml` file is located), then run:
+
+```bash
+docker compose down
+```
+
+To also remove unnamed volumes and orphan containers:
+
+```bash
+docker compose down --volumes --remove-orphans
+```
+
+## Remove Docker Volumes
+
+To check your existing volumes:
+
+```bash
+docker volume ls
+```
+
+Typical OpenCloud volumes may include:
+
+`opencloud_compose_opencloud-data`
+
+`opencloud_compose_opencloud-config`
+
+To delete specific volumes:
+
+```bash
+docker volume rm opencloud_compose_opencloud-data opencloud_compose_opencloud-config
+```
+
+Or to clean up all unused volumes (be careful!):
+
+```bash
+docker volume prune
+```
+
+## Delete Mounted Directories (if used)
+
+If your .env referenced local folders such as /mnt/opencloud/data, you should delete those manually:
+
+```bash
+sudo rm -rf /mnt/opencloud/data
+sudo rm -rf /mnt/opencloud/config
+```
+
+Adjust the paths to match your setup.
+
+## Remove the Compose Project Folder (Optional)
+
+If you want to delete the entire project directory:
+
+```bash
+cd ..
+rm -rf opencloud-compose
+```
+
+## Result
+
+After completing these steps, OpenCloud is fully removed, including:
+
+- All Docker containers
+
+- All persistent volumes
+
+- Any local folders and mounts
+
+- Optional project directory
diff --git a/versioned_docs/version-7.x/admin/maintenance/upgrade/_category_.json b/versioned_docs/version-7.x/admin/maintenance/upgrade/_category_.json
new file mode 100644
index 000000000..025a68228
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/maintenance/upgrade/_category_.json
@@ -0,0 +1,8 @@
+{
+  "label": "Upgrade",
+  "position": 1,
+  "link": {
+    "type": "doc",
+    "id": "upgrade"
+  }
+}
diff --git a/versioned_docs/version-7.x/admin/maintenance/upgrade/index.md b/versioned_docs/version-7.x/admin/maintenance/upgrade/index.md
new file mode 100644
index 000000000..b49c20dad
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/maintenance/upgrade/index.md
@@ -0,0 +1,18 @@
+---
+sidebar_position: 0
+id: upgrade
+title: Upgrade
+description: Overview of OpenCloud upgrade guides and release notes
+draft: false
+---
+
+# Upgrade
+
+This section collects the guides you need when upgrading OpenCloud.
+
+## Guides
+
+- [Standard Upgrade Guide](./upgrade.md)
+- [Upgrade 7.x.x](./upgrade-7.x.x.md)
+- [Upgrade 4.0.x](./upgrade-4.0.0.md)
+- [Release notes](./release-notes.md)
diff --git a/versioned_docs/version-7.x/admin/maintenance/upgrade/release-notes.md b/versioned_docs/version-7.x/admin/maintenance/upgrade/release-notes.md
new file mode 100644
index 000000000..92293d2e8
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/maintenance/upgrade/release-notes.md
@@ -0,0 +1,79 @@
+---
+sidebar_position: 40
+id: release-notes
+title: Release Notes
+description: Release Notes
+draft: false
+---
+
+# Release Notes: Migration from v5.x.x to v6.0.0
+
+- Version: 6.0.0
+- Type: Major Release (Breaking Change in Search Index)
+- [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v6.0.0)
+
+## Who Is Affected?
+
+Users who use the **OpenSearch backend** for search functionality.
+
+## Key Changes
+
+The OpenSearch index has been redesigned with the following improvements:
+
+- Fixes for persisting and querying favorite information
+- Fast Vector Highlighter support — significantly faster and without the character limits of the previous default highlighter
+
+:::warning breaking change
+This is an incompatible change. Users of the OpenSearch backend will have to drop their old index and rebuild it using:
+
+```bash
+opencloud search index --all-spaces
+```
+
+:::
+
+# Release Notes: Migration from v4.x.x to v5.0.0
+
+- Version: 5.0.0
+- Type: Major Release (Breaking Change in Service Architecture)
+- [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v5.0.0)
+
+## Who Is Affected?
+
+If you use the official Docker Compose setup, no migration is typically required.
+
+## Key Changes
+
+The OCDAV is no longer initialized as its own service, it was moved from the backend services into the frontend service
+
+:::compatibility note
+Legacy env variable names (OCDAV\_\*) still work. They just need to be set on the frontend service now
+:::
+
+# Release Notes: Migration from v2.x.x to v3.0.0
+
+- Version: 3.0.0
+- Type: Major Release (Breaking Changes in the GraphAPI)
+- [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v3.0.0)
+
+## Who Is Affected?
+
+This release introduces a breaking change in the GraphAPI.  
+If you are using OpenCloud only through official clients (Web, Desktop, or Mobile), no migration is needed.
+
+If you're using any other software that utilizes the GraphAPI, that software might need to be adjusted to follow the new behavior of the GraphAPI.
+
+## Key Changes
+
+The following endpoints of the GraphAPI were changed in a way that is not backwards compatible with the previous releases:
+
+```http
+GET /v1.0/me/drives/
+GET /v1.0/drives/
+GET /v1beta1/drives/
+GET /v1beta1/me/drives/
+```
+
+:::note
+Due to performance optimizations, these endpoints no longer automatically expand all permissions on the drives root items. If needed, the permissions can be explicitly requested via the appropriate $expand query option.
+:::
diff --git a/versioned_docs/version-7.x/admin/maintenance/upgrade/upgrade-4.0.0.md b/versioned_docs/version-7.x/admin/maintenance/upgrade/upgrade-4.0.0.md
new file mode 100644
index 000000000..c5631cfb6
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/maintenance/upgrade/upgrade-4.0.0.md
@@ -0,0 +1,242 @@
+---
+sidebar_position: 30
+id: upgrade-4.0.x
+title: Upgrade 4.0.x
+description: Upgrading to 4.0.x
+draft: false
+---
+
+import Tabs from '@theme/Tabs'
+import TabItem from '@theme/TabItem'
+
+# Upgrading to OpenCloud 4.0.x
+
+This guide explains how to upgrade from the previous stable opencloud_full Compose setup to the new
+[opencloud-compose](https://github.com/opencloud-eu/opencloud-compose.git) repository structure.  
+It covers both types of persistent storage used in earlier deployments:
+
+- Bind mounts: host directories mapped into containers.
+- Docker named volumes: volumes managed directly by Docker.
+
+Following this guide, you can safely migrate to the stable v4.0.x release of OpenCloud.
+
+## Before You Begin
+
+- Determine Your Deployment Type: This guide covers two common setups:
+  - Bind Mounts: Config and data are stored in directories on the host machine (e.g., `/mnt/opencloud/config`).
+  - Docker Named Volumes: Config and data are managed by Docker. You will need your `COMPOSE_PROJECT_NAME` to access them.
+- Check Paths: If you are using bind mounts, ensure you know the correct paths on your host system. You can find them by inspecting your current container's `docker run` command or `docker-compose.yml` file (look for `volumes:` sections that map to host paths). For a running container, `docker inspect opencloud_full-opencloud-1` also exposes this information in the `Mounts` section.
+
+## Backup Config and Data
+
+:::important
+Important: Always create a backup before upgrading to prevent data loss.  
+We strongly recommend following the [backup documentation](../backup.md)
+and creating copies of your configuration and data directories.
+:::
+
+<Tabs> <TabItem value="bind-mounts" label="Using Bind Mounts">
+If your config and data are stored in host directories (bind mounts), create a direct copy of these folders.
+
+### Example (adjust paths to match your setup)
+
+```bash
+cp -a /mnt/opencloud/config /mnt/opencloud/config-backup
+cp -a /mnt/opencloud/data /mnt/opencloud/data-backup
+```
+
+</TabItem>
+
+<TabItem value="named-volumes" label="Using Named Volumes">
+
+### Create backup directory
+
+```bash
+mkdir -p ~/opencloud-backups
+```
+
+### Backup config and data
+
+```bash
+docker cp opencloud_full-opencloud-1:/var/lib/opencloud ~/opencloud-backups/data-backup
+docker cp opencloud_full-opencloud-1:/etc/opencloud ~/opencloud-backups/config-backup
+```
+
+</TabItem>
+
+</Tabs>
+
+## Stop OpenCloud
+
+First, gracefully stop your currently running OpenCloud instance:
+
+<Tabs>
+
+<TabItem value="docker" label="docker">
+
+```bash
+docker stop opencloud
+```
+
+</TabItem>
+
+<TabItem value="docker compose" label="docker compose">
+
+```bash
+docker compose stop
+```
+
+</TabItem>
+
+</Tabs>
+
+## Pull the 4.0.x Production Release Image
+
+```bash
+docker pull opencloudeu/opencloud:4.0.x
+```
+
+## Update Deployment Configuration
+
+<Tabs>
+
+<TabItem value="docker compose" label="docker compose">
+
+### Clone the opencloud-compose Repository
+
+Clone the official opencloud-compose repository onto your server:
+
+```bash
+git clone https://github.com/opencloud-eu/opencloud-compose.git
+cd opencloud-compose
+```
+
+### Migrate Environment Variables
+
+Transfer your existing environment variables to the new opencloud-compose structure. Refer to the [Docker Compose configuration documentation](../../getting-started/container/docker-compose/docker-compose-base.md) for detailed instructions.
+
+</TabItem>
+
+</Tabs>
+
+## Verify Configuration Changes
+
+Go inside the container:
+
+If your config is stored in host directories (change `<your-home-directory>` to your home directory. In our example it is `/mnt` ):
+
+```bash
+docker run --rm -it --entrypoint /bin/sh -v <your-home-directory>/opencloud/opencloud-config:/etc/opencloud opencloudeu/opencloud:4.0.x
+```
+
+or, if you use Docker Named Volumes (replace `<your-named-volume>`with your volume name. In our example it is `opencloud_full_opencloud-config`):
+
+```bash
+docker run --rm -it --entrypoint /bin/sh \
+  -v <your-named-volume>:/etc/opencloud \
+  opencloudeu/opencloud:4.0.x
+```
+
+Check for configuration changes:
+
+```bash
+opencloud init --diff
+```
+
+Example output:
+
+```bash
+opencloud init --diff
+Do you want to configure OpenCloud with certificate checking disabled?
+ This is not recommended for public instances! [yes | no = default] yes
+running in diff mode
+diff -u /etc/opencloud/opencloud.yaml /etc/opencloud/opencloud.yaml.tmp
+--- /etc/opencloud/opencloud.yaml
++++ /etc/opencloud/opencloud.yaml.tmp
+@@ -3,6 +3,7 @@
+ machine_auth_api_key: k55Y7i3Djeeu4aPPNzM67Q39rf3ZHz^9
+ system_user_api_key: GeTXN@Mj7-4n8Yhuwb&#oq8Gb1hF7Q%^
+ transfer_secret: ANy#T5.IvknED9-Ud39+YmlXzN^TdaKi
++url_signing_secret: zB#FtAYid24Z^DkuBoTllnId=igo!tCO
+ system_user_id: 8cc36d34-cd87-4434-b9e2-726e5553609c
+ admin_user_id: 34a73600-a02c-4064-8aec-341cd1865a71
+ graph:
+
+diff written to /etc/opencloud/opencloud.config.patch
+```
+
+Apply any necessary changes to `/etc/opencloud/opencloud.yaml` based on the diff output. In this example, add `url_signing_secret` to your `opencloud.yaml`.
+
+## Start OpenCloud (v4.0.x)
+
+<Tabs>
+
+<TabItem value="docker" label="docker">
+
+```bash
+docker run \
+    --name opencloud \
+    --rm \
+    -d \
+    -p 9200:9200 \
+    -v $HOME/opencloud/opencloud-config:/etc/opencloud \
+    -v $HOME/opencloud/opencloud-data:/var/lib/opencloud \
+    -e OC_INSECURE=true \
+    -e PROXY_HTTP_ADDR=0.0.0.0:9200 \
+    -e OC_URL=https://localhost:9200 \
+    opencloudeu/opencloud:4.0.x
+```
+
+</TabItem>
+
+<TabItem value="docker compose" label="docker compose">
+
+## Important Note for Existing Deployments
+
+If you previously deployed OpenCloud using the project name `opencloud_full` (our earlier example) and are now switching to the official [opencloud-compose](https://github.com/opencloud-eu/opencloud-compose) repository, you may need to specify the original project name to ensure:
+
+- Network compatibility - for services like S3 that need to be on the same network
+- Volume persistence - to access existing Docker volumes
+
+Run the command with your original project name:
+
+```bash
+docker compose -p opencloud_full up -d
+```
+
+Alternatively, set the project name permanently in the .env file:
+
+```bash
+COMPOSE_PROJECT_NAME=opencloud_full
+```
+
+Then use the standard command:
+
+```bash
+docker compose up -d
+```
+
+</TabItem>
+
+</Tabs>
+
+## Verification
+
+Your OpenCloud instance should now be running on `v4.0.x`.
+
+### Essential Checks
+
+- User Accounts — Confirm all users can log in successfully
+- Shared Folders — Verify shared folder permissions and access
+- Public Links — Test that public links remain functional
+- Data Integrity — Ensure all files and folders are accessible
+- Service Health — Check logs for any errors or warnings
+
+## Troubleshooting
+
+If you encounter issues during or after the upgrade:
+
+1. Review the logs for error messages
+2. Consult the [troubleshooting guide](../../resources/common-issues)
+3. Restore from backup if necessary
+4. Contact support or open an issue on [GitHub](https://github.com/opencloud-eu/opencloud/issues)
diff --git a/versioned_docs/version-7.x/admin/maintenance/upgrade/upgrade-7.x.x.md b/versioned_docs/version-7.x/admin/maintenance/upgrade/upgrade-7.x.x.md
new file mode 100644
index 000000000..0e43df85d
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/maintenance/upgrade/upgrade-7.x.x.md
@@ -0,0 +1,377 @@
+---
+sidebar_position: 20
+id: upgrade-7.x.x
+title: Upgrade 7.x.x
+description: Upgrading to OpenCloud 7.x.x
+draft: false
+---
+
+import Tabs from '@theme/Tabs'
+import TabItem from '@theme/TabItem'
+
+# Upgrading to OpenCloud 7.x.x
+
+This guide describes how to upgrade an existing OpenCloud deployment to OpenCloud 7.x.x.
+
+The guide applies to upgrades from:
+
+- OpenCloud 6.x rolling
+- OpenCloud 4.0.x stable
+
+It covers the required configuration migration, optional OpenSearch index rebuild, and web extension updates introduced with OpenCloud 7.x.x.
+
+## Before You Start
+
+- Make sure your current deployment is running on OpenCloud 6.x (rolling) or OpenCloud 4.0.x (stable).
+- Create a complete backup of your configuration and data.
+- Make sure you have access to your current `opencloud.yaml`.
+- Verify that your current deployment is healthy before upgrading.
+- Review the OpenCloud 7.x.x [release notes](https://github.com/opencloud-eu/opencloud/releases) before starting the upgrade.
+
+## Back Up Configuration and Data
+
+<Tabs>
+  <TabItem value="bind-mounts" label="Using Bind Mounts">
+
+If your configuration and data are stored in directories on the host, create a copy of these directories.
+
+Example:
+
+```bash
+cp -a /mnt/opencloud/config /mnt/opencloud/config-backup
+cp -a /mnt/opencloud/data /mnt/opencloud/data-backup
+```
+
+Replace the paths with the directories used by your deployment.
+
+  </TabItem>
+
+  <TabItem value="named-volumes" label="Using Named Volumes">
+
+Create a backup directory and copy the configuration and data from the OpenCloud container.
+
+```bash
+mkdir -p ~/opencloud-backups
+docker cp opencloud-compose-opencloud-1:/etc/opencloud ~/opencloud-backups/config-backup
+docker cp opencloud-compose-opencloud-1:/var/lib/opencloud ~/opencloud-backups/data-backup
+```
+
+Replace `opencloud-compose-opencloud-1` with the name of your OpenCloud container if it differs.
+
+  </TabItem>
+</Tabs>
+
+## Update the `opencloud-compose` Checkout
+
+If you use the `opencloud-compose` repository, update your local copy of the repository.
+
+```bash
+cd /opencloud-compose
+git pull
+```
+
+Skip this step if you run OpenCloud with plain Docker.
+
+## Stop OpenCloud
+
+Stop the currently running OpenCloud instance.
+
+<Tabs>
+  <TabItem value="docker-compose" label="Docker Compose">
+
+```bash
+docker compose stop
+```
+
+  </TabItem>
+
+  <TabItem value="docker" label="Docker">
+
+```bash
+docker stop opencloud
+```
+
+  </TabItem>
+</Tabs>
+
+## Pull the OpenCloud 7.x.x Image
+
+Pull the OpenCloud 7.x.x image.
+
+Replace `7.x.x` with the exact image tag for the version you want to install. Available tags are listed on [Docker Hub](https://hub.docker.com/u/opencloudeu).
+
+```bash
+docker pull opencloudeu/opencloud:7.x.x
+```
+
+## Apply the Configuration Migration
+
+OpenCloud 7.x.x includes a breaking configuration change that must be applied before starting the upgraded instance.
+
+### Open a Temporary OpenCloud Container
+
+Open a shell in a temporary OpenCloud 7.x.x container and mount your OpenCloud configuration directory or configuration volume to `/etc/opencloud`.
+
+<Tabs>
+  <TabItem value="named-volumes" label="Using Named Volumes">
+
+```bash
+docker run --rm -it --entrypoint /bin/sh -v "<opencloud-config-volume>:/etc/opencloud" opencloudeu/opencloud:7.x.x
+```
+
+Replace `<opencloud-config-volume>` with the Docker volume or bind mount that contains your OpenCloud configuration.
+
+  </TabItem>
+
+  <TabItem value="bind-mounts" label="Using Bind Mounts">
+
+```bash
+docker run --rm -it --entrypoint /bin/sh -v "<path-to-your-config-directory>:/etc/opencloud" opencloudeu/opencloud:7.x.x
+```
+
+Replace `<path-to-your-config-directory>` with the host directory that contains your `opencloud.yaml`.
+
+  </TabItem>
+</Tabs>
+
+### Generate the Configuration Diff
+
+Inside the temporary container, run:
+
+```bash
+opencloud init --diff
+```
+
+Example output:
+
+```diff
+diff -u /etc/opencloud/opencloud.yaml /etc/opencloud/opencloud.yaml.tmp
+--- /etc/opencloud/opencloud.yaml
++++ /etc/opencloud/opencloud.yaml.tmp
+@@ -90,6 +90,9 @@
+ sharing:
+   events:
+     tls_insecure: false
++service_account:
++  service_account_id: 00000000-0000-0000-0000-000000000000
++  service_account_secret: example-service-account-secret
+ storage_users:
+   events:
+     tls_insecure: false
+
+diff written to /etc/opencloud/opencloud.config.patch
+```
+
+The command creates the following patch file:
+
+```bash
+/etc/opencloud/opencloud.config.patch
+```
+
+### Apply the Configuration Patch
+
+Change to the configuration directory:
+
+```bash
+cd /etc/opencloud
+```
+
+Verify that the patch file was created:
+
+```bash
+ls
+```
+
+Example output:
+
+```bash
+banned-password-list.txt
+csp.yaml
+opencloud.config.patch
+opencloud.yaml
+opencloud.yaml.2026-05-19-15-45-44.backup
+```
+
+Test the patch before applying it:
+
+```bash
+patch --dry-run opencloud.yaml < opencloud.config.patch
+```
+
+Expected output:
+
+```bash
+checking file opencloud.yaml
+```
+
+Apply the patch:
+
+```bash
+patch opencloud.yaml < opencloud.config.patch
+```
+
+Expected output:
+
+```bash
+patching file opencloud.yaml
+```
+
+Verify that the following configuration entries exist in `opencloud.yaml`:
+
+```yaml
+service_account:
+  service_account_id: 00000000-0000-0000-0000-000000000000
+  service_account_secret: example-service-account-secret
+```
+
+### Exit the Temporary Container
+
+Exit the temporary container after applying the configuration patch.
+
+```bash
+exit
+```
+
+## Start OpenCloud
+
+Start OpenCloud with the upgraded image.
+
+<Tabs>
+  <TabItem value="docker-compose" label="Docker Compose">
+
+```bash
+docker compose up -d
+```
+
+  </TabItem>
+
+  <TabItem value="docker" label="Docker">
+
+```bash
+docker start opencloud
+```
+
+  </TabItem>
+</Tabs>
+
+### ⏳ First Startup After Upgrading to OpenCloud 7.x.x
+
+After upgrading to OpenCloud 7.x.x, the first startup may take several minutes before all Spaces become fully available.
+
+During this period, some Space-related functionality is temporarily restricted:
+
+- Space member lists may be incomplete or incorrect.
+- Space memberships cannot be modified.
+- Creating or deleting Spaces is not possible.
+- Share-related operations may be unavailable until the migration has completed.
+
+#### Background
+
+OpenCloud 7.x.x introduced a new backend mechanism for managing Space memberships. When upgrading from an earlier release, the `sharing` service automatically migrates existing memberships to the new format.
+
+Depending on the number of Spaces and members in your installation, this process may take several minutes to complete.
+
+#### Monitoring Migration Progress
+
+To monitor the migration progress, configure the sharing service log level to `info` before starting the upgrade:
+
+```bash
+OC_LOG_LEVEL=info
+```
+
+or
+
+```bash
+SHARING_LOG_LEVEL=info
+```
+
+With the log level set to `info`, the sharing service writes migration progress information to the logs while the migration is running.
+
+#### Migration Completed
+
+Once the migration has finished successfully, the sharing service writes a completion message to the logs indicating that the migration has been completed.
+
+> **Note:** Migration progress and completion messages are only available when the sharing service log level is configured to `info`.
+
+After the completion message appears in the logs, all Space functionality, including member management, sharing operations, and Space creation or deletion, is available again.
+
+#### Required Configuration Changes
+
+The upgrade also requires a configuration change for the `sharing` service.
+
+Please follow the instructions in the Upgrade Guide and apply the required configuration updates before starting the upgraded version of OpenCloud.
+
+## Rebuild the OpenSearch Index
+
+:::note
+
+This step is only required for instances that use OpenSearch.
+
+:::
+
+OpenCloud 7.x.x introduces a new OpenSearch index structure.
+
+Reference: [OpenSearch Index PR](https://github.com/opencloud-eu/opencloud/pull/2514)
+
+After upgrading, rebuild the search index.
+
+<Tabs>
+  <TabItem value="docker" label="Docker">
+
+```bash
+docker exec -it opencloud opencloud search index --all-spaces
+```
+
+  </TabItem>
+
+  <TabItem value="docker-compose" label="Docker Compose">
+
+```bash
+docker compose exec opencloud opencloud search index --all-spaces
+```
+
+  </TabItem>
+</Tabs>
+
+The indexing process can take longer on larger installations.
+
+## Update Web Extensions
+
+OpenCloud 7.x.x introduces breaking changes in the web client architecture.
+
+Older web extension versions are no longer compatible with OpenCloud 7.x.x and must be updated.
+
+New extension versions are available from:
+
+- The App Store inside the OpenCloud web interface
+- [OpenCloud Web Extensions on GitHub](https://github.com/opencloud-eu/web-extensions/releases)
+
+Download the latest extension versions and follow the [web applications installation guide](../../configuration/web-applications.md).
+
+## Verify the Upgrade
+
+After starting OpenCloud, verify that the instance works as expected.
+
+- Users can log in.
+- Existing shares are still available.
+- Public links work as expected.
+- Project spaces show the correct members and permissions.
+- Search returns expected results after rebuilding the OpenSearch index.
+- The container logs do not show upgrade-related errors.
+
+## Troubleshooting
+
+If issues occur during or after the upgrade:
+
+- Review the OpenCloud container logs.
+- Verify the generated changes in `opencloud.yaml`.
+- Re-run the configuration diff if required.
+- Restore the backup if the instance cannot be recovered.
+- Check the troubleshooting documentation.
+- Open an issue on GitHub if the issue persists.
+
+## Useful Resources
+
+- [OpenCloud Troubleshooting Guide](../../resources/common-issues.md)
+- [OpenCloud GitHub Issues](https://github.com/opencloud-eu/opencloud/issues)
+- [OpenCloud Web Extensions Releases](https://github.com/opencloud-eu/web-extensions/releases)
diff --git a/versioned_docs/version-7.x/admin/maintenance/upgrade/upgrade.md b/versioned_docs/version-7.x/admin/maintenance/upgrade/upgrade.md
new file mode 100644
index 000000000..342481e6b
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/maintenance/upgrade/upgrade.md
@@ -0,0 +1,276 @@
+---
+sidebar_position: 10
+id: upgrade-guide
+title: Standard Upgrade Guide
+description: Standard guide for upgrading OpenCloud
+draft: false
+slug: upgrade-guide
+---
+
+# Standard Upgrade Guide
+
+import Tabs from '@theme/Tabs'
+import TabItem from '@theme/TabItem'
+
+This guide provides the standard steps to upgrade OpenCloud for both [docker](../../getting-started/container/docker.md) and [docker compose](../../getting-started/container/docker-compose/docker-compose-base.md)
+
+## Stop OpenCloud
+
+Stop the currently running OpenCloud instance:
+
+<Tabs groupId="deployment">
+  <TabItem value="docker" label="docker">
+    ```Shell
+    docker stop opencloud
+    ```
+  </TabItem>
+  <TabItem value="docker-compose" label="docker compose">
+    ```Shell
+    docker compose stop
+    ```
+  </TabItem>
+</Tabs>
+
+## Back Up Configuration and Data
+
+<Tabs>
+  <TabItem value="bind-mounts" label="Using Bind Mounts">
+
+If your configuration and data are stored in directories on the host, create a copy of these directories.
+
+Example:
+
+```bash
+cp -a /mnt/opencloud/config /mnt/opencloud/config-backup
+cp -a /mnt/opencloud/data /mnt/opencloud/data-backup
+```
+
+Replace the paths with the directories used by your deployment.
+
+  </TabItem>
+
+  <TabItem value="named-volumes" label="Using Named Volumes">
+
+Create a backup directory and copy the configuration and data from the OpenCloud container.
+
+```bash
+mkdir -p ~/opencloud-backups
+docker cp opencloud-compose-opencloud-1:/etc/opencloud ~/opencloud-backups/config-backup
+docker cp opencloud-compose-opencloud-1:/var/lib/opencloud ~/opencloud-backups/data-backup
+```
+
+Replace `opencloud-compose-opencloud-1` with the name of your OpenCloud container if it differs.
+
+  </TabItem>
+</Tabs>
+
+## Update the `opencloud-compose` Checkout
+
+If you use the `opencloud-compose` repository, update your local copy of the repository.
+
+```bash
+cd /opencloud-compose
+git pull
+```
+
+Skip this step if you run OpenCloud with plain Docker.
+
+## Stop OpenCloud
+
+Stop the currently running OpenCloud instance.
+
+<Tabs>
+  <TabItem value="docker-compose" label="Docker Compose">
+
+```bash
+docker compose stop
+```
+
+  </TabItem>
+
+  <TabItem value="docker" label="Docker">
+
+```bash
+docker stop opencloud
+```
+
+  </TabItem>
+</Tabs>
+
+## Pull the new OpenCloud image
+
+Pull the image that matches the release channel you use:
+
+- `opencloudeu/opencloud-rolling:{tag}` for rolling releases
+- `opencloudeu/opencloud:{tag}` for stable releases
+
+Replace `{tag}` with the image tag for the version you want to install. Available tags are listed on [Docker Hub](https://hub.docker.com/u/opencloudeu).
+
+```bash
+docker pull opencloudeu/opencloud-rolling:{tag}
+```
+
+## Verify Configuration Changes
+
+If upgrading from an older release, check for required configuration changes:
+
+### Open a Temporary OpenCloud Container
+
+Open a shell in a temporary OpenCloud container and mount your OpenCloud configuration directory or configuration volume to `/etc/opencloud`.
+
+<Tabs>
+  <TabItem value="named-volumes" label="Using Named Volumes">
+
+```bash
+docker run --rm -it --entrypoint /bin/sh -v "<opencloud-config-volume>:/etc/opencloud" opencloudeu/opencloud (or opencloud-rolling):"version-tag"
+```
+
+Replace `<opencloud-config-volume>` with the Docker volume or bind mount that contains your OpenCloud configuration.
+
+  </TabItem>
+
+  <TabItem value="bind-mounts" label="Using Bind Mounts">
+
+```bash
+docker run --rm -it --entrypoint /bin/sh -v "<path-to-your-config-directory>:/etc/opencloud" opencloudeu/opencloud (or opencloud-rolling):"version-tag"
+```
+
+Replace `<path-to-your-config-directory>` with the host directory that contains your `opencloud.yaml`.
+
+  </TabItem>
+</Tabs>
+
+### Generate the Configuration Diff
+
+Inside the temporary container, run:
+
+```bash
+opencloud init --diff
+```
+
+If you see `no changes, your config is up to date`, no further action is needed.
+
+<img src={require("../img/init-diff.png").default} alt="init -diff" width="1920"/>
+
+In that case, [exit the temporary container](#exit-the-temporary-container) and start OpenCloud.
+
+Otherwise, update your `opencloud.yaml` file accordingly and [apply the patch](#apply-the-configuration-patch).
+
+Example output:
+
+```diff
+diff -u /etc/opencloud/opencloud.yaml /etc/opencloud/opencloud.yaml.tmp
+--- /etc/opencloud/opencloud.yaml
++++ /etc/opencloud/opencloud.yaml.tmp
+@@ -90,6 +90,9 @@
+ sharing:
+   events:
+     tls_insecure: false
++service_account:
++  service_account_id: 00000000-0000-0000-0000-000000000000
++  service_account_secret: example-service-account-secret
+ storage_users:
+   events:
+     tls_insecure: false
+
+diff written to /etc/opencloud/opencloud.config.patch
+```
+
+The command creates the following patch file:
+
+```bash
+/etc/opencloud/opencloud.config.patch
+```
+
+### Apply the Configuration Patch
+
+Change to the configuration directory:
+
+```bash
+cd /etc/opencloud
+```
+
+Verify that the patch file was created:
+
+```bash
+ls
+```
+
+Example output:
+
+```bash
+banned-password-list.txt
+csp.yaml
+opencloud.config.patch
+opencloud.yaml
+opencloud.yaml.2026-05-19-15-45-44.backup
+```
+
+Test the patch before applying it:
+
+```bash
+patch --dry-run opencloud.yaml < opencloud.config.patch
+```
+
+Expected output:
+
+```bash
+checking file opencloud.yaml
+```
+
+Apply the patch:
+
+```bash
+patch opencloud.yaml < opencloud.config.patch
+```
+
+Expected output:
+
+```bash
+patching file opencloud.yaml
+```
+
+Verify that the following configuration entries exist in `opencloud.yaml`:
+
+```yaml
+service_account:
+  service_account_id: 00000000-0000-0000-0000-000000000000
+  service_account_secret: example-service-account-secret
+```
+
+### Exit the Temporary Container
+
+Exit the temporary container after applying the configuration patch.
+
+```bash
+exit
+```
+
+## Start OpenCloud with updated image
+
+<Tabs groupId="deployment">
+  <TabItem value="docker" label="docker">
+    ```Shell
+    docker run \
+    --name opencloud \
+    --rm \
+    -it \
+    -p 9200:9200 \
+    -v $HOME/opencloud/opencloud-config:/etc/opencloud \
+    -v $HOME/opencloud/opencloud-data:/var/lib/opencloud \
+    -e OC_INSECURE=true \
+    -e PROXY_HTTP_ADDR=0.0.0.0:9200 \
+    -e OC_URL=https://localhost:9200 \
+    opencloudeu/opencloud-rolling:{tag}
+    ```
+  </TabItem>
+  <TabItem value="docker-compose" label="docker compose">
+    ```Shell
+    docker compose up -d
+    ```
+  </TabItem>
+</Tabs>
+
+## Conclusion
+
+Make sure that all previously created data, users, shared files, public links exist.
diff --git a/versioned_docs/version-7.x/admin/resources/_category_.json b/versioned_docs/version-7.x/admin/resources/_category_.json
new file mode 100644
index 000000000..ca4df7ca0
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/resources/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Resources",
+  "position": 7
+}
diff --git a/versioned_docs/version-7.x/admin/resources/common-issues.md b/versioned_docs/version-7.x/admin/resources/common-issues.md
new file mode 100644
index 000000000..fab2bd8bc
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/resources/common-issues.md
@@ -0,0 +1,245 @@
+---
+sidebar_position: 4
+id: common-issues
+title: Common Issues & Help
+description: Common issues & help
+draft: false
+---
+
+# Common Issues & Help
+
+## Check whether the containers are running
+
+```bash
+docker ps
+```
+
+<img src={require("./img/common-issues/quick-docker-running.png").default} alt="Admin general" width="1920"/>
+
+Several containers should be listed here, e.g., for opencloud, traefik, etc.
+
+## Accept Self-Signed Certificates
+
+As the local environment is self-signed, you must accept the security risk in your browser.
+
+For Firefox:
+
+You need to click on Advanced
+
+<img src={require("./img/common-issues/quick-advanced.png").default} alt="Admin general" width="500"/>
+
+Confirm the risk with Accept the risk and Continue
+
+<img src={require("./img/common-issues/quick-accept-security-risk.png").default} alt="Admin general" width="500"/>
+
+## Docker Permission Issues
+
+If your Docker Compose setup fails to start and the logs contain messages such as `permission denied`, it's likely due to incorrect ownership of local directories used by the containers.
+
+Example log output:
+
+```bash
+opencloud-1 | {"level":"fatal","service":"nats","time":"2025-04-08T09:59:59Z","line":"github.com/opencloud-eu/opencloud/services/nats/pkg/logging/nats.go:33","message":"Can't start JetStream: could not create storage directory - mkdir /var/lib/opencloud/nats: permission denied"}
+```
+
+This error typically occurs when the mounted directories are owned by the wrong user, such as `root`, instead of the standard Docker user (`UID 1000`).
+
+Incorrect directory ownership:
+
+```bash
+drwxr-xr-x  3 root root 4096 Apr  8 09:59 opencloud-data
+```
+
+Correct ownership should be:
+
+```bash
+drwxr-xr-x  9 1000 1000 4096 Apr  7 07:57 opencloud-data
+```
+
+To resolve this issue, adjust the ownership of the directory using the `chown` command:
+
+```bash
+chown -R 1000:1000 opencloud-data
+```
+
+:::caution
+Security Warning
+
+The user with UID 1000 on your host system will have full access to these mounted directories. This means that any local user account with this ID can read, modify, or delete OpenCloud config and data files.
+
+This can pose a security risk in shared or multi-user environments. Make sure to implement proper user and permission management and consider isolating access to these directories.
+
+:::
+
+Ensure you apply this to all relevant folders that are mounted into your containers. This will grant the Docker container the necessary permissions to access and write to these directories.
+
+## Change Admin Password Set in `.env`
+
+If you initially set the OpenCloud admin password using the `.env` file, please note:
+
+:::caution
+You cannot simply change the password again by editing the `.env` file.  
+Once the container is running, password changes must be made via the Web UI or terminal.
+:::
+
+### Option 1: Change via Web UI
+
+If the current admin password is known:
+
+1. Log in to the OpenCloud Web Interface.
+2. Navigate to Settings > Security.
+3. Enter your current password and choose a new one.
+
+> If the admin password is forgotten or you prefer command-line tools, use the terminal method below.
+
+### Option 2: Change via Terminal
+
+If the admin password is forgotten or needs to be changed via the terminal:
+
+#### Stop the Docker container
+
+First, stop your OpenCloud container:
+
+```bash
+docker compose stop opencloud
+```
+
+#### Run the password reset command
+
+Use the following command to reset the password:
+
+```bash
+sudo docker run -it --rm -v <opencloud-data-path>:/var/lib/opencloud -v <opencloud-config-path>:/etc/opencloud opencloudeu/opencloud:<opencloud-version> idm resetpassword
+```
+
+#### Replace
+
+`<opencloud-data-path>` – Docker volume for OpenCloud data
+
+`<opencloud-config-path>` – Docker volume for OpenCloud config
+
+`<opencloud-version>` – Use latest or your specific version
+
+🔍 How to find the volume names
+You can list your current Docker volumes with:
+
+```bash
+docker volume ls
+```
+
+Look for volumes like:
+
+`opencloud-compose_opencloud-data`
+
+`opencloud-compose_opencloud-config`
+
+#### Example for standard setup
+
+```bash
+sudo docker run -it --rm -v opencloud-compose_opencloud-data:/var/lib/opencloud -v opencloud-compose_opencloud-config:/etc/opencloud opencloudeu/opencloud:latest idm resetpassword
+```
+
+#### Start the container again
+
+```bash
+docker compose up -d
+```
+
+## Internal LibreIDM cert expires
+
+### 🔧 Renewing an expired certificate in internal IDM (OpenCloud)
+
+When using the internal IDM (LibreIDM), the LDAP certificate may expire over time.
+You can see similar errormessages in your logfiles:
+
+```bash
+opencloud-1      | 2026-03-10T14:10:36Z WRN core access token not set host.name=3133c92656c8 pkg=rhttp service=frontend traceid=2da2886cf47f0143876953ee33f814a9
+opencloud-1      | 2026-03-10T14:10:36Z ERR failed to build subject.session error="invalid key format" service=proxy
+opencloud-1      | 2026-03-10T14:10:36Z ERR handleConnection ber.ReadPacket error="remote error: tls: bad certificate" service=idm
+opencloud-1      | 2026-03-10T14:10:37Z ERR could not get ldap Connection error="LDAP Result Code 200 \"Network Error\": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-03-10T14:10:37Z is after 2026-03-04T10:02:39Z" service=graph
+opencloud-1      | 2026-03-10T14:10:37Z ERR failed to add user error="LDAP Result Code 200 \"Network Error\": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-03-10T14:10:37Z is after 2026-03-04T10:02:39Z" request-id=3133c92656c8/LlC0SVlYb4-000023 service=graph
+opencloud-1      | 2026-03-10T14:10:37Z ERR handleConnection ber.ReadPacket error="remote error: tls: bad certificate" service=idm
+opencloud-1      | 2026-03-10T14:10:37Z ERR could not create user: backend error error="generalException: failed to add user" request-id=3133c92656c8/LlC0SVlYb4-000023 service=graph
+opencloud-1      | 2026-03-10T14:10:37Z WRN Error Response OData Error="failed to add user" service=proxy
+opencloud-1      | 2026-03-10T14:10:37Z ERR Error creating user error="500 Internal Server Error" service=proxy
+opencloud-1      | 2026-03-10T14:10:37Z ERR Autoprovisioning user failed error="500 Internal Server Error" service=proxy
+```
+
+#### 🛠️ Solution
+
+Navigate to the IDM directory
+
+```bash
+cd .opencloud/idm
+```
+
+Delete the old certificates
+
+```bash
+rm ldap.crt ldap.key
+
+Directory structure:
+
+.opencloud/idm
+├── idm.boltdb
+├── ldap.crt
+└── ldap.key
+```
+
+Restart the OpenCloud container
+
+```bash
+docker compose restart
+```
+
+➡️ The certificates will be automatically regenerated on restart.
+
+#### ⚠️ Recommendation
+
+Admins should avoid using LibreIDM in production and use OpenLDAP instead.
+
+## Login fails with LDAP Result Code 49 (Invalid Credentials)
+
+When using the built-in IDM (LibreIDM), login can fail with `Unexpected HTTP response:
+500` in the browser, and the logs show the internal directory rejecting a bind:
+
+```bash
+opencloud-1 | {"level":"error","service":"idm","bind_dn":"uid=idp,ou=sysusers,o=libregraph-idm","op":"bind","message":"not found"}
+opencloud-1 | {"level":"error","service":"idp","error":"ldap identifier backend logon connect error: LDAP Result Code 49 \"Invalid Credentials\": ","message":"identifier failed to logon with backend"}
+```
+
+The built-in IDM seeds its service-account passwords once, at first start, into a
+bolt-store on the data volume (`idm.boltdb`), matching the values `opencloud init`
+writes into `opencloud.yaml` on the config volume. The bind fails when the two volumes
+are no longer from the same `init`. The `idm` line reads either `not found` or
+`invalid credentials`; both mean the same mismatch. This usually comes from setting an
+internal LDAP password in the environment, or from reusing one volume (for example a
+restored or carried-over data volume) without the other.
+
+### Solution
+
+With the built-in IDM, do not set the internal LDAP or service passwords in `.env` or
+the environment. Let `opencloud init` generate them, and keep only
+`INITIAL_ADMIN_PASSWORD`.
+
+Treat `opencloud.yaml` (config volume) and the data volume as one set. When you back
+up, restore, or move the instance, keep them together and from the same point in time.
+
+If you do not need the existing data, remove both volumes so `init` generates a
+matching set, then start again:
+
+```bash
+docker compose down
+docker volume rm opencloud-compose_opencloud-config opencloud-compose_opencloud-data
+docker compose up -d
+```
+
+:::caution
+Deleting `idm.boltdb` alone may not be enough: it is re-seeded from the current config,
+but a bind password still set in the environment keeps the two sides out of sync.
+:::
+
+### Recommendation
+
+The built-in IDM is intended for testing and small installations. For production, use
+an external identity provider, for example Keycloak with an external LDAP.
diff --git a/versioned_docs/version-7.x/admin/resources/demo-user.md b/versioned_docs/version-7.x/admin/resources/demo-user.md
new file mode 100644
index 000000000..957bfe5d9
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/resources/demo-user.md
@@ -0,0 +1,97 @@
+---
+sidebar_position: 5
+id: demo-user
+title: Demo User
+description: Demo User Overview
+draft: false
+---
+
+# Demo User Overview
+
+This page introduces the pre-configured demo users available in OpenCloud. These users are designed to help you explore the platform’s features, test different roles, and experience OpenCloud from various perspectives without setting up new accounts.
+
+Each demo user has specific permissions and access levels, allowing you to simulate real-world scenarios such as admin management, file sharing, and collaboration.
+
+Below, you’ll find details about each user, including their roles and login credentials.
+
+| Name                | User Name | Password |    Role     |                 Group membership                 |
+| :------------------ | :-------: | :------: | :---------: | :----------------------------------------------: |
+| Dennis Ritchie      |  dennis   |   demo   |    Admin    |  basic-haters, programmers, unix-lovers, users   |
+| Margaret Hamilton   | margaret  |   demo   | Space Admin |           apollos, programmers, users            |
+| Alan Turing         |   alan    |   demo   |    User     | chess-lovers, machine-lovers, programmers, users |
+| Lynn Conway         |   lynn    |   demo   |    User     |         programmers, users, vlsi-lovers          |
+| Mary Kenneth Keller |   mary    |   demo   |    User     |               bible-readers, users               |
+
+## Dennis Ritchie
+
+OpenCloud Username: dennis
+
+Role: Admin
+
+Co-developer of UNIX & inventor of the C programming language
+
+<img src={require("./img/demo-user/dennis-ritchie.png").default} alt="Dennis Ritchie" width="200"/>
+
+- Studied physics and applied mathematics at Harvard University
+- Worked at Bell Labs from 1967, where he developed the first version of the Unix operating system
+- Died in 2011, but his influence on modern software development remains immeasurable
+
+## Margaret Hamilton
+
+OpenCloud Username: margaret
+
+Role: Space Admin
+
+Software pioneer & NASA developer
+
+<img src={require("./img/demo-user/margaret-hamilton.png").default} alt="Margaret Hamilton" width="200"/>
+
+- Studied mathematics at Earlham College
+- Developed the on-board flight software for NASA as a software engineer at MIT
+- Her work was crucial to the success of the Apollo 11 mission in 1969
+- From 1976 to 1984, she was the Managing Director of Higher Order Software (HOS)
+
+## Alan Turing
+
+OpenCloud Username: alan
+
+Role: User
+
+Father of modern computer science & codebreaker in the Second World War
+
+<img src={require("./img/demo-user/alan-turing.png").default} alt="Alan Turing" width="200"/>
+
+- British logician, mathematician, and computer scientist
+- Developed the theoretical foundations of modern computer technology
+- Made a decisive contribution to the decryption of the German Enigma cipher
+- Was discriminated against and persecuted because of his homosexuality
+
+## Lynn Conway
+
+OpenCloud Username: lynn
+
+Role: User
+
+Computer scientist & microchip design pioneer
+
+<img src={require("./img/demo-user/lynn-conway.png").default} alt="Lynn Conway" width="200"/>
+
+- Studied electrical engineering at Columbia University
+- Developed VLSI design methodology, revolutionizing microchip development
+- Worked at IBM, but was dismissed after gender transition; later contributed at Xerox PARC
+- Professor of electrical engineering and computer science at the University of Michigan
+- Advocate for transgender rights and diversity in STEM fields
+
+## Mary Kenneth Keller
+
+OpenCloud Username: mary
+
+Role: User
+
+First woman with a PhD in computer science
+
+<img src={require("./img/demo-user/mary-kenneth-keller.png").default} alt="Mary Kenneth Keller" width="200"/>
+
+- Was a nun and studied mathematics (Bachelor & Master of Science)
+- First woman to work at Dartmouth College's Computer Science Center
+- Founded and chaired the first computer science department at Clarke University, Iowa, for over 20 years
diff --git a/versioned_docs/version-7.x/admin/resources/faq.md b/versioned_docs/version-7.x/admin/resources/faq.md
new file mode 100644
index 000000000..35ba2b575
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/resources/faq.md
@@ -0,0 +1,342 @@
+---
+sidebar_position: 1
+id: faq
+title: FAQ
+description: Frequently asked questions FAQ
+draft: false
+---
+
+# FAQ
+
+Welcome to the frequently asked questions (FAQ). Here you will find answers to the most common questions.
+
+## General Questions
+
+<details>
+<summary>What problem does OpenCloud solve for me?</summary>
+
+### Simplified Administration
+
+OpenCloud is designed to be straightforward to set up and manage, allowing administrators to handle the system with minimal effort and without unnecessary complexity.
+
+### Independent File-sharing
+
+OpenCloud is designed to give you a privacy-focused alternative to mainstream platforms like Microsoft OneDrive or Google Drive, freeing you from reliance on big tech services and their data-collection practices.
+
+</details>
+
+<details>
+<summary>How does OpenCloud differ from other open source file sharing applications?</summary>
+
+OpenCloud is simpler and more reliable than existing PHP-based solutions. OpenCloud stands out by offering a radically simplified architecture compared to other open-source file-sharing solutions. While many alternatives require maintaining complex stacks involving multiple components like PHP, MySQL, Redis, and Apache — creating a web of dependencies and potential security risks—OpenCloud avoids this entirely. It writes data directly to disk instead of relying on a dedicated database, making it much easier to maintain and far more reliable. With OpenCloud, you can focus on your files without worrying about intricate setups or data loss risks.
+
+</details>
+
+<details>
+<summary>Is OpenCloud 100% open source?</summary>
+
+Yes. The source code of OpenCloud is licenced under the Apache 2 licence.
+
+</details>
+
+## Cost and Licensing
+
+<details>
+<summary>Is OpenCloud free to use?</summary>
+
+Yes, please!
+
+</details>
+
+<details>
+<summary>Can I use it for commercial purposes?</summary>
+
+Absolutely!
+
+</details>
+
+<details>
+<summary>If OpenCloud is free, how are the employees paid?</summary>
+
+We're glad you asked.
+We provide a paid support subscription, see [https://opencloud.eu/en/product/service-and-support](https://opencloud.eu/en/product/service-and-support). With a support subscription you’ll be the first to know about security vulnerabilities and receive detailed instructions on how to address them or how to integrate OpenCloud into your existing systems and storage. We also provide Long-Term-Support if you don't want to upgrade your system so frequently.
+
+</details>
+
+<details>
+<summary>Are there educational or non-profit discounts or support plans?</summary>
+
+Please contact sales for such inquiries and we'll find a good solution.
+
+</details>
+
+## Privacy and Security
+
+<details>
+<summary>Does OpenCloud comply with privacy regulations such as GDPR or HIPAA?</summary>
+
+Yes, of course!
+
+</details>
+
+## Features and Functionality
+
+<details>
+<summary>What types of files can I store and share with OpenCloud?</summary>
+
+No restrictions. You can store and share any filetype. If necessary, you can restrict the upload of certain filetypes like .exe or documents with macros like xlsm.
+
+</details>
+
+<details>
+<summary>Is there an upload file size limit in OpenCloud?</summary>
+
+Nope.
+
+</details>
+
+<details>
+<summary>Does OpenCloud support real-time collaboration and editing?</summary>
+
+Yes. We use the WOPI standard for realtime collaboration in the web office application Collabora.
+
+</details>
+
+<details>
+<summary>Can I create and manage user accounts and permissions?</summary>
+
+Yes, you can either use the built-in user management system or integrate OpenCloud with your existing identity management.
+
+</details>
+
+<details>
+<summary>Are there mobile apps, and do they offer the same features as the desktop version?</summary>
+
+We provide apps for Windows, MacOS, Linux, iOS and Android. Please refer to the roadmap to see when the apps will be available: [https://opencloud.eu/roadmap](https://opencloud.eu/roadmap)
+
+</details>
+
+<details>
+<summary>Does OpenCloud support versioning?</summary>
+
+Yes. In case you made a mistake, you can always jump back to older versions of a file. We got your back!
+
+</details>
+
+## Deployment and Installation
+
+<details>
+<summary>Can I self-host OpenCloud on my own server?</summary>
+
+Yes and we encourage you to do so! (We do not provide a SaaS service that stores your files on our servers, like Google Drive or Microsoft OneDrive do.)
+
+</details>
+
+<details>
+<summary>What are the system requirements for hosting OpenCloud?</summary>
+
+The system requirements for hosting OpenCloud depend heavily on the number of concurrent users and the workload they generate, such as the frequency of their requests. OpenCloud is versatile—it can run on anything from a Raspberry Pi to a large data center setup.
+
+For example, a Raspberry Pi 4 can support hundreds of registered users, but the key factor is the number of users actively using the system at the same time. Concurrent users, especially those using desktop or mobile clients (which frequently check for updates), require more resources. Additional features like the web office integration Collabora or antivirus scanning also impact performance.
+
+For a minimal setup, OpenCloud can comfortably support 20 concurrent users browsing files via the web interface. As your user base or workload increases, scaling the hardware accordingly will ensure smooth performance. A factor to scale performance is just to add storage, as OpenCloud needs storage IOPS for performance.
+
+Key Factors for Optimal Performance:
+
+- Storage IOPS: The performance of OpenCloud highly relies on the amount of IOPS of your storage - the more, the better.
+- Network throughput: Another factor for enhancing the performance of OpenCloud is network throughput in distributed storage.
+
+</details>
+
+<details>
+<summary>How difficult is it to set up, and is technical expertise required?</summary>
+
+One of our goals is to make the deployment of OpenCloud as simple as possible. Depending on your experience, it's possible to set up a basic OpenCloud instance in less than 1 minute. See [the Quick Start](https://docs.opencloud.eu/docs/admin)
+
+</details>
+
+<details>
+<summary>Can it be deployed in a Docker or Kubernetes environment?</summary>
+
+Yes.
+
+- Docker Compose: The docker compose files are maintained and tested by us.
+- Community HELM charts: Feel free to contribute!
+
+</details>
+
+## Customization and Extensibility
+
+<details>
+<summary>Can I add modifications like add-ons or extensions?</summary>
+
+Yes, OpenCloud allows you customizations:
+
+- Wordings: You can replace specific terms, such as changing the word “Spaces” to “Datarooms” to better fit your terminology.
+- Extensions: The web UI also supports custom web extensions. Check out our developer documentation [here] to learn how to get started with creating and adding your own extensions and find existing extensions [here].
+
+</details>
+
+## Collaboration and Sharing
+
+<details>
+<summary>How does file sharing work within OpenCloud?</summary>
+
+OpenCloud offers three main ways to share files, making it easy to collaborate and manage access:
+
+### Personal Share
+
+Share files with registered users within your organization. You can assign permissions such as view, edit, or download, providing flexible control over file access.
+
+### Share via Link
+
+Share files with anyone, even outside your organization, by generating a link. No account is required for accessing the file.
+
+### Spaces
+
+Spaces are user-independent datarooms that belong to the organization rather than an individual. This ensures files remain within the organization, even if users leave. Examples of Spaces include school classes, collaborative projects, or organizational units like Marketing, Sales, or Finance. Spaces are easier for admins to manage, as they can be self-managed by designated users.
+
+### Special Feature: Secret File Drop
+
+The Secret File Drop allows anonymous users to securely upload files (e.g., homework, photos or even whistleblower material) without needing an account.
+
+</details>
+
+<details>
+<summary>Can I share files with external users?</summary>
+
+Yes. You can share files with anyone, even outside your organization, by generating a link. No account is required for accessing the file. Link sharing can be disabled if needed.
+
+</details>
+
+<details>
+<summary>Does it support federated sharing between different instances?</summary>
+
+Yes, federated sharing is possible via Open Cloud Mesh (OCM). This feature allows you to securely share files and collaborate across different instances, even if they are hosted by different organizations.
+
+For example, a company with multiple branches in different regions could use OCM to share files between instances, enabling collaboration across teams while maintaining control over local data.
+
+</details>
+
+<details>
+<summary>Are there limits on the number of users or size of files shared?</summary>
+
+No.
+
+</details>
+
+## Data Management
+
+<details>
+<summary>Where is my data stored, and can I choose the storage location?</summary>
+
+OpenCloud is a fully self-hosted (on-premise) solution, meaning you have complete control over where your data is stored. You can choose the server and country where OpenCloud will be installed. Unlike SaaS services like Google Drive or Microsoft OneDrive, which store your files on their servers, OpenCloud gives you full control over your data, ensuring privacy and security on your terms.
+
+</details>
+
+<details>
+<summary>Does it support integration with third-party storage solutions like S3 Storage?</summary>
+
+Yes, the following storage can be used:
+
+- Posix Storage
+- S3ng
+- Ceph
+
+</details>
+
+## Support and Community
+
+<details>
+<summary>How often is OpenCloud updated, and how are updates delivered?</summary>
+
+Download updates on download.opencloud.eu or via docker hub.
+
+OpenCloud is released in three different release types: Production, Rolling and Daily. Each of them is targeted to a specific use case and audience group.
+
+</details>
+
+## Migration
+
+<details>
+<summary>Can I migrate from ownCloud or Nextcloud?</summary>
+
+Yes, there will be a migration available in 2025.
+
+</details>
+
+## Compliance and Legal
+
+<details>
+<summary>Is OpenCloud compliant with GDPR (DSGVO) or HIPAA?</summary>
+
+Yes, of course!
+
+</details>
+
+<details>
+<summary>Is the OpenCloud Web UI accessible according to EN 301 549 / WCAG / BITV 2.0?</summary>
+
+Yes, the OpenCloud Web UI is accessible according to EN 301 549, WCAG, and BITV 2.0. We believe that accessibility is important for everyone, not just for individuals with disabilities, as it benefits all users at some point in their lives.
+
+As we release new features every 3 weeks, we ensure that accessibility is integrated into the feature development lifecycle. While we strive to maintain high accessibility standards, we’re only human and occasional mistakes may happen. If a new feature unintentionally impacts accessibility, we treat it as a bug and address it in the next release.
+
+If you encounter any accessibility violations, please let us know so we can promptly resolve the issue.
+
+</details>
+
+<details>
+<summary>Can access controls and permissions be configured to meet regulatory requirements?</summary>
+
+Yes, OpenCloud offers robust access control and permission settings that can be fully configured to meet various regulatory requirements. You can define user roles, assign specific permissions, and set up granular access controls to ensure compliance with industry standards and regulations such as GDPR, HIPAA, and others. With OpenCloud, you have the flexibility to control who accesses your data, what actions they can perform, and how data is shared, ensuring that your system remains secure and compliant with the required regulations.
+
+</details>
+
+<details>
+<summary>How does it handle requests for data access or deletion under GDPR?</summary>
+
+OpenCloud provides users with the ability to trigger a GDPR Export in a self-service manner. This export generates a detailed report of all personal data stored in the context of OpenCloud, excluding the user’s own files. The report includes relevant data related to the user’s account and activity within the system, ensuring transparency and compliance with GDPR requirements. For the deletion of personal files, users have full control to manage and remove their own data as needed.
+
+</details>
+
+## Miscellaneous
+
+<details>
+<summary>Does OpenCloud offer multi-language support?</summary>
+
+Yes, OpenCloud fully maintains both English and German languages. Additionally, the web UI offers support for other languages, which are listed below. Please note that these languages are not 100% translated and are maintained by the community on a best-effort basis. We appreciate the contributions from our community to help improve the language support over time.
+
+Community maintained languages:
+
+- Albanian
+- Afrikaans
+- Arabic
+- Bosnian
+- Bulgarian
+- Chinese
+- Croatian
+- Czech
+- Estonian
+- French
+- Galician
+- Georgian
+- Greek
+- Hebrew
+- Indonesian
+- Italian
+- Japanese
+- Korean
+- Dutch
+- Polish
+- Portuguese
+- Romanian
+- Russian
+- Serbian
+- Sinhala
+- Slovak
+- Spanish
+- Swedish
+- Turkish
+- Ukrainian
+
+</details>
diff --git a/versioned_docs/version-7.x/admin/resources/img/common-issues/quick-accept-security-risk.png b/versioned_docs/version-7.x/admin/resources/img/common-issues/quick-accept-security-risk.png
new file mode 100644
index 000000000..696068732
Binary files /dev/null and b/versioned_docs/version-7.x/admin/resources/img/common-issues/quick-accept-security-risk.png differ
diff --git a/versioned_docs/version-7.x/admin/resources/img/common-issues/quick-advanced.png b/versioned_docs/version-7.x/admin/resources/img/common-issues/quick-advanced.png
new file mode 100644
index 000000000..ce4ef77f2
Binary files /dev/null and b/versioned_docs/version-7.x/admin/resources/img/common-issues/quick-advanced.png differ
diff --git a/versioned_docs/version-7.x/admin/resources/img/common-issues/quick-docker-running.png b/versioned_docs/version-7.x/admin/resources/img/common-issues/quick-docker-running.png
new file mode 100644
index 000000000..5e0cde78b
Binary files /dev/null and b/versioned_docs/version-7.x/admin/resources/img/common-issues/quick-docker-running.png differ
diff --git a/versioned_docs/version-7.x/admin/resources/img/demo-user/admin.png b/versioned_docs/version-7.x/admin/resources/img/demo-user/admin.png
new file mode 100644
index 000000000..6c6a319d5
Binary files /dev/null and b/versioned_docs/version-7.x/admin/resources/img/demo-user/admin.png differ
diff --git a/versioned_docs/version-7.x/admin/resources/img/demo-user/alan-turing.png b/versioned_docs/version-7.x/admin/resources/img/demo-user/alan-turing.png
new file mode 100644
index 000000000..7adc97d2d
Binary files /dev/null and b/versioned_docs/version-7.x/admin/resources/img/demo-user/alan-turing.png differ
diff --git a/versioned_docs/version-7.x/admin/resources/img/demo-user/dennis-ritchie.png b/versioned_docs/version-7.x/admin/resources/img/demo-user/dennis-ritchie.png
new file mode 100644
index 000000000..baa33575b
Binary files /dev/null and b/versioned_docs/version-7.x/admin/resources/img/demo-user/dennis-ritchie.png differ
diff --git a/versioned_docs/version-7.x/admin/resources/img/demo-user/lynn-conway.png b/versioned_docs/version-7.x/admin/resources/img/demo-user/lynn-conway.png
new file mode 100644
index 000000000..dc0892b14
Binary files /dev/null and b/versioned_docs/version-7.x/admin/resources/img/demo-user/lynn-conway.png differ
diff --git a/versioned_docs/version-7.x/admin/resources/img/demo-user/margaret-hamilton.png b/versioned_docs/version-7.x/admin/resources/img/demo-user/margaret-hamilton.png
new file mode 100644
index 000000000..023748be3
Binary files /dev/null and b/versioned_docs/version-7.x/admin/resources/img/demo-user/margaret-hamilton.png differ
diff --git a/versioned_docs/version-7.x/admin/resources/img/demo-user/mary-kenneth-keller.png b/versioned_docs/version-7.x/admin/resources/img/demo-user/mary-kenneth-keller.png
new file mode 100644
index 000000000..699ac4962
Binary files /dev/null and b/versioned_docs/version-7.x/admin/resources/img/demo-user/mary-kenneth-keller.png differ
diff --git a/versioned_docs/version-7.x/admin/resources/img/lifecycle/Release Cycle OpenCloud.png b/versioned_docs/version-7.x/admin/resources/img/lifecycle/Release Cycle OpenCloud.png
new file mode 100644
index 000000000..9b950d111
Binary files /dev/null and b/versioned_docs/version-7.x/admin/resources/img/lifecycle/Release Cycle OpenCloud.png differ
diff --git a/versioned_docs/version-7.x/admin/resources/img/lifecycle/semver.png b/versioned_docs/version-7.x/admin/resources/img/lifecycle/semver.png
new file mode 100644
index 000000000..c8181a00d
Binary files /dev/null and b/versioned_docs/version-7.x/admin/resources/img/lifecycle/semver.png differ
diff --git a/versioned_docs/version-7.x/admin/resources/index.md b/versioned_docs/version-7.x/admin/resources/index.md
new file mode 100644
index 000000000..7f0ac6336
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/resources/index.md
@@ -0,0 +1,18 @@
+---
+sidebar_position: 0
+id: admin-resources
+title: Resources
+description: Helpful resources for OpenCloud administrators
+---
+
+# Resources
+
+Use this section for troubleshooting, lifecycle information, and general admin help.
+
+## In this section
+
+- [FAQ](./faq.md)
+- [What's New](./whats-new.md)
+- [Release Lifecycle](./lifecycle.md)
+- [Common Issues & Help](./common-issues.md)
+- [Demo User](./demo-user.md)
diff --git a/versioned_docs/version-7.x/admin/resources/lifecycle.md b/versioned_docs/version-7.x/admin/resources/lifecycle.md
new file mode 100644
index 000000000..6e3b91f58
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/resources/lifecycle.md
@@ -0,0 +1,88 @@
+---
+sidebar_position: 2
+id: lifecycle
+title: Release Lifecycle
+description: Release Lifecycle
+draft: false
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+## Release Types
+
+OpenCloud offers three release types to suit different needs: Rolling, Production, and LTS. For most users, Rolling is ideal, providing the latest features every few weeks. Production focuses on stability. LTS (Long-Term Support Release) is designed specifically for businesses that need longevity and extended backports.
+
+<img src={require("./img/lifecycle/Release Cycle OpenCloud.png").default} alt="Release types" width="1920"/>
+
+### Advantage of the LTS Releases
+
+With LTS, businesses can continue using an older production release without needing to upgrade to the latest version, while still receiving critical security patches and critical stability fixes. This makes LTS the perfect choice for organizations seeking a stable long-term solution. LTS is available exclusively to customers with a service and support entitlement through a enterprise license.
+
+| Rolling                                                                                                                                                                                       | Production                                                                                                                                                              | LTS                                                                                                                                                                      |
+| :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <ul><li>For enthusiasts</li><li>Contains latest features</li><li>Every 3 weeks</li><li>Automated quality assurance</li><li>Community supported</li><li>Documentation on best effort</li></ul> | <ul><li>For production</li><li>Focus on stability</li><li>About every 6 months</li><li>Full quality assurance</li><li>Professional support</li><li>Documented</li></ul> | <ul><li>For production</li><li>Focus on longevity</li><li>Backports for 2 years</li><li>Full quality assurance</li><li>Professional support</li><li>Documented</li></ul> |
+
+## Release Dates
+
+<Tabs>
+  <TabItem value="rolling" label="Rolling" default>
+    | Version | Release Date | Release Notes & Download|
+    |:--------|:-------------|:--------------|
+    | v7.1.0 | 2026 June 2 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v7.1.0) |
+    | v7.0.0 | 2026 May 21 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v7.0.0) |
+    | v6.2.0 | 2026 May 11 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v6.2.0) |
+    | v6.1.0 | 2026 April 20 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v6.1.0) |
+    | v6.0.0 | 2026 March 30 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v6.0.0) |
+    | v5.2.0 | 2026 March 9 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v5.2.0) |
+    | v5.1.0 | 2026 February 16 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v5.1.0) |
+    | v5.0.2 | 2026 February 5 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v5.0.2) |
+    | v5.0.1 | 2026 January 28 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v5.0.1) |
+    | v5.0.0 | 2026 January 26 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v5.0.0) |
+    | v4.1.0 | 2025 December 15 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v4.1.0) |
+    | v3.7.0 | 2025 November 3 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v3.7.0) |
+    | v3.6.0 | 2025 October 27 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v3.6.0) |
+    | v3.5.0 | 2025 September 22 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v3.5.0) |
+    | v3.4.0 | 2025 September 2 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v3.4.0) |
+    | v3.3.0 | 2025 August 11 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v3.3.0) |
+    | v3.2.0 | 2025 July 21 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v3.2.0) |
+    | v3.1.0 | 2025 June 30 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v3.1.0) |
+    | v3.0.0 | 2025 June 10 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v3.0.0) |
+    | v2.3.0 | 2025 May 19 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v2.3.0) |
+    | v2.2.0 | 2025 April 28 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v2.2.0) |
+    | v2.1.0 | 2025 April 07 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v2.1.0) |
+    | v2.0.0 | 2025 March 26 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v2.0.0) |
+    | v1.1.0 | 2025 March 18 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v1.1.0) |
+    | v1.0.0 | 2025 February 24 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v1.0.0) |
+
+  </TabItem>
+  <TabItem value="production " label="Production">
+    | Version | Release Date | Release Notes & Download |
+    |:--------|:-------------|:--------------|
+    | - | 2026 October 26 | Production Release |
+    | - | 2026 June 22 | Production Release |
+    | v4.0.7 | 2026 May 18 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v4.0.7) |
+    | v4.0.6 | 2026 April 29 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v4.0.6) |
+    | v4.0.5 | 2026 April 8 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v4.0.5) |
+    | v4.0.4 | 2026 March 30 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v4.0.4) |
+    | v4.0.3 | 2026 February 5 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v4.0.3) |
+    | v4.0.2 | 2026 February 5 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v4.0.2) |
+    | v4.0.1 | 2025 December 15 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v4.0.1) |
+    | v4.0.0 | 2025 December 1 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v4.0.0) |
+    | v2.0.5 | 2025 October 29 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v2.0.5) |
+    | v2.0.4 | 2025 July 16 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v2.0.4) |
+    | v2.0.3 | 2025 June 10 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v2.0.3) |
+    | v2.0.2 | 2025 May 2 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v2.0.2) |
+    | v2.0.1 | 2025 April 28 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v2.0.1) |
+    | v2.0.0 | 2025 March 26 | [Details · Download](https://github.com/opencloud-eu/opencloud/releases/tag/v2.0.0) |
+    </TabItem>
+  <TabItem value="lts" label="LTS">
+    LTS Releases will be availabile as the second Production Releases will be published. Until then a LTS release makes no sense.
+  </TabItem>
+</Tabs>
+
+## Versioning Scheme: Semantic Versioning
+
+OpenCloud follows [Semantic Versioning](https://semver.org/), also known as SemVer. Version numbers are structured as MAJOR.MINOR.PATCH. Breaking changes increase the MAJOR version, new backward-compatible features increase the MINOR version, and backward-compatible bug fixes increment the PATCH version.
+
+<img src={require("./img/lifecycle/semver.png").default} alt="Semantic Versioning" width="1920"/>
diff --git a/versioned_docs/version-7.x/admin/resources/whats-new.md b/versioned_docs/version-7.x/admin/resources/whats-new.md
new file mode 100644
index 000000000..a8e6f7343
--- /dev/null
+++ b/versioned_docs/version-7.x/admin/resources/whats-new.md
@@ -0,0 +1,11 @@
+---
+sidebar_position: 1
+id: whats-new
+title: What's New
+description: Release notes
+draft: false
+---
+
+# Release notes
+
+Please find the [Release notes on Github](https://github.com/opencloud-eu/opencloud/releases/latest).
diff --git a/versioned_docs/version-7.x/dev/cdperf.md b/versioned_docs/version-7.x/dev/cdperf.md
new file mode 100644
index 000000000..a13c70c32
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/cdperf.md
@@ -0,0 +1,7 @@
+---
+id: cdperf
+title: cdPerf
+custom_edit_url: https://github.com/opencloud-eu/opencloud/edit/main/docs/cdperf.md
+---
+
+The cdPerf documentation can be found <a href="/cdperf" target="_blank">here</a>.
diff --git a/versioned_docs/version-7.x/dev/index.md b/versioned_docs/version-7.x/dev/index.md
new file mode 100644
index 000000000..42e8fff52
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/index.md
@@ -0,0 +1,15 @@
+---
+sidebar_position: 1
+title: Welcome
+custom_edit_url: https://github.com/opencloud-eu/opencloud/edit/main/docs/intro.md
+---
+
+# Welcome
+
+Welcome to the OpenCloud Developer Documentation.
+
+Please be patient, we are working on the content.
+
+If you want to contribute to the dev docs, please visit [OpenCloud on Github](https://github.com/opencloud-eu/).
+
+Contents will be transferred during the build process.
diff --git a/versioned_docs/version-7.x/dev/server/_category_.json b/versioned_docs/version-7.x/dev/server/_category_.json
new file mode 100644
index 000000000..2d1556d73
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Server",
+  "position": 2
+}
diff --git a/versioned_docs/version-7.x/dev/server/apis/_category_.json b/versioned_docs/version-7.x/dev/server/apis/_category_.json
new file mode 100644
index 000000000..c345e05a4
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/apis/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Apis",
+  "position": 1
+}
\ No newline at end of file
diff --git a/versioned_docs/version-7.x/dev/server/apis/grpc_apis/index.md b/versioned_docs/version-7.x/dev/server/apis/grpc_apis/index.md
new file mode 100644
index 000000000..5b6aa07e8
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/apis/grpc_apis/index.md
@@ -0,0 +1,52 @@
+---
+title: gRPC
+sidebar_position: 2
+---
+
+## **R**emote &nbsp; **P**rocedure &nbsp; **C**alls
+
+[gRPC](https://grpc.io) is a modern open source high performance Remote Procedure Call (RPC) framework that can run in any environment. It can efficiently connect services in and across data centers with pluggable support for load balancing, tracing, health checking and authentication. It is also applicable in last mile of distributed computing to connect devices, mobile applications and browsers to backend services.
+
+## Advantages of gRPC
+
+### 🚀 Performance
+
+gRPC uses http/2 by default and is faster than REST. When using protocol buffers for encoding, the information comes on and off the wire much faster than JSON. Latency is an important factor in distributed systems. JSON encoding creates a noticeable factor of latency. For distributed systems and high data loads, gRPC can actually make an important difference. Other than that, gRPC supports multiple calls via the same channel and the connections are bidirectional. A single connection can transmit requests and responses at the same time. gRPC keeps connections open to reuse the same connection again which prevents latency and saves bandwidth.
+
+### 🛡️ Robustness
+
+gRPC empowers better relationships between clients and servers. The rules of communication are strictly enforced. That is not the case in REST calls, where the client and the server can send and receive anything they like and hopefully the other end understands what to do with it. In gRPC, to make changes to the communication, both client and server need to change accordingly. This prevents mistakes specially in microservice architectures.
+
+### 🔍 Debuggability
+
+gRPC requests are re-using the same context and can be tracked or traced across multiple service boundaries.
+This helps to identify slow calls and see what is causing delays. It is possible to cancel requests which cancels
+them on all involved services.
+
+### 📦 Microservices
+
+gRPC has been evolving and has become the best option for communication between microservices because of its unmatched
+performance and its polyglot nature. One of the biggest strengths of microservices is the freedom of programming
+languages and technologies. By using gRPC we can leverage all the advantages of strictly enforced communication
+standards combined with freedom of choice between different programming languages - whichever would fit best.
+
+:::info gRPC Advantages
+
+- http/2
+- protocol buffers
+- reusable connections
+- multi language support
+
+:::
+
+## CS3 APIs
+
+![CS3 Organization](/img/cs3org.png)
+
+The [CS3 APIs](https://github.com/cs3org/cs3apis) connect storages and application providers.
+
+The CS3 APIs follow Google and Uber API design guidelines, specially on error handling and naming convention. You can read more about these
+guidelines at [Google Api Design](https://cloud.google.com/apis/design) and [Uber Protocol](https://github.com/uber/prototool/blob/dev/style/README.md).
+
+The CS3 APIs use [Protocol Buffers version 3 (proto3)](https://github.com/protocolbuffers/protobuf) as their
+Interface Definition Language (IDL) to define the API interface and the structure of the payload messages.
diff --git a/versioned_docs/version-7.x/dev/server/apis/http/authorization.md b/versioned_docs/version-7.x/dev/server/apis/http/authorization.md
new file mode 100644
index 000000000..d215dadf0
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/apis/http/authorization.md
@@ -0,0 +1,142 @@
+---
+title: Authorization
+sidebar_position: 40
+---
+
+In its default configuration, OpenCloud supports three authentication methods as outlined on the [OIDC official site](https://openid.net/specs/openid-connect-core-1_0.html#rfc.section.3):
+
+1. Authorization Code Flow
+2. Implicit Flow
+3. Hybrid Flow
+
+For detailed information on OpenCloud's support for OpenID Connect (OIDC), please consult the [Official Documentation](../../../../admin/configuration/authentication-and-user-management/).
+
+While selecting an OpenCloud client for authentication, take note of specific limitations such as the `Redirect URI`:
+
+| Source  | Redirect URI                                 |
+| ------- | -------------------------------------------- |
+| Android | oc://android.opencloud.eu                    |
+| iOS     | oc://ios.opencloud.eu                        |
+| Desktop | `http://127.0.0.1` <br /> `http://localhost` |
+
+In this example, the desktop app's `client_id` are being used.
+
+```bash
+client_id=OpenCloudDesktop
+```
+
+## Authorization Code Flow
+
+1. Requesting authorization
+
+   To initiate the OIDC Code Flow, you can use tools like curl and a web browser.
+   The user should be directed to a URL to authenticate and give their consent (bypassing consent is against the standard):
+
+   ```plaintext
+   https://cloud.opencloud.test/signin/v1/identifier/_/authorize?client_id=client_id&scope=openid+profile+email+offline_access&response_type=code&redirect_uri=http://path-to-redirect-uri
+   ```
+
+   After a successful authentication, the browser will redirect to a URL that looks like this:
+
+   ```plaintext
+   http://path-to-redirect-uri?code=mfWsjEL0mc8gx0ftF9LFkGb__uFykaBw&scope=openid%20profile%20email%20offline_access&session_state=32b08dd...&state=
+   ```
+
+   For the next step extract the code from the URL.
+
+   In the above example,
+   the code is `mfWsjEL0mc8gx0ftF9LFkGb__uFykaBw`
+
+2. Requesting an access token
+
+   The next step in the OIDC Code Flow involves an HTTP POST request
+   to the token endpoint of the **OpenCloud Identity Server**.
+
+   ```bash
+   curl -vk -X POST https://cloud.opencloud.test/konnect/v1/token \
+   -d "grant_type=authorization_code" \
+   -d "code=3a3PTcO-WWXfN3l1mDN4u7G5PzWFxatU" \
+   -d "redirect_uri=http:path-to-redirect-uri" \
+   -d "client_id=client_id"
+   ```
+
+   Response looks like this:
+
+   ```json
+   {
+     "access_token": "eyJhbGciOid...",
+     "token_type": "Bearer",
+     "id_token": "eyJhbGciOi...",
+     "refresh_token": "eyJhbGciOiJ...",
+     "expires_in": 300
+   }
+   ```
+
+3. Refreshing an access token
+
+   If the access token has expired, you can get a new one using the refresh token.
+
+   ```bash
+   curl -vk -X POST https://cloud.opencloud.test/konnect/v1/token \
+   -d "grant_type=refresh_token" \
+   -d "refresh_token=eyJhbGciOiJ..." \
+   -d "redirect_uri=http://path-to-redirect-uri" \
+   -d "client_id=client_id"
+   ```
+
+   Response looks like this:
+
+   ```json
+   {
+     "access_token": "eyJhbGciOi...",
+     "token_type": "Bearer",
+     "expires_in": 300
+   }
+   ```
+
+## Implicit Code Flow
+
+When using the implicit flow, tokens are provided in a URI fragment of the redirect URL.
+Valid values for the `response_type` request parameter are:
+
+- token
+- id_token token
+
+:::warning Important Warning
+If you are using the implicit flow, `nonce` parameter is required in the initial `/authorize` request.
+`nonce=pL3UkpAQPZ8bTMGYOmxHY/dQABin8yrqipZ7iN0PY18=`
+
+bash command to generate cryptographically random value
+
+```bash
+openssl rand -base64 32
+```
+
+:::
+The user should be directed to a URL to authenticate and give their consent (bypassing consent is against the standard):
+
+```bash
+https://cloud.opencloud.test/signin/v1/identifier/_/authorize?client_id=client_id&scope=openid+profile+email+offline_access&response_type=id_token+token&redirect_uri=http://path-to-redirect-uri&nonce=pL3UkpAQPZ8bTMGYOmxHY/dQABin8yrqipZ7iN0PY18=
+```
+
+After a successful authentication, the browser will redirect to a URL that looks like this:
+
+```bash
+http://path-to-redirect-uri#access_token=eyJhbGciOiJQUzI...&expires_in=300&id_token=eyJhbGciOiJ...&scope=email%20openid%20profile&session_state=c8a1019f5e054d...&state=&token_type=Bearer
+```
+
+For the next step, extract the access_token from the URL.
+
+```bash
+access_token = 'eyJhbGciOiJQ...'
+```
+
+## Hybrid Flow
+
+The Hybrid Flow in OpenID Connect melds features from both the Implicit and Authorization Code flows. It allows clients to directly retrieve certain tokens from the Authorization Endpoint, yet also offers the option to acquire additional tokens from the Token Endpoint.
+
+The Authorization Server redirects back to the client with appropriate parameters in the response, based on the value of the response_type request parameter:
+
+- code token
+- code id_token
+- code id_token token
diff --git a/versioned_docs/version-7.x/dev/server/apis/http/graph/groups.md b/versioned_docs/version-7.x/dev/server/apis/http/graph/groups.md
new file mode 100644
index 000000000..e2b16100f
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/apis/http/graph/groups.md
@@ -0,0 +1,269 @@
+---
+title: Groups
+sidebar_position: 40
+---
+
+## Groups API
+
+The Groups API is implementing a subset of the functionality of the
+[MS Graph Group resource](https://docs.microsoft.com/en-us/graph/api/resources/group?view=graph-rest-1.0)
+The JSON representation of a Group as handled by the Groups API looks like this:
+
+```json
+{
+  "displayName": "group",
+  "id": "f0d97060-da16-4b0d-9fa4-d1ec43afc5f1"
+}
+```
+
+Our implementation currently supports two Attributes for a Group:
+
+| Attribute   | Description                                                                                                                 |
+| ----------- | --------------------------------------------------------------------------------------------------------------------------- |
+| displayName | The groups name                                                                                                             |
+| id          | An unique, stable readonly identifier for the group that stays the same for the whole lifetime of the Group, usually a UUID |
+
+### Reading groups
+
+#### `GET /groups`
+
+Returns a list of all groups
+
+Example:
+
+```bash
+curl -k 'https://localhost:9200/graph/v1.0/groups' -u user:password
+
+```
+
+Response:
+
+```json
+{
+  "value": [
+    {
+      "displayName": "group",
+      "id": "38580a2e-7018-42ed-aff6-b2af0b4e9790"
+    },
+    {
+      "displayName": "Example Users",
+      "id": "7a20f238-8a22-4458-902d-47674c317e5f"
+    }
+  ]
+}
+```
+
+#### `GET /groups?$expand=members`
+
+Returns a list of all groups including its members
+
+Example:
+
+```bash
+curl -k 'https://localhost:9200/graph/v1.0/groups?$expand=members' -u user:password
+
+```
+
+Response:
+
+```json
+{
+  "value": [
+    {
+      "displayName": "group",
+      "id": "38580a2e-7018-42ed-aff6-b2af0b4e9790",
+      "members": [
+        {
+          "displayName": "user1",
+          "id": "2e7b7e23-6c42-4d34-81b0-2bed34e51983",
+          "mail": "user1@example.org",
+          "onPremisesSamAccountName": "user1"
+        },
+        {
+          "displayName": "user2",
+          "id": "b45c9e35-0d95-4165-96bc-68bff4a316ed",
+          "mail": "user2@example.org",
+          "onPremisesSamAccountName": "user2"
+        }
+      ]
+    },
+    {
+      "displayName": "Example Users",
+      "id": "7a20f238-8a22-4458-902d-47674c317e5f",
+      "members": [
+        {
+          "displayName": "user3",
+          "id": "026fbfef-79ef-4f5d-887b-9eaf42777239",
+          "mail": "user3@example.org",
+          "onPremisesSamAccountName": "user3"
+        }
+      ]
+    }
+  ]
+}
+```
+
+#### `GET /groups/{groupid}`
+
+Example:
+
+```bash
+curl -k 'https://localhost:9200/graph/v1.0/groups/7a20f238-8a22-4458-902d-47674c317e5f' -u user:password
+```
+
+Response:
+
+```json
+{
+  "displayName": "Example Users",
+  "id": "7a20f238-8a22-4458-902d-47674c317e5f"
+}
+```
+
+#### `GET /groups/{groupid}?$expand=members`
+
+Example:
+
+```bash
+curl -k 'https://localhost:9200/graph/v1.0/groups/7a20f238-8a22-4458-902d-47674c317e5f?$expand=members' -u user:password
+```
+
+Response:
+
+```json
+{
+  "displayName": "Example Users",
+  "id": "7a20f238-8a22-4458-902d-47674c317e5f",
+  "members": [
+    {
+      "displayName": "user3",
+      "id": "026fbfef-79ef-4f5d-887b-9eaf42777239",
+      "mail": "user3@example.org",
+      "onPremisesSamAccountName": "user3"
+    }
+  ]
+}
+```
+
+### Getting Group Members
+
+#### `GET /groups/{groupid}/members`
+
+Returns a list of User objects that are members of a group.
+
+Example:
+
+```bash
+curl -k 'https://localhost:9200/graph/v1.0/groups/7a20f238-8a22-4458-902d-47674c317e5f/members' -u user:password
+
+```
+
+Response:
+
+```json
+[
+  {
+    "displayName": "Test User",
+    "id": "c54b0588-7157-4521-bb52-c1c8ca84ea71",
+    "mail": "example@example.org",
+    "onPremisesSamAccountName": "example"
+  },
+  {
+    "displayName": "Dennis Ritchie",
+    "id": "4c510ada-c86b-4815-8820-42cdf82c3d51",
+    "mail": "dennis@example.org",
+    "onPremisesSamAccountName": "dennis"
+  }
+]
+```
+
+### Creating / Updating Groups
+
+#### `POST /groups`
+
+Use this to create a new group.
+
+##### Request Body
+
+Note the missing `"id"` Attribute. It will be generated by the server:
+
+```json
+{
+  "displayName": "Example Users"
+}
+```
+
+##### Response
+
+When successful, the response will return the new group including the newly allocated `"id"`:
+
+```json
+{
+  "displayName": "Example Users",
+  "id": "7a20f238-8a22-4458-902d-47674c317e5f"
+}
+```
+
+#### `DELETE /groups/{id}`
+
+Example:
+
+```bash
+curl -k --request DELETE 'https://localhost:9200/graph/v1.0/groups/7a20f238-8a22-4458-902d-47674c317e5f' -u user:password
+```
+
+When successful the API returns no response body and the HTTP status code 204 (No Content)
+
+#### `PATCH /groups/\{id\}`
+
+Updating attributes of a single group is supposed to be done with a patch request. This is however currently not fully
+implemented for our write-enabled backends. The PATCH request can however be used to add multiple members to a group at once.
+See below.
+
+### Adding a single member to a group
+
+#### `POST /groups/{id}/members/$ref`
+
+The request body contains a single attribute "`@odata.id`" referencing the new member of the group by URI. Example:
+
+```bash
+curl -k --header "Content-Type: application/json" \
+        --request POST  --data \
+ '{ "@odata.id": "https://localhost:9200/graph/v1.0/users/4c510ada-c86b-4815-8820-42cdf82c3d51" }' \
+ 'https://localhost:9200/graph/v1.0/groups/7a20f238-8a22-4458-902d-47674c317e5f/members/$ref' -u user:password
+
+```
+
+When successful the API returns no response body and the HTTP status code 204 (No Content)
+
+### Adding multiple members in a single request
+
+#### `PATCH /groups/\{id\}`
+
+The request body contains the attribute `members@odata.bind` holding a list of URI references for the new members.
+Example:
+
+```json
+{
+  "members@odata.bind": [
+    "https://localhost:9200/graph/v1.0/users/4c510ada-c86b-4815-8820-42cdf82c3d51",
+    "https://localhost:9200/graph/v1.0/users/c54b0588-7157-4521-bb52-c1c8ca84ea71"
+  ]
+}
+```
+
+When successful the API returns no response body and the HTTP status code 204 (No Content)
+
+### Removing a member
+
+#### `DELETE /groups/{groupid}/members/{id}/$ref`
+
+Example
+
+```bash
+curl -k --request DELETE  \
+     'https://localhost:9200/graph/v1.0/groups/7a20f238-8a22-4458-902d-47674c317e5f/members/4c510ada-c86b-4815-8820-42cdf82c3d51/$ref' \
+     -u user:password
+```
+
+When successful the API returns no response body and the HTTP status code 204 (No Content)
diff --git a/versioned_docs/version-7.x/dev/server/apis/http/graph/index.md b/versioned_docs/version-7.x/dev/server/apis/http/graph/index.md
new file mode 100644
index 000000000..1ec976e1a
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/apis/http/graph/index.md
@@ -0,0 +1,78 @@
+---
+title: LibreGraph
+sidebar_position: 1
+---
+
+The LibreGraph API is a REST Api which is inspired by the [Microsoft Graph API](https://developer.microsoft.com/en-us/graph). It tries to stay compliant with the Microsoft Graph API and aims to be the Next Generation Api in OpenCloud where we want to support most of the features of the platform.
+The [API specification](https://github.com/opencloud-eu/libre-graph-api) is available in the OpenApi 3 standard and there are generated client and server [SDKs](https://github.com/opencloud-eu/libre-graph-api#clients) available. You can browse the API with the [Swagger UI](https://docs.opencloud.eu/swagger/libre-graph-api/).
+
+## Calling the LibreGraph API
+
+```sh
+{HTTP method} https://cloud.opencloud.test/graph/{version}/{resource}?{query-parameters}
+```
+
+The request component consists of:
+
+| Component            | Description                                                             |
+| -------------------- | ----------------------------------------------------------------------- |
+| `{HTTP method}`      | The HTTP method which is used in the request.                           |
+| `{version}`          | The version of the LibreGraph API used by the client.                   |
+| `{resource}`         | The LibreGraph Resource which the client is referencing in the request. |
+| `{query-parameters}` | Optional parameters for the request to customize the response.          |
+
+### HTTP methods
+
+| Method | Description                   |
+| ------ | ----------------------------- |
+| GET    | Read data from a resource.    |
+| POST   | Create a new resource.        |
+| PATCH  | Update an existing resource.  |
+| PUT    | Replace an existing resource. |
+| DELETE | Delete an existing resource.  |
+
+The methods `GET` and `DELETE` need no request body. The methods `POST`, `PATCH` and `PUT` require a request body, normally in JSON format to provide the needed values.
+
+### Version
+
+OpenCloud currently provides the version `v1.0`.
+
+### Resource
+
+A resource could be an entity or a complex type and is usually defined by properties. Entities are always recognizable by an `Id` property. The URL contains the resource which you are interacting with e.g. `/me/drives` or `/groups/{group-id}`.
+
+Each resource could possibly require different permissions. Usually you need permissions on a higher level for creating or updating an existing resource than for reading.
+
+### Query parameters
+
+Query parameters can be OData system query options, or other strings that a method accepts to customize its response.
+
+You can use optional OData system query options to include more or fewer properties than the default response, filter the response for items that match a custom query, or provide additional parameters for a method.
+
+For example, adding the following filter parameter restricts the drives returned to only those with the driveType property of `project`.
+
+```shell
+GET https://cloud.opencloud.test/graph/v1.0/drives?$filter=driveType eq 'project'
+```
+
+For more information about OData query options please check the [API specification](https://github.com/opencloud-eu/libre-graph-api) and the provided examples.
+
+### Authorization
+
+For development purposes the examples in the developer documentation use Basic Auth. It is disabled by default and should only be enabled by setting `PROXY_ENABLE_BASIC_AUTH` in [the proxy](../../../services/proxy/env-vars.mdx) for development or test instances.
+
+To authenticate with a Bearer token or OpenID Connect access token replace the `-u user:password` Basic Auth option of curl with a `-H 'Authorization: Bearer <token>'` header. A `<token>` can be obtained by copying it from a request in the browser, although it will time out within minutes. To automatically refresh the OpenID Connect access token an ssh-agent like solution like [oidc-agent](https://github.com/indigo-dc/oidc-agent) should be used. The graph endpoints that support a preconfigured token can be found in the [API specification](https://github.com/opencloud-eu/libre-graph-api)
+
+#### Authorization with App token
+
+Users can create an App Token in their Open Cloud interface. This token can be used to authenticate a user using the Account Name for the username and the token as password. Here is an example using curl
+
+```sh
+curl 'https://cloud.opencloud.test/graph/v1.0/me' -H 'accept: application/json' -u 'accountname:the generated app token'
+
+# or using the Authentification Basic Header
+# Authentification: Basic BASE64(username + ':' + app token)
+curl 'https://cloud.opencloud.test/graph/v1.0/me' -H 'accept: application/json' -H 'Authorization: Basic YWNjb3VudG5hbWU6dGhlIGdlbmVyYXRlZCBhcHAgdG9rZW4='
+```
+
+## Resources
diff --git a/versioned_docs/version-7.x/dev/server/apis/http/graph/permissions.md b/versioned_docs/version-7.x/dev/server/apis/http/graph/permissions.md
new file mode 100644
index 000000000..74127dff3
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/apis/http/graph/permissions.md
@@ -0,0 +1,170 @@
+---
+title: Permissions
+sidebar_position: 50
+---
+
+## Permissions API
+
+The Permissions API is implementing a subset of the functionality of the
+[MS Graph Permission resource](https://learn.microsoft.com/en-us/graph/api/resources/permission?view=graph-rest-1.0).
+
+### Example Permissions
+
+The JSON representation of a Drive, as handled by the Spaces API, looks like this:
+
+```json
+{
+  "@libre.graph.permissions.roles.allowedValues": [
+    {
+      "id": "b1e2218d-eef8-4d4c-b82d-0f1a1b48f3b5",
+      "description": "Allows reading the shared file or folder",
+      "displayName": "Viewer",
+      "@libre.graph.weight": 1
+    },
+    {
+      "id": "fb6c3e19-e378-47e5-b277-9732f9de6e21",
+      "description": "Allows reading and writing the shared file or folder",
+      "displayName": "Editor",
+      "@libre.graph.weight": 2
+    },
+    {
+      "id": "312c0871-5ef7-4b3a-85b6-0e4074c64049",
+      "description": "Allows managing a space",
+      "displayName": "Manager",
+      "@libre.graph.weight": 3
+    },
+    {
+      "id": "4916f47e-66d5-49bb-9ac9-748ad00334b",
+      "description": "Allows creating new files",
+      "displayName": "File Drop",
+      "@libre.graph.weight": 4
+    }
+  ],
+  "@libre.graph.permissions.actions.allowedValues": [
+    "libre.graph/driveItem/basic/read",
+    "libre.graph/driveItem/permissions/read",
+    "libre.graph/driveItem/upload/create",
+    "libre.graph/driveItem/standard/allTasks",
+    "libre.graph/driveItem/upload/create"
+  ],
+  "value": [
+    {
+      "id": "67445fde-a647-4dd4-b015-fc5dafd2821d",
+      "link": {
+        "type": "view",
+        "webUrl": "https://cloud.example.org/s/fhGBMIkKFEHWysj"
+      }
+    },
+    {
+      "id": "34646ab6-be32-43c9-89e6-987e0c237e9b",
+      "roles": ["b1e2218d-eef8-4d4c-b82d-0f1a1b48f3b5"],
+      "grantedToV2": [
+        {
+          "user": {
+            "id": "4c510ada-c86b-4815-8820-42cdf82c3d51",
+            "displayName": "Dennis Ritchie"
+          }
+        }
+      ]
+    },
+    {
+      "id": "81d5bad3-3eff-410a-a2ea-eda2d14d4474",
+      "roles": ["b1e2218d-eef8-4d4c-b82d-0f1a1b48f3b5"],
+      "grantedToV2": [
+        {
+          "user": {
+            "id": "4c510ada-c86b-4815-8820-42cdf82c3d51",
+            "displayName": "Dennis Ritchie"
+          }
+        }
+      ]
+    },
+    {
+      "id": "b470677e-a7f5-4304-8ef5-f5056a21fff1",
+      "roles": ["b1e2218d-eef8-4d4c-b82d-0f1a1b48f3b5"],
+      "grantedToV2": [
+        {
+          "user": {
+            "id": "f7fbf8c8-139b-4376-b307-cf0a8c2d0d9c",
+            "displayName": "Alan Turing"
+          }
+        }
+      ]
+    },
+    {
+      "id": "453b02be-4ec2-4e7d-b576-09fc153de812",
+      "roles": ["fb6c3e19-e378-47e5-b277-9732f9de6e21"],
+      "grantedToV2": [
+        {
+          "user": {
+            "id": "4c510ada-c86b-4815-8820-42cdf82c3d51",
+            "displayName": "Dennis Ritchie"
+          }
+        }
+      ],
+      "expirationDateTime": "2018-07-15T14:00:00.000Z"
+    },
+    {
+      "id": "86765c0d-3905-444a-9b07-76201f8cf7df",
+      "roles": ["312c0871-5ef7-4b3a-85b6-0e4074c64049"],
+      "grantedToV2": [
+        {
+          "group": {
+            "id": "167cbee2-0518-455a-bfb2-031fe0621e5d",
+            "displayName": "Programmers"
+          }
+        }
+      ]
+    },
+    {
+      "id": "c42b5cbd-2d65-42cf-b0b6-fb6d2b762256",
+      "grantedToV2": [
+        {
+          "user": {
+            "id": "4c510ada-c86b-4815-8820-42cdf82c3d51",
+            "displayName": "Dennis Ritchie"
+          }
+        }
+      ],
+      "@libre.graph.permissions.actions": [
+        "libre.graph/driveItem/basic/read",
+        "libre.graph/driveItem/path/update"
+      ]
+    }
+  ]
+}
+```
+
+## Creating Share Invitation / Link
+
+### Create a link share `POST /drives/{drive-id}/items/{item-id}/createLink`
+
+[CreateLink](https://docs.opencloud.eu/swagger/libre-graph-api/#/drives.permissions/CreateLink)
+
+### Create a user/group share `POST /drives/{drive-id}/items/{item-id}/invite`
+
+[Invite](https://docs.opencloud.eu/swagger/libre-graph-api/#/drives.permissions/Invite)
+
+## Reading Permissions
+
+### List the effective sharing permissions on a driveitem `GET /drives/{drive-id}/items/{item-id}/permissions`
+
+[ListPermissions](https://docs.opencloud.eu/swagger/libre-graph-api/#/drives.permissions/ListPermissions)
+
+### List Get sharing permission for a file or folder `GET /drives/{drive-id}/items/{item-id}/permissions/{perm-id}`
+
+[GetPermission](https://docs.opencloud.eu/swagger/libre-graph-api/#/drives.permissions/GetPermission)
+
+## Updating Permissions
+
+### Updating sharing permission `POST /drives/{drive-id}/items/{item-id}/permissions/{perm-id}`
+
+[UpdatePermission](https://docs.opencloud.eu/swagger/libre-graph-api/#/drives.permissions/UpdatePermission)
+
+### Set password of permission `POST /drives/{drive-id}/items/{item-id}/permissions/{perm-id}/setPassword`
+
+[SetPermissionPassword](https://docs.opencloud.eu/swagger/libre-graph-api/#/drives.permissions/SetPermissionPassword)
+
+### Deleting permission `DELETE /drives/{drive-id}/items/{item-id}/permissions/{perm-id}`
+
+[DeletePermission](https://docs.opencloud.eu/swagger/libre-graph-api/#/drives.permissions/DeletePermission)
diff --git a/versioned_docs/version-7.x/dev/server/apis/http/graph/role.md b/versioned_docs/version-7.x/dev/server/apis/http/graph/role.md
new file mode 100644
index 000000000..a06781a57
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/apis/http/graph/role.md
@@ -0,0 +1,33 @@
+---
+title: Role
+sidebar_position: 60
+---
+
+## Role API
+
+The Roles API is implementing a subset of the functionality of the
+[MS Graph Role Management](https://learn.microsoft.com/en-us/graph/api/resources/rolemanagement?view=graph-rest-1.0).
+
+## Role Management
+
+### List roleDefinitions `GET /v1beta1/roleManagement/permissions/roleDefinitions`
+
+[ListPermissionRoleDefinitions](https://docs.opencloud.eu/swagger/libre-graph-api/#/roleManagement/ListPermissionRoleDefinitions)
+
+### Get unifiedRoleDefinition `GET /drives/{drive-id}/items/{item-id}/permissions/{perm-id}`
+
+[GetPermissionRoleDefinition](https://docs.opencloud.eu/swagger/libre-graph-api/#/roleManagement/GetPermissionRoleDefinition)
+
+## Role Assignment
+
+### Get appRoleAssignments of a user `GET /v1.0/users/{user-id}/appRoleAssignments`
+
+[ListAppRoleAssignments](https://docs.opencloud.eu/swagger/libre-graph-api/#/user.appRoleAssignment/user.ListAppRoleAssignments)
+
+### Grant an appRoleAssignment to a user `POST /v1.0/users/{user-id}/appRoleAssignments`
+
+[CreateAppRoleAssignments](https://docs.opencloud.eu/swagger/libre-graph-api/#/user.appRoleAssignment/user.CreateAppRoleAssignments)
+
+### Delete the appRoleAssignment from a user `DELETE /v1.0/users/{user-id}/appRoleAssignments/{appRoleAssignment-id}`
+
+[DeleteAppRoleAssignments](https://docs.opencloud.eu/swagger/libre-graph-api/#/user.appRoleAssignment/user.DeleteAppRoleAssignments)
diff --git a/versioned_docs/version-7.x/dev/server/apis/http/graph/spaces.md b/versioned_docs/version-7.x/dev/server/apis/http/graph/spaces.md
new file mode 100644
index 000000000..526507a15
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/apis/http/graph/spaces.md
@@ -0,0 +1,491 @@
+---
+title: Spaces
+sidebar_position: 20
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+## Spaces API
+
+The Spaces API is implementing a subset of the functionality of the
+[MS Graph Drives resource](https://learn.microsoft.com/en-us/graph/api/resources/drive?view=graph-rest-1.0).
+
+### Example Space
+
+The JSON representation of a Drive, as handled by the Spaces API, looks like this:
+
+```json
+{
+  "driveAlias": "project/mars",
+  "driveType": "project",
+  "id": "storage-users-1$89ad5ad2-5fdb-4877-b8c9-601a9670b925",
+  "lastModifiedDateTime": "2023-01-24T21:19:26.417055+01:00",
+  "name": "Mars",
+  "owner": {
+    "user": {
+      "displayName": "",
+      "id": "89ad5ad2-5fdb-4877-b8c9-601a9670b925"
+    }
+  },
+  "quota": {
+    "remaining": 999853685,
+    "state": "normal",
+    "total": 1000000000,
+    "used": 146315
+  },
+  "root": {
+    "eTag": "\"910af0061161c42d8d1224df6c4a2527\"",
+    "id": "storage-users-1$89ad5ad2-5fdb-4877-b8c9-601a9670b925",
+    "permissions": [
+      {
+        "grantedToIdentities": [
+          {
+            "user": {
+              "displayName": "Admin",
+              "id": "some-admin-user-id-0000-000000000000"
+            }
+          }
+        ],
+        "roles": ["manager"]
+      }
+    ],
+    "webDavUrl": "https://localhost:9200/dav/spaces/storage-users-1$89ad5ad2-5fdb-4877-b8c9-601a9670b925"
+  },
+  "special": [
+    {
+      "eTag": "\"f97829324f63ce778095334cfeb0097b\"",
+      "file": {
+        "mimeType": "image/jpeg"
+      },
+      "id": "storage-users-1$89ad5ad2-5fdb-4877-b8c9-601a9670b925!40171bea-3263-47a8-80ef-0ca20c37f45a",
+      "lastModifiedDateTime": "2022-02-15T17:11:50.000000496+01:00",
+      "name": "Mars_iStock-MR1805_20161221.jpeg",
+      "size": 146250,
+      "specialFolder": {
+        "name": "image"
+      },
+      "webDavUrl": "https://localhost:9200/dav/spaces/storage-users-1$89ad5ad2-5fdb-4877-b8c9-601a9670b925%2189ad5ad2-5fdb-4877-b8c9-601a9670b925/.space/Mars_iStock-MR1805_20161221.jpeg"
+    },
+    {
+      "eTag": "\"ff38b31d8f109a4fbb98ab34499a3379\"",
+      "file": {
+        "mimeType": "text/markdown"
+      },
+      "id": "storage-users-1$89ad5ad2-5fdb-4877-b8c9-601a9670b925!e2167612-7578-46e2-8ed7-971481037bc1",
+      "lastModifiedDateTime": "2023-01-24T21:10:23.661841+01:00",
+      "name": "readme.md",
+      "size": 65,
+      "specialFolder": {
+        "name": "readme"
+      },
+      "webDavUrl": "https://localhost:9200/dav/spaces/storage-users-1$89ad5ad2-5fdb-4877-b8c9-601a9670b925%2189ad5ad2-5fdb-4877-b8c9-601a9670b925/.space/readme.md"
+    }
+  ],
+  "webUrl": "https://localhost:9200/f/storage-users-1$89ad5ad2-5fdb-4877-b8c9-601a9670b925"
+}
+```
+
+## Creating Spaces
+
+### Create a single space `POST /drives`
+
+[Create Drive](https://docs.opencloud.eu/swagger/libre-graph-api/#/drives/CreateDrive)
+
+### Create a space item (Enable sync) `POST /drives/\{drive-id\}/root/children`
+
+[Create Drive Item](https://docs.opencloud.eu/swagger/libre-graph-api/#/drives.root/CreateDriveItem)
+
+## Reading Spaces
+
+```shell
+GET https://cloud.opencloud.test/graph/{version}/{me/}drives/?{query-parameters}
+```
+
+| Component            | Description                                                                                                            |
+| -------------------- | ---------------------------------------------------------------------------------------------------------------------- |
+| \{version\}          | The version of the LibreGraph API used by the client.                                                                  |
+| \{/me\}              | The `me` component of the part is optional. If used, you only see spaces where the acting user is a regular member of. |
+| \{query-parameters\} | Optional parameters for the request to customize the response.                                                         |
+
+### List all spaces `GET /drives`
+
+Returns a list of all available spaces, even ones where the acting user is not a regular member of. You need elevated permissions to do list all spaces. If you don't have the elevated permissions, the result is the same like `GET /me/drives`.
+
+:::info[Multiple Administration Personas]
+
+The openCloud spaces concept draws a strict line between users which can work with the content of a space and others who have the permission to manage the space. A user which is able to manage quota and space metadata does not necessarily need to be able to access the content of a space.
+
+**Space Admin**\
+There is a global user role "Space Admin" which grants users some global permissions to manage space quota and some space metadata. This Role enables the user also to disable, restore and delete spaces. He cannot manage space members.
+
+**Space Manager**\
+The "Space Manager" is a user which is a regular member of a space because he has been invited. In addition to being part of a space the user can also manage the memberships of the space.
+
+:::
+
+### List My Spaces `GET /me/drives`
+
+[List My Drives](https://docs.opencloud.eu/swagger/libre-graph-api/#/me.drives/ListMyDrives)
+
+## Modifying Spaces
+
+Modify the properties of a space. You need elevated permissions to execute this request.
+
+### Set the space quota to 5GB `PATCH /drives/\{drive-id\}`
+
+To limit the quota of a space you need to set the `quota.total` value. The API response will give back all actual quota properties.
+
+```json
+{
+  "quota": {
+    "remaining": 5368709120,
+    "state": "normal",
+    "total": 5368709120,
+    "used": 0
+  }
+}
+```
+
+| Attribute | Description                                                                                                                                                                                                |
+| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| remaining | The remaining disk space in `bytes`. If the quota is not limited, this will show the total available disk space.                                                                                           |
+| state     | The state of the space in regards to quota usage. This can be used for visual indicators. It can be `normal`(\<75%), `nearing`(between 75% and 89%), `critical`(between 90% and 99%) and `exceeded`(100%). |
+| total     | The space id. The value needs to be a space ID.                                                                                                                                                            |
+| used      | The used disk space in bytes.                                                                                                                                                                              |
+
+<Tabs>
+<TabItem value="request" label="Request">
+
+```shell
+curl -L -k -X PATCH 'https://localhost:9200/graph/v1.0/drives/storage-users-1$535aa42d-a3c7-4329-9eba-5ef48fcaa3ff' \
+-H 'Content-Type: application/json' \
+--data-raw '{
+    "quota": {
+        "total": 5368709120
+    }
+}'
+```
+
+</TabItem>
+<TabItem value="response" label="Response - 200 OK">
+
+```json title="Response" {17}
+{
+  "description": "Marketing team resources",
+  "driveAlias": "project/marketing",
+  "driveType": "project",
+  "id": "storage-users-1$535aa42d-a3c7-4329-9eba-5ef48fcaa3ff",
+  "lastModifiedDateTime": "2023-01-18T17:13:48.385204589+01:00",
+  "name": "Marketing",
+  "owner": {
+    "user": {
+      "displayName": "",
+      "id": "535aa42d-a3c7-4329-9eba-5ef48fcaa3ff"
+    }
+  },
+  "quota": {
+    "remaining": 5368709120,
+    "state": "normal",
+    "total": 5368709120,
+    "used": 0
+  },
+  "root": {
+    "eTag": "\"f91e56554fd9305db81a93778c0fae96\"",
+    "id": "storage-users-1$535aa42d-a3c7-4329-9eba-5ef48fcaa3ff",
+    "permissions": [
+      {
+        "grantedToIdentities": [
+          {
+            "user": {
+              "displayName": "Admin",
+              "id": "some-admin-user-id-0000-000000000000"
+            }
+          }
+        ],
+        "roles": ["manager"]
+      }
+    ],
+    "webDavUrl": "https://localhost:9200/dav/spaces/storage-users-1$535aa42d-a3c7-4329-9eba-5ef48fcaa3ff"
+  },
+  "webUrl": "https://localhost:9200/f/storage-users-1$535aa42d-a3c7-4329-9eba-5ef48fcaa3ff"
+}
+```
+
+</TabItem>
+</Tabs>
+
+### Change the space name, subtitle and alias `PATCH /drives/\{drive-id\}`
+
+You can change multiple space properties in one request as long as you submit a valid JSON body. Please be aware that some properties need different permissions.
+
+<Tabs>
+<TabItem value="request" label="Request">
+```shell
+curl -L -k -X PATCH 'https://localhost:9200/graph/v1.0/drives/storage-users-1$535aa42d-a3c7-4329-9eba-5ef48fcaa3ff' \
+-H 'Content-Type: application/json' \
+--data-raw '{
+    "name": "Mars",
+    "description": "Mission to mars",
+    "driveAlias": "project/mission-to-mars"
+}'
+```
+</TabItem>
+
+<TabItem value="response" label="Response - 200 OK">
+
+```json title="Response" {2,3,7}
+{
+  "description": "Mission to mars",
+  "driveAlias": "project/mission-to-mars",
+  "driveType": "project",
+  "id": "storage-users-1$535aa42d-a3c7-4329-9eba-5ef48fcaa3ff",
+  "lastModifiedDateTime": "2023-01-19T14:17:36.094283+01:00",
+  "name": "Mars",
+  "owner": {
+    "user": {
+      "displayName": "",
+      "id": "535aa42d-a3c7-4329-9eba-5ef48fcaa3ff"
+    }
+  },
+  "quota": {
+    "remaining": 15,
+    "state": "normal",
+    "total": 15,
+    "used": 0
+  },
+  "root": {
+    "eTag": "\"f5fee4fdfeedd6f98956500779eee15e\"",
+    "id": "storage-users-1$535aa42d-a3c7-4329-9eba-5ef48fcaa3ff",
+    "permissions": [
+      {
+        "grantedToIdentities": [
+          {
+            "user": {
+              "displayName": "Admin",
+              "id": "some-admin-user-id-0000-000000000000"
+            }
+          }
+        ],
+        "roles": ["manager"]
+      }
+    ],
+    "webDavUrl": "https://localhost:9200/dav/spaces/storage-users-1$535aa42d-a3c7-4329-9eba-5ef48fcaa3ff"
+  },
+  "webUrl": "https://localhost:9200/f/storage-users-1$535aa42d-a3c7-4329-9eba-5ef48fcaa3ff"
+}
+```
+
+</TabItem>
+</Tabs>
+
+## Disabling / Deleting Spaces
+
+### Disable a space `DELETE /drives/\{drive-id\}`
+
+This operation will make the space content unavailable for all space members. No data will be deleted.
+
+<Tabs>
+<TabItem value="request" label="Request">
+
+```shell
+curl -L -k -X DELETE 'https://localhost:9200/graph/v1.0/drives/storage-users-1$535aa42d-a3c7-4329-9eba-5ef48fcaa3ff/'
+```
+
+</TabItem>
+
+<TabItem value="response" label="Response - 204 No Content">
+
+This response has no body value.
+
+A disabled space will appear in listings with a `root.deleted.state=trashed` property. The space description and the space image will not be readable anymore.
+
+```json title="Response" {18,19,20}
+{
+  "description": "Marketing team resources",
+  "driveAlias": "project/marketing",
+  "driveType": "project",
+  "id": "storage-users-1$535aa42d-a3c7-4329-9eba-5ef48fcaa3ff",
+  "lastModifiedDateTime": "2023-01-19T14:17:36.094283+01:00",
+  "name": "Marketing",
+  "owner": {
+    "user": {
+      "displayName": "",
+      "id": "535aa42d-a3c7-4329-9eba-5ef48fcaa3ff"
+    }
+  },
+  "quota": {
+    "total": 15
+  },
+  "root": {
+    "deleted": {
+      "state": "trashed"
+    },
+    "eTag": "\"f5fee4fdfeedd6f98956500779eee15e\"",
+    "id": "storage-users-1$535aa42d-a3c7-4329-9eba-5ef48fcaa3ff",
+    "permissions": [
+      {
+        "grantedToIdentities": [
+          {
+            "user": {
+              "displayName": "Admin",
+              "id": "some-admin-user-id-0000-000000000000"
+            }
+          }
+        ],
+        "roles": ["manager"]
+      }
+    ],
+    "webDavUrl": "https://localhost:9200/dav/spaces/storage-users-1$535aa42d-a3c7-4329-9eba-5ef48fcaa3ff"
+  },
+  "webUrl": "https://localhost:9200/f/storage-users-1$535aa42d-a3c7-4329-9eba-5ef48fcaa3ff"
+}
+```
+
+</TabItem>
+</Tabs>
+
+### Restore a space `PATCH /drives/\{drive-id\}`
+
+This operation will make the space content available again to all members. No content will be changed.
+
+To restore a space, the Header `Restore: T` needs to be set.
+<Tabs>
+<TabItem value="request" label="Request">
+
+```shell
+curl -L -X PATCH 'https://localhost:9200/graph/v1.0/drives/storage-users-1$535aa42d-a3c7-4329-9eba-5ef48fcaa3ff/' \
+-H 'Restore: T' \
+-H 'Content-Type: text/plain' \
+--data-raw '{}'
+```
+
+:::info[Body value]
+
+This request needs an empty body (--data-raw '{}') to fulfil the standard libregraph specification even when the body is not needed.
+
+:::
+</TabItem>
+
+<TabItem value="response" label="Response - 200 OK">
+
+```json
+{
+  "description": "Marketing team resources",
+  "driveAlias": "project/marketing",
+  "driveType": "project",
+  "id": "storage-users-1$535aa42d-a3c7-4329-9eba-5ef48fcaa3ff",
+  "lastModifiedDateTime": "2023-01-19T14:17:36.094283+01:00",
+  "name": "Marketing",
+  "owner": {
+    "user": {
+      "displayName": "",
+      "id": "535aa42d-a3c7-4329-9eba-5ef48fcaa3ff"
+    }
+  },
+  "quota": {
+    "remaining": 15,
+    "state": "normal",
+    "total": 15,
+    "used": 0
+  },
+  "root": {
+    "eTag": "\"f5fee4fdfeedd6f98956500779eee15e\"",
+    "id": "storage-users-1$535aa42d-a3c7-4329-9eba-5ef48fcaa3ff",
+    "permissions": [
+      {
+        "grantedToIdentities": [
+          {
+            "user": {
+              "displayName": "Admin",
+              "id": "some-admin-user-id-0000-000000000000"
+            }
+          }
+        ],
+        "roles": ["manager"]
+      }
+    ],
+    "webDavUrl": "https://localhost:9200/dav/spaces/storage-users-1$535aa42d-a3c7-4329-9eba-5ef48fcaa3ff"
+  },
+  "webUrl": "https://localhost:9200/f/storage-users-1$535aa42d-a3c7-4329-9eba-5ef48fcaa3ff"
+}
+```
+
+</TabItem>
+</Tabs>
+
+### Permanently delete a space `DELETE /drives/\{drive-id\}`
+
+This operation will delete a space and all its data permanently. This is restricted to spaces which are already disabled.
+
+To delete a space, the Header `Purge: T` needs to be set.
+
+<Tabs>
+<TabItem value="request" label="Request">
+
+```shell title="Request" {2}
+curl -L -X DELETE 'https://localhost:9200/graph/v1.0/drives/storage-users-1$535aa42d-a3c7-4329-9eba-5ef48fcaa3ff' \
+-H 'Purge: T'
+```
+
+:::warning[Data will be deleted]
+
+This request will delete a space and all its content permanently. This operation cannot be reverted.
+
+:::
+
+</TabItem>
+<TabItem value="response-204" label="Response - 204 No Content">
+
+This response has no body value.
+
+</TabItem>
+<TabItem value="response-400" label="Response - 400 Bad Request">
+
+The space to be deleted was not disabled before.
+
+```json
+{
+  "error": {
+    "code": "invalidRequest",
+    "innererror": {
+      "date": "2023-01-24T19:57:19Z",
+      "request-id": "f62af40f-bc18-475e-acd7-e9008d6bd326"
+    },
+    "message": "error: bad request: can't purge enabled space"
+  }
+}
+```
+
+</TabItem>
+</Tabs>
+
+## Sharing Space
+
+### Add member to space `POST /drives/\{drive-id\}/root/invite`
+
+[Invite](https://docs.opencloud.eu/swagger/libre-graph-api/#/drives.permissions/Invite)
+
+### Sharing space as a link `POST /drives/\{drive-id\}/root/createLink`
+
+[CreateLinkSpaceRoot](https://docs.opencloud.eu/swagger/libre-graph-api/#/drives.root/CreateLinkSpaceRoot)
+
+## Reading Space Permissions
+
+### Listing permissions of a space `GET /drives/\{drive-id\}/root/permissions`
+
+[ListPermissionsSpaceRoot](https://docs.opencloud.eu/swagger/libre-graph-api/#/drives.root/ListPermissionsSpaceRoot)
+
+## Modifying / Deleting Space Permissions
+
+### Update permissions of a drive `PATCH /drives/\{drive-id\}/root/permissions/\{perm-id\}`
+
+[UpdatePermissionSpaceRoot](https://docs.opencloud.eu/swagger/libre-graph-api/#/drives.root/UpdatePermissionSpaceRoot)
+
+### Set password of a link share `POST /drives/\{drive-id\}/root/permissions/\{perm-id\}/setPassword`
+
+[SetPermissionPasswordSpaceRoot](https://docs.opencloud.eu/swagger/libre-graph-api/#/drives.root/SetPermissionPasswordSpaceRoot)
+
+### Removing acess to a space `DELETE /drives/\{drive-id\}/root/permissions/\{perm-id\}`
+
+[DeletePermissionSpaceRoot](https://docs.opencloud.eu/swagger/libre-graph-api/#/drives.root/DeletePermissionSpaceRoot)
diff --git a/versioned_docs/version-7.x/dev/server/apis/http/graph/users.md b/versioned_docs/version-7.x/dev/server/apis/http/graph/users.md
new file mode 100644
index 000000000..dffab4ef4
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/apis/http/graph/users.md
@@ -0,0 +1,264 @@
+---
+title: Users
+sidebar_position: 30
+---
+
+## Users API
+
+The Users API is implementing a subset of the functionality of the
+[MS Graph User resource](https://docs.microsoft.com/en-us/graph/api/resources/user?view=graph-rest-1.0)
+The JSON representation of a User handled by the Users API looks like this:
+
+```json
+{
+  "displayName": "Dennis Ritchie",
+  "id": "4c510ada-c86b-4815-8820-42cdf82c3d51",
+  "mail": "dennis@example.org",
+  "onPremisesSamAccountName": "dennis"
+}
+```
+
+Our implementation currently supports only a limited set of Attributes of Users:
+
+| Attribute                | Description                                                                                                               |
+| ------------------------ | ------------------------------------------------------------------------------------------------------------------------- |
+| displayName              | The full name of the user, usually a combination of given name and last name                                              |
+| mail                     | The user's email address                                                                                                  |
+| onPremisesSamAccountName | The loginname/account name of the user                                                                                    |
+| id                       | An unique, stable readonly identifier for the user that stays the same for the whole lifetime of the User, usually a UUID |
+| passwordProfile          | Contains the password of the users. This is only present when updating or creating users. It is never returned by the API |
+
+### Reading users
+
+#### `GET /me`
+
+Returns the user object of the currently signed-in user
+
+Example:
+
+```bash
+curl -k 'https://localhost:9200/graph/v1.0/me' -u user:password
+```
+
+Response:
+
+```json
+{
+  "displayName": "Dennis Ritchie",
+  "id": "4c510ada-c86b-4815-8820-42cdf82c3d51",
+  "mail": "dennis@example.org",
+  "onPremisesSamAccountName": "dennis"
+}
+```
+
+#### `GET /users`
+
+Returns a list of all users
+
+Example:
+
+```bash
+curl -k 'https://localhost:9200/graph/v1.0/users' -u user:password
+
+```
+
+Response:
+
+```json
+{
+  "value": [
+    {
+      "displayName": "Dennis Ritchie",
+      "id": "4c510ada-c86b-4815-8820-42cdf82c3d51",
+      "mail": "dennis@example.org",
+      "onPremisesSamAccountName": "dennis"
+    },
+    {
+      "displayName": "Lynn Conway",
+      "id": "058bff95-6708-4fe5-91e4-9ea3d377588b",
+      "mail": "lynn@example.org",
+      "onPremisesSamAccountName": "lynn"
+    }
+  ]
+}
+```
+
+#### `GET /users?$expand=memberOf`
+
+Returns a list of all users
+
+Example:
+
+```bash
+curl -k 'https://localhost:9200/graph/v1.0/users?$expand=memberOf' -u user:password
+
+```
+
+Response:
+
+```json
+{
+  "value": [
+    {
+      "displayName": "Dennis Ritchie",
+      "id": "4c510ada-c86b-4815-8820-42cdf82c3d51",
+      "mail": "dennis@example.org",
+      "onPremisesSamAccountName": "dennis",
+      "memberOf": [
+        {
+          "displayName": "users",
+          "id": "509a9dcd-bb37-4f4f-a01a-19dca27d9cfa"
+        },
+        {
+          "displayName": "basic-haters",
+          "id": "6040aa17-9c64-4fef-9bd0-77234d71bad0"
+        },
+        {
+          "displayName": "bible-readers",
+          "id": "dd58e5ec-842e-498b-8800-61f2ec6f911f"
+        },
+        {
+          "displayName": "programmers",
+          "id": "262982c1-2362-4afa-bfdf-8cbfef64a06e"
+        }
+      ]
+    },
+    {
+      "displayName": "Lynn Conway",
+      "id": "058bff95-6708-4fe5-91e4-9ea3d377588b",
+      "mail": "lynn@example.org",
+      "onPremisesSamAccountName": "lynn",
+      "memberOf": [
+        {
+          "displayName": "users",
+          "id": "509a9dcd-bb37-4f4f-a01a-19dca27d9cfa"
+        }
+      ]
+    }
+  ]
+}
+```
+
+#### `GET /users/{userid or accountname}`
+
+Example:
+
+```bash
+curl -k 'https://localhost:9200/graph/v1.0/users/058bff95-6708-4fe5-91e4-9ea3d377588b' -u user:password
+```
+
+Response:
+
+```json
+{
+  "displayName": "Lynn Conway",
+  "id": "058bff95-6708-4fe5-91e4-9ea3d377588b",
+  "mail": "lynn@example.org",
+  "onPremisesSamAccountName": "lynn"
+}
+```
+
+#### `GET /users/{userid or accountname}?$expand=memberOf`
+
+Example:
+
+```bash
+curl -k 'https://localhost:9200/graph/v1.0/users/058bff95-6708-4fe5-91e4-9ea3d377588b?$expand=memberOf' -u user:password
+```
+
+Response:
+
+```json
+{
+  "displayName": "Lynn Conway",
+  "id": "058bff95-6708-4fe5-91e4-9ea3d377588b",
+  "mail": "lynn@example.org",
+  "onPremisesSamAccountName": "lynn",
+  "memberOf": [
+    {
+      "displayName": "users",
+      "id": "509a9dcd-bb37-4f4f-a01a-19dca27d9cfa"
+    }
+  ]
+}
+```
+
+### Creating / Updating Users
+
+#### `POST /users`
+
+Use this to create a new user.
+
+##### Request Body
+
+Note the missing `"id"` Attribute. It will be generated by the server:
+
+```json
+{
+  "displayName": "Example User",
+  "mail": "example@example.org",
+  "onPremisesSamAccountName": "example",
+  "passwordProfile": {
+    "password": "ThePassword"
+  }
+}
+```
+
+##### Response
+
+When successful, the response will return the new user, without the password, but including the newly allocated `"id"`:
+
+```json
+{
+  "displayName": "Example User",
+  "id": "c067b139-c91c-4e47-8be6-669156a0587b",
+  "mail": "example@example.org",
+  "onPremisesSamAccountName": "example"
+}
+```
+
+#### `DELETE /users/{id}`
+
+Example:
+
+```bash
+curl -k --request DELETE 'https://localhost:9200/graph/v1.0/users/c067b139-c91c-4e47-8be6-669156a0587b' -u user:password
+```
+
+When successful the API returns no response body and the HTTP status code 204 (No Content)
+
+#### `PATCH /users/{id}`
+
+Updating attributes of a single user can be done with a patch request. The Request Body contains the new values of the attributes
+to be updated. E.g. to update the `displayName` Attribute:
+
+```bash
+ curl -k --header "Content-Type: application/json" \
+         --request PATCH  --data '{"displayName": "Test User" }' \
+  'https://localhost:9200/graph/v1.0/users/c54b0588-7157-4521-bb52-c1c8ca84ea71' -u user:password
+```
+
+Similar to creating a user via `POST`, the `PATCH` request will return the user object containing the new attribute values.
+
+### Change password
+
+#### `POST /me/changePassword`
+
+Users can change their own password by sending a POST request to `/me/changePassword`
+
+##### Request Body
+
+```json
+{
+  "currentPassword": "current",
+  "newPassword": "new"
+}
+```
+
+When successful the API returns no response body and the HTTP status code 204 (No Content)
+
+```bash
+ curl -i -k --header "Content-Type: application/json" \
+      --request POST  --data '{"currentPassword": "current", "newPassword": "new" }' \
+      'https://localhost:9200/graph/v1.0/me/changePassword' -u user:current
+```
diff --git a/versioned_docs/version-7.x/dev/server/apis/http/index.md b/versioned_docs/version-7.x/dev/server/apis/http/index.md
new file mode 100644
index 000000000..a24d8ac14
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/apis/http/index.md
@@ -0,0 +1,8 @@
+---
+title: HTTP
+sidebar_position: 1
+---
+
+The [Hypertext Transfer Protocol (HTTP)](https://www.rfc-editor.org/rfc/rfc2616) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. HTTP is the foundation of data communication for the World Wide Web, where hypertext documents include hyperlinks to other resources that the user can easily access, for example by a mouse click or by tapping the screen in a web browser.
+
+Development of HTTP was initiated by Tim Berners-Lee at CERN in 1989 and summarized in a simple document describing the behavior of a client and a server using the first HTTP protocol version that was named 0.9. That first version of HTTP protocol soon evolved into a more elaborated version that was the first draft toward a far future version 1.0
diff --git a/versioned_docs/version-7.x/dev/server/apis/http/tus_upload.md b/versioned_docs/version-7.x/dev/server/apis/http/tus_upload.md
new file mode 100644
index 000000000..514df2d65
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/apis/http/tus_upload.md
@@ -0,0 +1,236 @@
+---
+title: Resumable Upload
+sidebar_position: 21
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+OpenCloud supports the tus resumable-upload protocol, which is a robust, modular, and open protocol designed to resume large file uploads reliably over HTTP.
+In situations where file uploads might be interrupted due to network issues, browser crashes, or other unforeseen interruptions,
+tus ensures that uploads can be resumed from the point of failure without losing data.
+This documentation shows some basic examples, refer [tus official site](https://tus.io/protocols/resumable-upload) for more details.
+
+## Supported tus Features
+
+The backend announces certain tus features to clients. WebDAV responses come with tus HTTP headers for the official tus features, and additional, OpenCloud specific features are announced via the capabilities endpoint (e.g. `https://localhost:9200/ocs/v1.php/cloud/capabilities?format=json`).
+
+The following snippet shows the relevant part of the server capabilities of OpenCloud that concerns the tus upload:
+
+```json
+{
+  "ocs": {
+    "data": {
+      "capabilities": {
+        "files": {
+          "tus_support": {
+            "version": "1.0.0",
+            "resumable": "1.0.0",
+            "extension": "creation,creation-with-upload",
+            "max_chunk_size": 10000000,
+            "http_method_override": ""
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+| Parameter      | Environment Variable           | Default Value | Description                                                         |
+| -------------- | ------------------------------ | ------------- | ------------------------------------------------------------------- |
+| max_chunk_size | FRONTEND_UPLOAD_MAX_CHUNK_SIZE | 10000000      | Announces the max chunk sizes in bytes for uploads via the clients. |
+
+## Upload in Chunks
+
+### Create an Upload URL
+
+The client must send a POST request against a known upload creation URL to request a new upload resource.
+The filename has to be provided in base64-encoded format.
+
+Example:
+
+```bash
+# base64 encoded filename 'tustest.txt' is 'dHVzdGVzdC50eHQ='
+echo -n 'tustest.txt' | base64
+```
+
+<Tabs>
+<TabItem value="request" label="Request">
+```bash
+curl -ks -XPOST https://cloud.opencloud.test/remote.php/dav/spaces/8d72036d-14a5-490f-889e-414064156402$196ac304-7b88-44ce-a4db-c4becef0d2e0 \
+-H "Authorization: Bearer eyJhbGciOiJQUzI..."\
+-H "Tus-Resumable: 1.0.0" \
+-H "Upload-Length: 10" \
+-H "Upload-Metadata: filename dHVzdGVzdC50eHQ="
+```
+</TabItem>
+
+<TabItem value="response-201" label="Response - 201 Created">
+```bash
+< HTTP/1.1 201 Created
+< Access-Control-Allow-Headers: Tus-Resumable, Upload-Length, Upload-Metadata, If-Match
+< Access-Control-Allow-Origin: *
+< Access-Control-Expose-Headers: Tus-Resumable, Upload-Offset, Location
+< Content-Length: 0
+< Content-Security-Policy: default-src 'none';
+< Date: Mon, 16 Oct 2023 08:49:39 GMT
+< Location: https://cloud.opencloud.test/data/eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJyZXZhIiwiZXhwIjoxNjk3NTMyNTc5LCJpYXQiOjE2OTc0NDYxNzksInRhcmdldCI6Imh0dHA6Ly9sb2NhbGhvc3Q6OTE1OC9kYXRhL3R1cy8zYTU3ZWZlMS04MzE0LTQ4MGEtOWY5Ny04N2Q1YzBjYTJhMTgifQ.FbrlY7mdOfsbFgMrP8OtcHlCEq72a2ZVnPD2iBo9MfM
+< Tus-Extension: creation,creation-with-upload,checksum,expiration
+< Tus-Resumable: 1.0.0
+< Vary: Origin
+< X-Content-Type-Options: nosniff
+< X-Download-Options: noopen
+< X-Frame-Options: SAMEORIGIN
+< X-Permitted-Cross-Domain-Policies: none
+< X-Request-Id: xxxxxxxxxxxxxxxxxxxxxx
+< X-Robots-Tag: none
+< X-Xss-Protection: 1; mode=block
+<
+* Connection #0 to host localhost left intact
+```
+</TabItem>
+</Tabs>
+
+The server will return a temporary upload URL in the location header of the response:
+
+```bash
+< Location: https://cloud.opencloud.test/data/eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJyZXZhIiwiZXhwIjoxNjk3NTMyNTc5LCJpYXQiOjE2OTc0NDYxNzksInRhcmdldCI6Imh0dHA6Ly9sb2NhbGhvc3Q6OTE1OC9kYXRhL3R1cy8zYTU3ZWZlMS04MzE0LTQ4MGEtOWY5Ny04N2Q1YzBjYTJhMTgifQ.FbrlY7mdOfsbFgMrP8OtcHlCEq72a2ZVnPD2iBo9MfM
+```
+
+### Upload the First Chunk
+
+Once a temporary upload URL has been created, a client can send a PATCH request to upload a file. The file content should be sent in the body of the request:
+<Tabs>
+<TabItem value="request" label="Request">
+
+```shell
+curl -ks -XPATCH https://temporary-upload-url \
+-H "Authorization: Bearer eyJhbGciOiJQUzI..." \
+-H "Tus-Resumable: 1.0.0" \
+-H "Upload-Offset: 0" \
+-H "Content-Type: application/offset+octet-stream" -d "01234"
+```
+
+</TabItem>
+
+<TabItem value="response-204" label="Response - 204 No Content">
+```bash
+< HTTP/1.1 204 No Content
+< Date: Tue, 17 Oct 2023 04:10:52 GMT
+< Oc-Fileid: 8d72036d-14a5-490f-889e-414064156402$73bb5450-816b-4cae-90aa-1f96adc95bd4!84e319e4-de1d-4dd8-bbd0-e51d933cdbcd
+< Tus-Resumable: 1.0.0
+< Upload-Expires: 1697602157
+< Upload-Offset: 5
+< Vary: Origin
+< X-Content-Type-Options: nosniff
+< X-Request-Id: xxxxxxxxxxxxxxxxxxxxxx
+<
+* Connection #0 to host localhost left intact
+```
+</TabItem>
+</Tabs>
+
+### Upload Further Chunks
+
+After the first chunk is uploaded, the second chunk can be uploaded by pointing `Upload-Offset` to exact position that was returned in the first response.
+Upload process will not be marked as complete until the total uploaded content size matches the `Upload-Length` specified during the creation of the temporary URL.
+
+<Tabs>
+<TabItem value="request" label="Request">
+```shell
+curl -ks -XPATCH https://temporary-upload-url \
+-H "Authorization: Bearer eyJhbGciOiJQUzI..." \
+-H "Tus-Resumable: 1.0.0" \
+-H "Upload-Offset: 5" \
+-H "Content-Type: application/offset+octet-stream" -d "56789"
+```
+</TabItem>
+
+<TabItem value="response-204-2" label="Response - 204 No Content">
+```bash
+< HTTP/1.1 204 No Content
+< Date: Tue, 17 Oct 2023 04:11:00 GMT
+< Oc-Fileid: 8d72036d-14a5-490f-889e-414064156402$73bb5450-816b-4cae-90aa-1f96adc95bd4!84e319e4-de1d-4dd8-bbd0-e51d933cdbcd
+< Tus-Resumable: 1.0.0
+< Upload-Expires: 1697602157
+< Upload-Offset: 10
+< Vary: Origin
+< X-Content-Type-Options: nosniff
+< X-Request-Id: xxxxxxxxxxxxxxxxxxxxxx
+<
+* Connection #0 to host localhost left intact
+```
+</TabItem>
+</Tabs>
+
+:::warning Important Warning
+`Upload-Offset` header indicates the byte position in the target file where the server should start writing the upload content.
+It ensures data integrity and order during the upload process.
+:::
+
+## Creation with Upload
+
+<Tabs>
+<TabItem value="request" label="Request">
+```shell
+curl -ks -XPOST https://cloud.opencloud.test/remote.php/dav/spaces/\{space-id\} \
+-H "Authorization: Bearer eyJhbGciOiJQUzI..." \
+-H "Tus-Resumable: 1.0.0" \
+-H "Upload-Length: 14" \
+-H "Content-Type: application/offset+octet-stream" \
+-H "Upload-Metadata: filename dGVzdC50eHQ=" \
+-H "Tus-Extension: creation-with-upload" \
+-d "upload content"
+```
+</TabItem>
+
+<TabItem value="response-201-creation" label="Response - 201 Created">
+```shell
+< HTTP/1.1 201 Created
+< Access-Control-Allow-Headers: Tus-Resumable, Upload-Length, Upload-Metadata, If-Match
+< Access-Control-Allow-Origin: *
+< Access-Control-Expose-Headers: Tus-Resumable, Upload-Offset, Location
+< Content-Length: 0
+< Content-Security-Policy: default-src 'none';
+< Content-Type: text/plain
+< Date: Mon, 16 Oct 2023 04:18:25 GMT
+< Etag: "372c96743f68bc40e789124d30567371"
+< Last-Modified: Mon, 16 Oct 2023 04:18:25 +0000
+< Location: https://cloud.opencloud.test/data/eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJyZXZhIiwiZXhwIjoxNjk3NTE2MzA1LCJpYXQiOjE2OTc0Mjk5MDUsInRhcmdldCI6Imh0dHA6Ly9sb2NhbGhvc3Q6OTE1OC9kYXRhL3R1cy82NjlhODBlZi1hN2VjLTQwYTAtOGNmOS05MTgwNTVhYzlkZjAifQ.yq-ofJYnJ9FLML7Z_jki1FJQ7Ulbt9O_cmLe6V411A4
+< Oc-Etag: "372c96743f68bc40e789124d30567371"
+< Oc-Fileid: 44d3e1e0-6c01-4b94-9145-9d0068239fcd$446bdad4-4b27-41f1-afce-0881f202a214!d7c292a6-c395-4e92-bf07-2c1663aec8dd
+< Oc-Perm: RDNVWZP
+< Tus-Extension: creation,creation-with-upload,checksum,expiration
+< Tus-Resumable: 1.0.0
+< Upload-Expires: 1697516305
+< Upload-Offset: 14
+< Vary: Origin
+< X-Content-Type-Options: nosniff
+< X-Download-Options: noopen
+< X-Frame-Options: SAMEORIGIN
+* TLSv1.2 (IN), TLS header, Supplemental data (23):
+{ [5 bytes data]
+< X-Permitted-Cross-Domain-Policies: none
+< X-Request-Id: xxxxxxxxxxxxxxxxxxxxxx
+< X-Robots-Tag: none
+< X-Xss-Protection: 1; mode=block
+<
+* Connection #0 to host localhost left intact
+```
+</TabItem>
+</Tabs>
+
+:::warning Important Warning
+The `Upload-Length` header of the request has to contain the exact size of the upload content in byte.
+:::
+
+## Supported Upload-Metadata
+
+Upload-metadata key-value pairs aren't specified in the general tus docs. The following ones are supported in the OpenCloud ecosystem:
+
+| Parameter (key)          | Example (value MUST be Base64 encoded)        | Description                          |
+| ------------------------ | --------------------------------------------- | ------------------------------------ |
+| `filename` (mandatory)   | example.pdf                                   | Filename                             |
+| `mtime` (recommended)    | 1701708712                                    | Modification time (Unix time format) |
+| `checksum` (recommended) | SHA1 a330de5886e5a92d78fb3f8d59fe469857759e72 | Checksum, computed from the client   |
diff --git a/versioned_docs/version-7.x/dev/server/apis/http/webdav/index.md b/versioned_docs/version-7.x/dev/server/apis/http/webdav/index.md
new file mode 100644
index 000000000..e793bcdd7
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/apis/http/webdav/index.md
@@ -0,0 +1,558 @@
+---
+title: WebDAV
+sidebar_position: 2
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+**Web** **D**istributed **A**uthoring and **V**ersioning (WebDAV) consists of a set of methods, headers, and content-types extending HTTP/1.1 for the management of resources and -properties, creation and management of resource collections, URL namespace manipulation, and resource locking (collision avoidance). WebDAV is one of the central APIs that OpenCloud uses for handling file resources, metadata and locks.
+
+:::info RFC
+**WebDAV RFCs**
+
+RFC 2518 was published in February 1999. [RFC 4918](https://datatracker.ietf.org/doc/html/rfc4918), published in June 2008 obsoletes RFC 2518 with minor revisions mostly due to interoperability experience.
+
+:::
+
+## Calling the WebDAV API
+
+### Request URI
+
+```sh
+{HTTP method} https://cloud.opencloud.test/{webdav-base}/{resourceID}/{path}
+```
+
+The request URI consists of:
+
+| Component       | Description                                                                                            |
+| --------------- | ------------------------------------------------------------------------------------------------------ |
+| `{HTTP method}` | The HTTP method which is used in the request.                                                          |
+| `{webdav-base}` | The WebDAV base path component. Possible options are                                                   |
+|                 | `dav/spaces/` This is the default and optimized endpoint for all WebDAV requests.                      |
+|                 | `remote.php/dav/spaces/`\*                                                                             |
+|                 | `remote.php/webdav/`\*                                                                                 |
+|                 | `webdav/`\*                                                                                            |
+|                 | `dav/`\*                                                                                               |
+| `{resourceID}`  | This resourceID is used as the WebDAV root element. All children are accessed by their relative paths. |
+| `{path}`        | The relative path to the WebDAV root. In most of the cases, this is the space root.                    |
+
+\* these dav endpoints are implemented for legacy reasons and should not be used. Note: The legacy endpoints **do not take the resourceID as an argument.**
+
+### HTTP methods
+
+| Method    | Description                                                                                                                                                                                                                                  |
+| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| PROPFIND  | Retrieve properties as XML from a web resource. It is also overloaded to retrieve the collection structure (a.k.a. directory hierarchy) of a remote system.                                                                                  |
+| PROPPATCH | Process instructions specified in the request body to set and/or remove properties defined on the resource identified by the request uri.                                                                                                    |
+| MKCOL     | Create a WebDAV collection (folder) at the location specified by the request uri.                                                                                                                                                            |
+| GET       | Retrieve a WebDAV resource.                                                                                                                                                                                                                  |
+| HEAD      | Retrieve a WebDAV resource without reading the body.                                                                                                                                                                                         |
+| PUT       | A PUT performed on an existing resource replaces the GET response entity of the resource.                                                                                                                                                    |
+| POST      | Not part of the WebDAV rfc and has no effect on a WebDAV resource. However, this method is used in the TUS protocol for uploading resources.                                                                                                 |
+| PATCH     | Not part of the WebDAV rfc and has no effect on a WebDAV resource. However, this method is used in the TUS protocol for uploading resources.                                                                                                 |
+| COPY      | Creates a duplicate of the source resource identified by the Request-URI, in the destination resource identified by the URI in the Destination header.                                                                                       |
+| MOVE      | The MOVE operation on a non-collection resource is the logical equivalent of a copy (COPY), followed by consistency maintenance processing, followed by a delete of the source, where all three actions are performed in a single operation. |
+| DELETE    | Delete the resource identified by the Request-URI.                                                                                                                                                                                           |
+| LOCK      | A LOCK request to an existing resource will create a lock on the resource identified by the Request-URI, provided the resource is not already locked with a conflicting lock.                                                                |
+| UNLOCK    | The UNLOCK method removes the lock identified by the lock token in the Lock-Token request header. The Request-URI must identify a resource within the scope of the lock.                                                                     |
+
+The methods `MKCOL`, `GET`, `HEAD`, `LOCK`, `COPY`, `MOVE`, `UNLOCK` and `DELETE` need no request body.
+
+The methods `PROPFIND`, `PROPPATCH`, `PUT` require a request body, normally in XML format to provide the needed values.
+
+:::tip Tooling
+**WebDAV is not REST**
+
+The WebDAV protocol was created before the REST paradigm has become the de-facto standard for API design. WebDAV uses http methods which are not part of REST. Therefore all the tooling around API design and documentation is not usable (like OpenApi 3.0 / Swagger or others).
+:::
+
+### Authentication
+
+For development purposes the examples in the developer documentation use Basic Auth. It is disabled by default and should only be enabled by setting `PROXY_ENABLE_BASIC_AUTH` in [the proxy](./../../../services/proxy/env-vars.mdx) for development or test instances.
+
+To authenticate with a Bearer token or OpenID Connect access token replace the `-u user:password` Basic Auth option of curl with a `-H 'Authorization: Bearer <token>'` header. A `<token>` can be obtained by copying it from a request in the browser, although it will time out within minutes. To automatically refresh the OpenID Connect access token an ssh-agent like solution like [oidc-agent](https://github.com/indigo-dc/oidc-agent) should be used.
+
+## Listing Properties
+
+This method is used to list the properties of a resource in xml. This method can also be used to retrieve the listing of a WebDAV collection which means the content of a remote directory.
+
+<Tabs>
+<TabItem value="curl" label="Curl">
+
+```shell
+curl -L -X PROPFIND 'https://localhost:9200/dav/spaces/storage-users-1%24some-admin-user-id-0000-000000000000/' \
+-H 'Depth: 1' \
+-d '<?xml version="1.0"?>
+<d:propfind  xmlns:d="DAV:" xmlns:oc="http://owncloud.org/ns">
+  <d:prop>
+    <oc:permissions />
+    <oc:favorite />
+    <oc:fileid />
+    <oc:owner-id />
+    <oc:owner-display-name />
+    <oc:share-types />
+    <oc:privatelink />
+    <d:getcontentlength />
+    <oc:size />
+    <d:getlastmodified />
+    <d:getetag />
+    <d:getcontenttype />
+    <d:resourcetype />
+    <oc:downloadURL />
+  </d:prop>
+</d:propfind>'
+```
+
+</TabItem>
+<TabItem value="http" label="HTTP">
+
+```shell
+PROPFIND /dav/spaces/storage-users-1%24some-admin-user-id-0000-000000000000/ HTTP/1.1
+Host: localhost:9200
+Origin: https://localhost
+Access-Control-Request-Method: PROPFIND
+Depth: 1
+Content-Type: application/xml
+Authorization: Basic YWRtaW46YWRtaW4=
+Content-Length: 436
+
+<?xml version="1.0"?>
+<d:propfind  xmlns:d="DAV:" xmlns:oc="http://owncloud.org/ns">
+  <d:prop>
+    <oc:permissions />
+    <oc:favorite />
+    <oc:fileid />
+    <oc:owner-id />
+    <oc:owner-display-name />
+    <oc:share-types />
+    <oc:privatelink />
+    <d:getcontentlength />
+    <oc:size />
+    <d:getlastmodified />
+    <d:getetag />
+    <d:getcontenttype />
+    <d:resourcetype />
+    <oc:downloadURL />
+  </d:prop>
+</d:propfind>
+```
+
+</TabItem>
+</Tabs>
+
+The request consists of a request body and an optional `Depth` Header.
+
+:::tip PROPFIND usage
+**Metadata and Directory listings**
+
+Clients can use the `PROPFIND` method to retrieve properties of resources (metadata) and to list the content of a directories.
+:::
+
+### Response
+
+<Tabs>
+<TabItem value="207" label="207 - Multistatus">
+
+#### Multi Status Response
+
+A Multi-Status response conveys information about multiple resources
+in situations where multiple status codes might be appropriate. The
+default Multi-Status response body is an application/xml
+HTTP entity with a `multistatus` root element. Further elements
+contain `200`, `300`, `400`, and `500` series status codes generated during
+the method invocation.
+
+Although `207` is used as the overall response status code, the
+recipient needs to consult the contents of the multistatus response
+body for further information about the success or failure of the
+method execution. The response MAY be used in success, partial
+success and also in failure situations.
+
+The `multistatus` root element holds zero or more `response` elements
+in any order, each with information about an individual resource.
+
+#### Body
+
+```xml
+<d:multistatus xmlns:s="http://sabredav.org/ns" xmlns:d="DAV:" xmlns:oc="http://owncloud.org/ns">
+    <d:response>
+        <d:href>/dav/spaces/storage-users-1$some-admin-user-id-0000-000000000000/</d:href>
+        <d:propstat>
+            <d:prop>
+                <oc:permissions>RDNVCKZP</oc:permissions>
+                <oc:favorite>0</oc:favorite>
+                <oc:fileid>storage-users-1$some-admin-user-id-0000-000000000000!some-admin-user-id-0000-000000000000</oc:fileid>
+                <oc:id>storage-users-1$some-admin-user-id-0000-000000000000!some-admin-user-id-0000-000000000000</oc:id>
+                <oc:owner-id>admin</oc:owner-id>
+                <oc:owner-display-name>Admin</oc:owner-display-name>
+                <oc:privatelink>https://localhost:9200/f/storage-users-1$some-admin-user-id-0000-000000000000%21some-admin-user-id-0000-000000000000</oc:privatelink>
+                <oc:size>10364682</oc:size>
+                <d:getlastmodified>Mon, 04 Sep 2023 20:10:09 GMT</d:getlastmodified>
+                <d:getetag>"c4d3610dfe4fac9b44e1175cfc44b12b"</d:getetag>
+                <d:resourcetype>
+                    <d:collection/>
+                </d:resourcetype>
+            </d:prop>
+            <d:status>HTTP/1.1 200 OK</d:status>
+        </d:propstat>
+        <d:propstat>
+            <d:prop>
+                <oc:checksums></oc:checksums>
+                <oc:share-types></oc:share-types>
+                <d:getcontentlength></d:getcontentlength>
+                <d:getcontenttype></d:getcontenttype>
+            </d:prop>
+            <d:status>HTTP/1.1 404 Not Found</d:status>
+        </d:propstat>
+    </d:response>
+    <d:response>
+        <d:href>/dav/spaces/storage-users-1$some-admin-user-id-0000-000000000000/New%20file.txt</d:href>
+        <d:propstat>
+            <d:prop>
+                <oc:permissions>RDNVWZP</oc:permissions>
+                <oc:checksums>
+                    <oc:checksum>SHA1:1c68ea370b40c06fcaf7f26c8b1dba9d9caf5dea MD5:2205e48de5f93c784733ffcca841d2b5 ADLER32:058801ab</oc:checksum>
+                </oc:checksums>
+                <oc:favorite>0</oc:favorite>
+                <oc:fileid>storage-users-1$some-admin-user-id-0000-000000000000!90cc3e73-0c6c-4346-9c4d-f529976d4990</oc:fileid>
+                <oc:id>storage-users-1$some-admin-user-id-0000-000000000000!90cc3e73-0c6c-4346-9c4d-f529976d4990</oc:id>
+                <oc:owner-id>admin</oc:owner-id>
+                <oc:owner-display-name>Admin</oc:owner-display-name>
+                <oc:share-types>
+                    <oc:share-type>0</oc:share-type>
+                    <oc:share-type>1</oc:share-type>
+                    <oc:share-type>3</oc:share-type>
+                </oc:share-types>
+                <oc:privatelink>https://localhost:9200/f/storage-users-1$some-admin-user-id-0000-000000000000%2190cc3e73-0c6c-4346-9c4d-f529976d4990</oc:privatelink>
+                <d:getcontentlength>5</d:getcontentlength>
+                <oc:size>5</oc:size>
+                <d:getlastmodified>Mon, 28 Aug 2023 20:45:03 GMT</d:getlastmodified>
+                <d:getetag>"75115347c74701a3be9c635ddebbf5c4"</d:getetag>
+                <d:getcontenttype>text/plain</d:getcontenttype>
+                <d:resourcetype></d:resourcetype>
+            </d:prop>
+            <d:status>HTTP/1.1 200 OK</d:status>
+        </d:propstat>
+    </d:response>
+    <d:response>
+        <d:href>/dav/spaces/storage-users-1$some-admin-user-id-0000-000000000000/NewFolder/</d:href>
+        <d:propstat>
+            <d:prop>
+                <oc:permissions>RDNVCKZP</oc:permissions>
+                <oc:favorite>0</oc:favorite>
+                <oc:fileid>storage-users-1$some-admin-user-id-0000-000000000000!5c73ecd9-d9f4-44f4-b685-ca4cb40aa6b7</oc:fileid>
+                <oc:id>storage-users-1$some-admin-user-id-0000-000000000000!5c73ecd9-d9f4-44f4-b685-ca4cb40aa6b7</oc:id>
+                <oc:owner-id>admin</oc:owner-id>
+                <oc:owner-display-name>Admin</oc:owner-display-name>
+                <oc:privatelink>https://localhost:9200/f/storage-users-1$some-admin-user-id-0000-000000000000%215c73ecd9-d9f4-44f4-b685-ca4cb40aa6b7</oc:privatelink>
+                <oc:size>0</oc:size>
+                <d:getlastmodified>Mon, 28 Aug 2023 20:45:10 GMT</d:getlastmodified>
+                <d:getetag>"e83367534cc595a45d706857fa5f03d8"</d:getetag>
+                <d:resourcetype>
+                    <d:collection/>
+                </d:resourcetype>
+            </d:prop>
+            <d:status>HTTP/1.1 200 OK</d:status>
+        </d:propstat>
+        <d:propstat>
+            <d:prop>
+                <oc:checksums></oc:checksums>
+                <oc:share-types></oc:share-types>
+                <d:getcontentlength></d:getcontentlength>
+                <d:getcontenttype></d:getcontenttype>
+            </d:prop>
+            <d:status>HTTP/1.1 404 Not Found</d:status>
+        </d:propstat>
+    </d:response>
+</d:multistatus>
+```
+
+</TabItem>
+<TabItem value="400" label="400 - Bad Request">
+
+#### Body
+
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<d:error xmlns:d="DAV" xmlns:s="http://sabredav.org/ns">
+    <s:exception>Sabre\DAV\Exception\BadRequest</s:exception>
+    <s:message>Invalid Depth header value: 3</s:message>
+</d:error>
+```
+
+This can occur if the request is malformed e.g. due to an invalid xml request body or an invalid depth header value.
+</TabItem>
+<TabItem value="404" label="404 - Not Found">
+
+#### Body
+
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<d:error xmlns:d="DAV" xmlns:s="http://sabredav.org/ns">
+    <s:exception>Sabre\DAV\Exception\NotFound</s:exception>
+    <s:message>Resource not found</s:message>
+</d:error>
+```
+
+</TabItem>
+</Tabs>
+
+### Request Body
+
+The `PROPFIND` Request can include an XML request body containing a list of namespaced property names.
+
+### Namespaces
+
+When building the body of your DAV request, you will request properties that are available under a specific namespace URI. It is usual to declare prefixes for those namespace in the `d:propfind` element of the body.
+
+Available namespaces:
+
+| URI                                         | Prefix |
+| ------------------------------------------- | ------ |
+| DAV:                                        | d      |
+| `http://sabredav.org/ns`                    | s      |
+| `http://owncloud.org/ns`                    | oc     |
+| `http://open-collaboration-services.org/ns` | ocs    |
+| `http://open-cloud-mesh.org/ns`             | ocm    |
+
+### Request Example with declared namespaces
+
+```xml
+<?xml version="1.0"?>
+    <d:propfind xmlns:d="DAV:" xmlns:oc="http://owncloud.org/ns">
+    </d:propfind>
+```
+
+### Supported WebDAV Properties
+
+| Property                            | Desription                                                                 | Example                                                                                                                                          |
+| ----------------------------------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `<d:getlastmodified />`             | The latest modification time.                                              | `Fri, 30 Dec 2022 14:22:43 GMT`                                                                                                                  |
+| `<d:getetag />`                     | The file's etag.                                                           | `"c3a1ee4a0c28edc15b9635c3bf798013"`                                                                                                             |
+| `<d:getcontenttype />`              | The mime type of the file.                                                 | `image/jpeg`                                                                                                                                     |
+| `<d:resourcetype />`                | Specifies the nature of the resource.                                      | `<d:collection />` for a folder                                                                                                                  |
+| `<d:getcontentlength />`            | The size if it is a file in bytes.                                         | `5` bytes                                                                                                                                        |
+| `<d:lockdiscovery />`               | Describes the active locks on a resource.                                  |                                                                                                                                                  |
+| `<oc:id />`                         | The globally unique ID of the resource.                                    | `storage-1$27475553-7fb7-4689-b4cf-bbb635daff79!27475553-7fb7-4689-b4cf-bbb635daff79`                                                            |
+| `<oc:fileid />`                     | The globally unique ID of the resource.                                    | `storage-1$27475553-7fb7-4689-b4cf-bbb635daff79!27475553-7fb7-4689-b4cf-bbb635daff79`                                                            |
+| `<oc:downloadURL />`                | Direct URL to download a file from.                                        | Not implemented.                                                                                                                                 |
+| `<oc:permissions />`                | Determines the actions a user can take on the resource.                    | The value is a string containing letters that clients can use to determine available actions.                                                    |
+|                                     |                                                                            | `S`: Shared                                                                                                                                      |
+|                                     |                                                                            | `M`: Mounted                                                                                                                                     |
+|                                     |                                                                            | `D`: Deletable                                                                                                                                   |
+|                                     |                                                                            | `NV`: Updateable, Renameable, Moveable                                                                                                           |
+|                                     |                                                                            | `W`: Updateable (file)                                                                                                                           |
+|                                     |                                                                            | `CK`: Creatable (folders only)                                                                                                                   |
+|                                     |                                                                            | `Z`: Deniable                                                                                                                                    |
+|                                     |                                                                            | `P`: Trashbin Purgable                                                                                                                           |
+|                                     |                                                                            | `X`: Securely Viewable                                                                                                                           |
+|                                     |                                                                            | In the early stages this was indeed a list of permissions. Over time, more flags were added and the term permissions no longer really fits well. |
+| `<oc:tags />`                       | List of user specified tags.                                               | `<oc:tag>test</oc:tag>`                                                                                                                          |
+| `<oc:favorite />`                   | The favorite state.                                                        | `0` for not favourited, `1` for favourited                                                                                                       |
+| `<oc:owner-id />`                   | The user id of the owner of a resource. Project spaces have no owner.      | `dennis`                                                                                                                                         |
+| `<oc:owner-display-name />`         | The display name of the owner of a resource. Project spaces have no owner. | `Dennis Ritchie`                                                                                                                                 |
+| `<oc:share-types />`                | List of share types.                                                       | `0` = User Share                                                                                                                                 |
+|                                     |                                                                            | `1` = Group Share                                                                                                                                |
+|                                     |                                                                            | `2` = Public Link                                                                                                                                |
+| `<oc:checksums />`                  |                                                                            | `<oc:checksum>`<br/>`SHA1:1c68ea370b40c06fcaf7f26c8b1dba9d9caf5dea MD5:2205e48de5f93c784733ffcca841d2b5 ADLER32:058801ab`<br /> `</oc:checksum>` |
+|                                     |                                                                            | Due to a bug in the very early development of OpenCloud, this value is not an array, but a string separated by whitespaces.                      |
+| `<oc:size />`                       | Similar to `getcontentlength` but it also works for folders.               | `10` bytes                                                                                                                                       |
+| `<oc:shareid />`                    | The ID of the share if the resource is part of such.                       | `storage-1$27475553-7fb7-4689-b4cf-bbb635daff79!27475553-7fb7-4689-b4cf-bbb635daff79`                                                            |
+| `<oc:shareroot />`                  | The root path of the shared resource if the resource is part of such.      | `/shared-folder`                                                                                                                                 |
+| `<oc:remoteItemId />`               | The ID of the shared resource if the resource is part of such.             | `storage-1$27475553-7fb7-4689-b4cf-bbb635daff79!27475553-7fb7-4689-b4cf-bbb635daff79`                                                            |
+| `<oc:public-link-item-type />`      | The type of the resource if it's a public link.                            | `folder`                                                                                                                                         |
+| `<oc:public-link-permission />`     | The share permissions of the resource if it's a public link.               | `1`                                                                                                                                              |
+| `<oc:public-link-expiration />`     | The expiration date of the public link.                                    | `Tue, 14 May 2024 12:44:29 GMT`                                                                                                                  |
+| `<oc:public-link-share-datetime />` | The date the public link was created.                                      | `Tue, 14 May 2024 12:44:29 GMT`                                                                                                                  |
+| `<oc:public-link-share-owner />`    | The username of the user who created the public link.                      | `admin`                                                                                                                                          |
+| `<oc:trashbin-original-filename />` | The original name of the resource before it was deleted.                   | `some-file.txt`                                                                                                                                  |
+| `<oc:trashbin-original-location />` | The original location of the resource before it was deleted.               | `some-file.txt`                                                                                                                                  |
+| `<oc:trashbin-delete-datetime />`   | The date the resource was deleted.                                         | `Tue, 14 May 2024 12:44:29 GMT`                                                                                                                  |
+| `<oc:audio />`                      | Audio meta data if the resource contains such.                             | `<oc:artist>Metallica</oc:artist><oc:album>Metallica</oc:album><oc:title>Enter Sandman</oc:title>`                                               |
+| `<oc:location />`                   | Location meta data if the resource contains such.                          | `<oc:latitude>51.504106</oc:latitude><oc:longitude>-0.074575</oc:latitude>`                                                                      |
+
+### Request Headers
+
+A client executing a `PROPFIND` request MUST submit a Depth Header value. In practice, support for infinite-depth requests MAY be disabled, due to the performance and security concerns associated with this behavior. Servers SHOULD treat a
+request without a Depth header as if a `Depth: infinity` header was included. Infinite depth requests are disabled by default in opencloud.
+
+| Name  | Value                                                                                 |
+| ----- | ------------------------------------------------------------------------------------- |
+| Depth | `0` = Only return the desired resource.                                               |
+|       | `1` = Return the desired resource and all resources one level below in the hierarchy. |
+|       | `infinity` = Return all resources below the root.                                     |
+
+:::warning Use the Depth header with caution
+**Depth: infinity**
+
+Using the `Depth: infinity` header value can cause heavy load on the server, depending on the size of the file tree.
+
+The request can run into a timeout and the server performance could be affected for other users.
+:::
+
+## Create a Directory
+
+Clients create directories (WebDAV collections) by executing a `MKCOL` request at the location specified by the request url.
+
+<Tabs>
+<TabItem value="curl" label="Curl">
+```shell
+curl -L -X MKCOL 'https://localhost:9200/dav/spaces/storage-users-1%24some-admin-user-id-0000-000000000000/NewFolder/' \
+-H 'Authorization: Basic YWRtaW46YWRtaW4='
+```
+</TabItem>
+<TabItem value="http" label="HTTP">
+```shell
+MKCOL /dav/spaces/storage-users-1%24some-admin-user-id-0000-000000000000/NewFolder/ HTTP/1.1
+Host: localhost:9200
+Authorization: Basic YWRtaW46YWRtaW4=
+```
+</TabItem>
+</Tabs>
+### Response
+
+<Tabs>
+<TabItem value="201" label="201 - Created">
+This indicates that the Resource has been created successfully.
+
+### Body
+
+The response has no body.
+</TabItem>
+<TabItem value="403" label="403 - Forbidden">
+
+### Body
+
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<d:error xmlns:d="DAV" xmlns:s="http://sabredav.org/ns">
+    <s:exception>Sabre\DAV\Exception\Forbidden</s:exception>
+    <s:message></s:message>
+</d:error>
+```
+
+</TabItem>
+<TabItem value="405" label="405 - Method not allowed">
+
+### Body
+
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<d:error xmlns:d="DAV" xmlns:s="http://sabredav.org/ns">
+    <s:exception>Sabre\DAV\Exception\MethodNotAllowed</s:exception>
+    <s:message>The resource you tried to create already exists</s:message>
+</d:error>
+```
+
+</TabItem>
+</Tabs>
+
+## Upload File
+
+To upload files to the remote server, clients can use the `PUT` method to create or fully replace the content of the remote file.
+
+### Request Headers
+
+| Name          | Usage                                                                                                                                                                                                                                                                                                           |
+| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `X-OC-Mtime`  | Send the last modified<br/>time of the file to the server in unixtime format. The server applies this mtime to the resource rather than the actual time.                                                                                                                                                        |
+| `OC-Checksum` | Provide the checksum of the<br/>file content to the server.<br/>This is used to prevent corrupted data transfers.                                                                                                                                                                                               |
+| `If-Match`    | The If-Match request-header field is used with a method to make it<br/>conditional. A client that has one or more entities previously<br/>obtained from the resource can verify that one of those entities is<br/>current by including a list of their associated entity tags in the<br/>If-Match header field. |
+
+<Tabs>
+<TabItem value="curl" label="Curl">
+
+```shell
+curl -L -X PUT 'https://localhost:9200/dav/spaces/storage-users-1%24some-admin-user-id-0000-000000000000/test.txt' \
+-H 'X-OC-Mtime: 1692369418' \
+-H 'OC-Checksum: SHA1:40bd001563085fc35165329ea1ff5c5ecbdbbeef' \
+-H 'If-Match: "4436aef907f41f1ac7dfd1ac3d0d455f"' \
+-H 'Content-Type: text/plain' \
+-H 'Authorization: Basic YWRtaW46YWRtaW4=' \
+-d '123'
+```
+
+</TabItem>
+<TabItem value="http" label="HTTP">
+
+```shell
+PUT /dav/spaces/storage-users-1%24some-admin-user-id-0000-000000000000/test.txt HTTP/1.1
+Host: localhost:9200
+X-OC-Mtime: 1692369418
+OC-Checksum: SHA1:40bd001563085fc35165329ea1ff5c5ecbdbbeef
+If-Match: "4436aef907f41f1ac7dfd1ac3d0d455f"
+Content-Type: text/plain
+Authorization: Basic YWRtaW46YWRtaW4=
+Content-Length: 3
+
+123
+```
+
+</TabItem>
+</Tabs>
+
+### Response
+
+<Tabs>
+<TabItem value="201" label="201 - Created">
+This indicates that the Resource has been created successfully.
+
+#### Body
+
+The response has no body.
+
+#### Headers
+
+```yaml
+Oc-Etag: '4436aef907f41f1ac7dfd1ac3d0d455f'
+Oc-Fileid: storage-users-1$some-admin-user-id-0000-000000000000!07452b22-0ba9-4539-96e1-3511aff7fd2f
+Last-Modified: Fri, 18 Aug 2023 14:36:58 +0000
+X-Oc-Mtime: accepted
+```
+
+</TabItem>
+<TabItem value="204" label="204 - No Content">
+This indicates that the Resource has been updated successfully.
+
+#### Body
+
+The response has no body.
+
+#### Headers
+
+```yaml
+Oc-Etag: '4436aef907f41f1ac7dfd1ac3d0d455f'
+Oc-Fileid: storage-users-1$some-admin-user-id-0000-000000000000!07452b22-0ba9-4539-96e1-3511aff7fd2f
+Last-Modified: Fri, 18 Aug 2023 14:36:58 +0000
+X-Oc-Mtime: accepted
+```
+
+</TabItem>
+<TabItem value="400" label="400 - Bad Request">
+This indicates that the checksum, which was sent by the client, does not match the computed one after all bytes have been received by the server.
+
+#### Body
+
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<d:error xmlns:d="DAV" xmlns:s="http://sabredav.org/ns">
+    <s:exception>Sabre\DAV\Exception\BadRequest</s:exception>
+    <s:message>The computed checksum does not match the one received from the client.</s:message>
+</d:error>
+```
+
+</TabItem>
+<TabItem value="403" label="403 - Forbidden">
+
+The user cannot create files in that remote location.
+</TabItem>
+<TabItem value="404" label="404 - Not Found">
+
+The remote target space cannot be found.
+</TabItem>
+<TabItem value="409" label="409 - Conflict">
+
+This error can occur when the request cannot be executed due to a missing precondition. One example is a PUT into a non-existing remote folder. It can also happen when the client sends the wrong etag in the `If-Match` header.
+</TabItem>
+</Tabs>
diff --git a/versioned_docs/version-7.x/dev/server/apis/index.md b/versioned_docs/version-7.x/dev/server/apis/index.md
new file mode 100644
index 000000000..ae719f375
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/apis/index.md
@@ -0,0 +1,41 @@
+---
+title: APIs
+sidebar_position: 1
+---
+
+OpenCloud provides a large set of different **application programming interfaces (APIs)**. OpenCloud is built by microservices. That means many calls to "functions" in the code are remote calls.
+
+Basically we have two different API "universes": [HTTP](./http/) and [gRPC](./grpc_apis/).
+
+| HTTP                             | gRPC                             |
+| -------------------------------- | -------------------------------- |
+| ![HTTP Logo](/img/http-logo.png) | ![gRPC Logo](/img/grpc-logo.png) |
+
+For inter-service-communication we are using mostly gRPC calls because it has some advantages. In the future, clients may decide to use gRPC directly to make use of these advantages.
+
+![OpenCloud APIs Architecture](/img/oc-apis.drawio.svg)
+
+## [HTTP](./http/)
+
+HTTP APIs are mostly used for client < > server communication. Modern applications are embracing a [RESTful](https://en.wikipedia.org/wiki/Representational_state_transfer) software architecture style. REST APIs are using the HTTP protocol to transfer data between clients and servers. All our clients talk to the Server using HTTP APIs. This has legacy reasons and is well-supported across many platforms and technologies. OpenCloud uses an HTTP API gateway (proxy service) to route client requests to the correct service.
+
+### OpenAPI
+
+It is best practise to define APIs and their behavior by a spec. We are using the OpenAPI standard for all new APIs. The [OpenAPI Specification](https://swagger.io/specification/), previously known as the Swagger Specification, is a specification for a machine-readable interface definition language for describing, producing, consuming and visualizing RESTful web services. Previously part of the Swagger framework, it became a separate project in 2016, overseen by the OpenAPI Initiative, an open-source collaboration project of the Linux Foundation. Swagger and some other tools can generate code, documentation and test cases from interface files.
+
+### RFC
+
+Some APIs have become a de facto standard and are additionally covered by an [RFC](https://en.wikipedia.org/wiki/Request_for_Comments).
+
+## [gRPC](./grpc_apis/)
+
+In gRPC, a client application can directly call methods on a server application on a different machine as if it was a local object. This makes it easier to create distributed applications based on microservices. In gRPC we can define a service and specify the methods that can be called remotely. A gRPC client has a stub that provides the same methods and types as the server.
+OpenCloud uses a gRPC API Gateway (gateway service) to route the requests to the correct service.
+
+### Protobuf
+
+gRPC APIs are typically defined by [Protocol buffers](https://developers.google.com/protocol-buffers/docs/overview). The different client and server stubs are created from `*.proto` files by code generation tools.
+
+## Versioning
+
+There are different standards for API versioning: Through URL, through request parameter, through custom header and through content negotiation. OpenCloud uses the versioning by URL concept although this creates a big code footprint. The versioning follows [SemVer](https://semver.org). We update the major version number when breaking changes are needed. Clients can decide which major version they use through the request URL. The specific implementation is documented on each API.
diff --git a/versioned_docs/version-7.x/dev/server/configuration/config-system.md b/versioned_docs/version-7.x/dev/server/configuration/config-system.md
new file mode 100644
index 000000000..d434c09c4
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/configuration/config-system.md
@@ -0,0 +1,131 @@
+---
+title: Configuration System
+sidebar_position: 2
+slug: /dev/server/configuration/config-system
+---
+
+The Opencloud configuration system is designed for cloud‑native deployments and follows the 12‑Factor App principles. It provides a predictable override pattern, clear configuration locations, and a consistent approach across all services.
+
+- Cloud‑native: configuration is externalized from code and deployable via files, ConfigMaps/Secrets, or environment variables.
+- 12‑Factor friendly: environment variables are first‑class citizens; immutable images with runtime configuration injected at deploy time.
+- Composable: a global base config can be refined by per‑service files and finally overridden by environment variables.
+
+## Defaults
+
+The Opencloud services come with sensible default settings for most configuration options. These defaults are configured within each service and are listed in the service documentation for each individual service.
+
+:::tip
+Default values for all configuration options are built into each service. You only need to provide values for settings that differ from the defaults.
+:::
+
+### Configuration locations
+
+- Containers (default): `/etc/opencloud`
+  - Mount this directory into containers (Docker, Kubernetes) via ConfigMaps/Secrets or volumes.
+- Binary releases and local installs: `$HOME/.opencloud/config/`
+  - Useful when running downloaded binaries on developer laptops or bare hosts without container mounts.
+- The location for the configuration files can be changed by setting the environment variable `OC_CONFIG_DIR` to point to a different directory.
+- Typical files inside either location:
+  - `opencloud.yaml` — global defaults shared by all services
+  - `<service-name>.yaml` — overrides specific to a service (e.g. `activitylog.yaml`, `proxy.yaml`)
+
+### Override pattern (precedence)
+
+From lowest to highest precedence:
+
+1. `opencloud.yaml` (global defaults)
+2. `<service-name>.yaml` (service‑specific overrides)
+3. Environment variables (highest precedence)
+
+Environment variables always win over file values. If a key is not set at a higher level, it falls back to the next level down.
+
+### Config via YAML files
+
+- YAML is used for both the global file and per‑service files.
+- Keep keys lowercase with hyphens or underscores, matching service documentation.
+- Secrets should be provided via environment variables or secret mounts rather than committed files.
+- Simple bash substitution is supported. E.g. `https://${COLLABORA_DOMAIN|collabora.opencloud.test}/` will use the value of `COLLABORA_DOMAIN` env var or default to `collabora.opencloud.test` if not set.
+
+#### Bash substitution syntax
+
+| **Expression**     | **Meaning**                                                          |
+| ------------------ | -------------------------------------------------------------------- |
+| `${var}`           | Value of var (same as `$var`)                                        |
+| `${var-$DEFAULT}`  | If var not set, evaluate expression as $DEFAULT                      |
+| `${var:-$DEFAULT}` | If var not set or is empty, evaluate expression as $DEFAULT          |
+| `${var=$DEFAULT}`  | If var not set, evaluate expression as $DEFAULT                      |
+| `${var:=$DEFAULT}` | If var not set or is empty, evaluate expression as $DEFAULT          |
+| `${var+$OTHER}`    | If var set, evaluate expression as $OTHER, otherwise as empty string |
+| `${var:+$OTHER}`   | If var set, evaluate expression as $OTHER, otherwise as empty string |
+| `$$var`            | Escape expressions. Result will be `$var`.                           |
+
+#### Example: `opencloud.yaml`
+
+```yaml
+# /etc/opencloud/opencloud.yaml
+# Global OpenCloud configuration defaults
+token_manager:
+  jwt_secret: 'x8Kz$3vQw9!Rb7#NfU2^BgT%Lp1@Hm0'
+machine_auth_api_key: 'X7gH2k9Vb4q!S6dP'
+system_user_api_key: 'mS9#cR4pZx7%aL1t'
+transfer_secret: 'Tq6!vB2^nY8@wF5z'
+url_signing_secret: 'U9p$R0e!K3#sH7cQ'
+system_user_id: d3b1f5a2-7c9d-4e2f-a1b2-3c4d5e6f7a8b
+admin_user_id: a1f2e3d4-5b6c-7d8e-9f01-23456789abcd
+## Service-specific configurations, same as in <service-name>.yaml files
+graph:
+  application:
+    id: a72387e1-fb22-49c9-9c94-12ff0abf9b38
+  events:
+    tls_insecure: true
+  spaces:
+    insecure: true
+```
+
+#### Example: `proxy.yaml`
+
+```yaml
+# /etc/opencloud/proxy.yaml
+role_assignment:
+  driver: oidc
+  oidc_role_mapper:
+    role_claim: opencloudRoles
+    role_mapping:
+      - role_name: admin
+        claim_value: myAdminRole
+      - role_name: spaceadmin
+        claim_value: mySpaceAdminRole
+      - role_name: user
+        claim_value: myUserRole
+      - role_name: user-light
+        claim_value: myGuestRole
+```
+
+### Environment variables
+
+- Global scope: variables prefixed with `OC_` apply to more than one service (shared/global settings).
+- Service scope: variables prefixed with `<SERVICENAME>_` apply only to that specific service (e.g. `ACTIVITYLOG_`, `PROXY_`, `FRONTEND_`).
+- When both are present for the same setting, the service‑scoped variable wins for that service.
+- Booleans: `true`/`false` (case‑insensitive).
+- Numbers: plain integers/floats.
+- Lists: comma‑separated values unless otherwise specified by the service.
+
+Examples:
+
+```bash
+# Raise log level globally for all services
+export OC_LOG_LEVEL=debug
+
+# Override only the Proxy service log level
+export PROXY_LOG_LEVEL=info
+
+# Make public shares not require a password globally
+export OC_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD=false
+```
+
+Environment variables take precedence over both `opencloud.yaml` and `<service-name>.yaml`. See the list of [global variables](./global-environment-variables)
+
+### More information
+
+- [Global environment variable reference](./global-environment-variables)
+- Individual service pages for service‑specific options and examples (e.g. [Activity Log](../services/activitylog/), [Proxy](../services/proxy/), [Frontend](../services/frontend)/).
diff --git a/versioned_docs/version-7.x/dev/server/configuration/global-envvars.mdx b/versioned_docs/version-7.x/dev/server/configuration/global-envvars.mdx
new file mode 100644
index 000000000..4e054eb41
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/configuration/global-envvars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: global-envvars
+slug: global-environment-variables
+title: Global Environment Variables
+---
+
+import Envvars from '../../../_static/env-vars/global_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/configuration/global/_category_.json b/versioned_docs/version-7.x/dev/server/configuration/global/_category_.json
new file mode 100644
index 000000000..771114aa9
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/configuration/global/_category_.json
@@ -0,0 +1,3 @@
+{
+  "label": "Global Cnfiguration"
+}
\ No newline at end of file
diff --git a/versioned_docs/version-7.x/dev/server/configuration/index.md b/versioned_docs/version-7.x/dev/server/configuration/index.md
new file mode 100644
index 000000000..a1ba46fd7
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/configuration/index.md
@@ -0,0 +1,4 @@
+---
+title: Configuration
+sidebar_position: 1
+---
diff --git a/versioned_docs/version-7.x/dev/server/index.md b/versioned_docs/version-7.x/dev/server/index.md
new file mode 100644
index 000000000..51bfd4d4d
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/index.md
@@ -0,0 +1,8 @@
+---
+title: 'Architecture'
+sidebar_position: 1
+---
+
+Our current Architecture Diagrams can be found <a href="/likec4" target="_blank">here</a>.
+
+You’ll find the Libre Graph API documentation by clicking <a href="https://docs.opencloud.eu/swagger/libre-graph-api/" target="_blank">this link</a>.
diff --git a/versioned_docs/version-7.x/dev/server/services/_category_.json b/versioned_docs/version-7.x/dev/server/services/_category_.json
new file mode 100644
index 000000000..e2cbad408
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Services",
+  "position": 2
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/activitylog/_category_.json b/versioned_docs/version-7.x/dev/server/services/activitylog/_category_.json
new file mode 100644
index 000000000..40429492e
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/activitylog/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Activitylog",
+  "position": 1
+}
\ No newline at end of file
diff --git a/versioned_docs/version-7.x/dev/server/services/activitylog/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/activitylog/env-vars.mdx
new file mode 100644
index 000000000..058f56097
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/activitylog/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: activitylog-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/activitylog_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/activitylog/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/activitylog/example-config.mdx
new file mode 100644
index 000000000..b7bbf59de
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/activitylog/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: activitylog-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/activitylog.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/activitylog/index.md b/versioned_docs/version-7.x/dev/server/services/activitylog/index.md
new file mode 100644
index 000000000..f6f8838ac
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/activitylog/index.md
@@ -0,0 +1,11 @@
+---
+title: Activity Log
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Activity Log" service_machine_name="activitylog" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/activitylog/info.mdx b/versioned_docs/version-7.x/dev/server/services/activitylog/info.mdx
new file mode 100644
index 000000000..4e88c7fb4
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/activitylog/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: activitylog-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/activitylog_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/antivirus/_category_.json b/versioned_docs/version-7.x/dev/server/services/antivirus/_category_.json
new file mode 100644
index 000000000..f68f07441
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/antivirus/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Antivirus",
+  "position": 2
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/antivirus/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/antivirus/env-vars.mdx
new file mode 100644
index 000000000..255c06abd
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/antivirus/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: antivirus-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/antivirus_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/antivirus/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/antivirus/example-config.mdx
new file mode 100644
index 000000000..183f189b4
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/antivirus/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: antivirus-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/antivirus.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/antivirus/index.md b/versioned_docs/version-7.x/dev/server/services/antivirus/index.md
new file mode 100644
index 000000000..2af1e4f74
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/antivirus/index.md
@@ -0,0 +1,11 @@
+---
+title: Antivirus
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Antivirus" service_machine_name="antivirus" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/antivirus/info.mdx b/versioned_docs/version-7.x/dev/server/services/antivirus/info.mdx
new file mode 100644
index 000000000..cbb01e3f6
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/antivirus/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: antivirus-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/antivirus_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/app-provider/_category_.json b/versioned_docs/version-7.x/dev/server/services/app-provider/_category_.json
new file mode 100644
index 000000000..07e4ec980
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/app-provider/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "App-provider",
+  "position": 3
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/app-provider/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/app-provider/env-vars.mdx
new file mode 100644
index 000000000..0f515b592
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/app-provider/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: app-provider-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/app-provider_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/app-provider/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/app-provider/example-config.mdx
new file mode 100644
index 000000000..1bc43deff
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/app-provider/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: app-provider-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/app-provider.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/app-provider/index.md b/versioned_docs/version-7.x/dev/server/services/app-provider/index.md
new file mode 100644
index 000000000..baf775758
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/app-provider/index.md
@@ -0,0 +1,11 @@
+---
+title: App Provider
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="App Provider" service_machine_name="app-provider" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/app-registry/_category_.json b/versioned_docs/version-7.x/dev/server/services/app-registry/_category_.json
new file mode 100644
index 000000000..3b0316a9a
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/app-registry/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "App-registry",
+  "position": 4
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/app-registry/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/app-registry/env-vars.mdx
new file mode 100644
index 000000000..455d178de
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/app-registry/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: app-registry-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/app-registry_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/app-registry/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/app-registry/example-config.mdx
new file mode 100644
index 000000000..4378ca3b5
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/app-registry/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: app-registry-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/app-registry.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/app-registry/index.md b/versioned_docs/version-7.x/dev/server/services/app-registry/index.md
new file mode 100644
index 000000000..b2832d83c
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/app-registry/index.md
@@ -0,0 +1,11 @@
+---
+title: App Registry
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="App Registry" service_machine_name="app-registry" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/app-registry/info.mdx b/versioned_docs/version-7.x/dev/server/services/app-registry/info.mdx
new file mode 100644
index 000000000..385ae0350
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/app-registry/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: app-registry-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/app-registry_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/audit/_category_.json b/versioned_docs/version-7.x/dev/server/services/audit/_category_.json
new file mode 100644
index 000000000..7af484e69
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/audit/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Audit",
+  "position": 5
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/audit/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/audit/env-vars.mdx
new file mode 100644
index 000000000..b5c2a8577
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/audit/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: audit-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/audit_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/audit/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/audit/example-config.mdx
new file mode 100644
index 000000000..e4fa421fe
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/audit/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: audit-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/audit.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/audit/index.md b/versioned_docs/version-7.x/dev/server/services/audit/index.md
new file mode 100644
index 000000000..04580820b
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/audit/index.md
@@ -0,0 +1,11 @@
+---
+title: Audit
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Audit" service_machine_name="audit" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/audit/info.mdx b/versioned_docs/version-7.x/dev/server/services/audit/info.mdx
new file mode 100644
index 000000000..82ec9d03b
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/audit/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: audit-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/audit_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-app/_category_.json b/versioned_docs/version-7.x/dev/server/services/auth-app/_category_.json
new file mode 100644
index 000000000..da45d67cf
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-app/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Auth-app",
+  "position": 6
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-app/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/auth-app/env-vars.mdx
new file mode 100644
index 000000000..6f3c0e8c2
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-app/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: auth-app-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/auth-app_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-app/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/auth-app/example-config.mdx
new file mode 100644
index 000000000..f26ddfb8d
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-app/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: auth-app-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/auth-app.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-app/index.md b/versioned_docs/version-7.x/dev/server/services/auth-app/index.md
new file mode 100644
index 000000000..97a2a7e3d
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-app/index.md
@@ -0,0 +1,11 @@
+---
+title: Auth App
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Auth App" service_machine_name="auth-app" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-app/info.mdx b/versioned_docs/version-7.x/dev/server/services/auth-app/info.mdx
new file mode 100644
index 000000000..64f54f6e0
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-app/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: auth-app-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/auth-app_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-basic/_category_.json b/versioned_docs/version-7.x/dev/server/services/auth-basic/_category_.json
new file mode 100644
index 000000000..4bf1eb162
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-basic/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Auth-basic",
+  "position": 7
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-basic/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/auth-basic/env-vars.mdx
new file mode 100644
index 000000000..3748d1418
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-basic/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: auth-basic-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/auth-basic_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-basic/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/auth-basic/example-config.mdx
new file mode 100644
index 000000000..7360e0383
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-basic/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: auth-basic-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/auth-basic.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-basic/index.md b/versioned_docs/version-7.x/dev/server/services/auth-basic/index.md
new file mode 100644
index 000000000..e0a94eb87
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-basic/index.md
@@ -0,0 +1,11 @@
+---
+title: Auth Basic
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Auth Basic" service_machine_name="auth-basic" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-basic/info.mdx b/versioned_docs/version-7.x/dev/server/services/auth-basic/info.mdx
new file mode 100644
index 000000000..31ecb9738
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-basic/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: auth-basic-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/auth-basic_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-bearer/_category_.json b/versioned_docs/version-7.x/dev/server/services/auth-bearer/_category_.json
new file mode 100644
index 000000000..f50be5ee2
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-bearer/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Auth-bearer",
+  "position": 8
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-bearer/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/auth-bearer/env-vars.mdx
new file mode 100644
index 000000000..7a42d9877
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-bearer/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: auth-bearer-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/auth-bearer_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-bearer/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/auth-bearer/example-config.mdx
new file mode 100644
index 000000000..3a91b9d9d
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-bearer/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: auth-bearer-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/auth-bearer.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-bearer/index.md b/versioned_docs/version-7.x/dev/server/services/auth-bearer/index.md
new file mode 100644
index 000000000..40796cf66
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-bearer/index.md
@@ -0,0 +1,11 @@
+---
+title: Auth Bearer
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Auth Bearer" service_machine_name="auth-bearer" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-bearer/info.mdx b/versioned_docs/version-7.x/dev/server/services/auth-bearer/info.mdx
new file mode 100644
index 000000000..73ad0d8ba
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-bearer/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: auth-bearer-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/auth-bearer_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-machine/_category_.json b/versioned_docs/version-7.x/dev/server/services/auth-machine/_category_.json
new file mode 100644
index 000000000..d7cf7e295
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-machine/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Auth-machine",
+  "position": 9
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-machine/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/auth-machine/env-vars.mdx
new file mode 100644
index 000000000..9668c0b69
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-machine/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: auth-machine-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/auth-machine_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-machine/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/auth-machine/example-config.mdx
new file mode 100644
index 000000000..a7bfd110b
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-machine/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: auth-machine-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/auth-machine.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-machine/index.md b/versioned_docs/version-7.x/dev/server/services/auth-machine/index.md
new file mode 100644
index 000000000..8065a6830
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-machine/index.md
@@ -0,0 +1,11 @@
+---
+title: Auth Machine
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Auth Machine" service_machine_name="auth-machine" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-machine/info.mdx b/versioned_docs/version-7.x/dev/server/services/auth-machine/info.mdx
new file mode 100644
index 000000000..7b5e605ef
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-machine/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: auth-machine-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/auth-machine_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-service/_category_.json b/versioned_docs/version-7.x/dev/server/services/auth-service/_category_.json
new file mode 100644
index 000000000..371db847f
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-service/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Auth-service",
+  "position": 10
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-service/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/auth-service/env-vars.mdx
new file mode 100644
index 000000000..b9ed72921
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-service/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: auth-service-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/auth-service_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-service/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/auth-service/example-config.mdx
new file mode 100644
index 000000000..c449d2ff7
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-service/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: auth-service-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/auth-service.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-service/index.md b/versioned_docs/version-7.x/dev/server/services/auth-service/index.md
new file mode 100644
index 000000000..4449b2062
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-service/index.md
@@ -0,0 +1,11 @@
+---
+title: Auth Service
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Auth Service" service_machine_name="auth-service" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/auth-service/info.mdx b/versioned_docs/version-7.x/dev/server/services/auth-service/info.mdx
new file mode 100644
index 000000000..c5cccfb0d
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/auth-service/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: auth-service-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/auth-service_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/clientlog/_category_.json b/versioned_docs/version-7.x/dev/server/services/clientlog/_category_.json
new file mode 100644
index 000000000..5c624596a
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/clientlog/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Clientlog",
+  "position": 11
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/clientlog/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/clientlog/env-vars.mdx
new file mode 100644
index 000000000..0d1e70c1c
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/clientlog/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: clientlog-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/clientlog_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/clientlog/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/clientlog/example-config.mdx
new file mode 100644
index 000000000..c22a8fc90
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/clientlog/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: clientlog-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/clientlog.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/clientlog/index.md b/versioned_docs/version-7.x/dev/server/services/clientlog/index.md
new file mode 100644
index 000000000..e9bbc5f30
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/clientlog/index.md
@@ -0,0 +1,11 @@
+---
+title: Client Log
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Client Log" service_machine_name="clientlog" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/clientlog/info.mdx b/versioned_docs/version-7.x/dev/server/services/clientlog/info.mdx
new file mode 100644
index 000000000..2ea0dd240
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/clientlog/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: clientlog-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/clientlog_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/collaboration/_category_.json b/versioned_docs/version-7.x/dev/server/services/collaboration/_category_.json
new file mode 100644
index 000000000..697a2897f
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/collaboration/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Collaboration",
+  "position": 12
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/collaboration/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/collaboration/env-vars.mdx
new file mode 100644
index 000000000..2668f66fa
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/collaboration/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: collaboration-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/collaboration_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/collaboration/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/collaboration/example-config.mdx
new file mode 100644
index 000000000..fc1281109
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/collaboration/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: collaboration-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/collaboration.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/collaboration/index.md b/versioned_docs/version-7.x/dev/server/services/collaboration/index.md
new file mode 100644
index 000000000..ae28f7924
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/collaboration/index.md
@@ -0,0 +1,11 @@
+---
+title: Collaboration
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Collaboration" service_machine_name="collaboration" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/collaboration/info.mdx b/versioned_docs/version-7.x/dev/server/services/collaboration/info.mdx
new file mode 100644
index 000000000..67cdffb07
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/collaboration/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: collaboration-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/collaboration_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/eventhistory/_category_.json b/versioned_docs/version-7.x/dev/server/services/eventhistory/_category_.json
new file mode 100644
index 000000000..359221c6f
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/eventhistory/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Eventhistory",
+  "position": 13
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/eventhistory/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/eventhistory/env-vars.mdx
new file mode 100644
index 000000000..755eafb1d
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/eventhistory/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: eventhistory-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/eventhistory_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/eventhistory/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/eventhistory/example-config.mdx
new file mode 100644
index 000000000..00d776421
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/eventhistory/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: eventhistory-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/eventhistory.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/eventhistory/index.md b/versioned_docs/version-7.x/dev/server/services/eventhistory/index.md
new file mode 100644
index 000000000..e79d750a9
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/eventhistory/index.md
@@ -0,0 +1,11 @@
+---
+title: Event History
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Event History" service_machine_name="eventhistory" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/eventhistory/info.mdx b/versioned_docs/version-7.x/dev/server/services/eventhistory/info.mdx
new file mode 100644
index 000000000..0c018722d
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/eventhistory/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: eventhistory-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/eventhistory_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/frontend/_category_.json b/versioned_docs/version-7.x/dev/server/services/frontend/_category_.json
new file mode 100644
index 000000000..c2c4c2a8d
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/frontend/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Frontend",
+  "position": 14
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/frontend/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/frontend/env-vars.mdx
new file mode 100644
index 000000000..9ec5b4e38
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/frontend/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: frontend-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/frontend_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/frontend/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/frontend/example-config.mdx
new file mode 100644
index 000000000..55fe3e5bc
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/frontend/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: frontend-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/frontend.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/frontend/index.md b/versioned_docs/version-7.x/dev/server/services/frontend/index.md
new file mode 100644
index 000000000..518c009c1
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/frontend/index.md
@@ -0,0 +1,11 @@
+---
+title: Frontend
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Frontend" service_machine_name="frontend" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/frontend/info.mdx b/versioned_docs/version-7.x/dev/server/services/frontend/info.mdx
new file mode 100644
index 000000000..ef8e79de2
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/frontend/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: frontend-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/frontend_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/gateway/_category_.json b/versioned_docs/version-7.x/dev/server/services/gateway/_category_.json
new file mode 100644
index 000000000..933994ddf
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/gateway/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Gateway",
+  "position": 15
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/gateway/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/gateway/env-vars.mdx
new file mode 100644
index 000000000..f3cf079c3
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/gateway/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: gateway-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/gateway_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/gateway/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/gateway/example-config.mdx
new file mode 100644
index 000000000..b42cfa172
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/gateway/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: gateway-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/gateway.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/gateway/index.md b/versioned_docs/version-7.x/dev/server/services/gateway/index.md
new file mode 100644
index 000000000..5a0f12ae8
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/gateway/index.md
@@ -0,0 +1,11 @@
+---
+title: Gateway
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Gateway" service_machine_name="gateway" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/gateway/info.mdx b/versioned_docs/version-7.x/dev/server/services/gateway/info.mdx
new file mode 100644
index 000000000..94ce34d05
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/gateway/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: gateway-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/gateway_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/graph/_category_.json b/versioned_docs/version-7.x/dev/server/services/graph/_category_.json
new file mode 100644
index 000000000..2ba522f77
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/graph/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Graph",
+  "position": 16
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/graph/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/graph/env-vars.mdx
new file mode 100644
index 000000000..ddd8584a3
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/graph/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: graph-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/graph_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/graph/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/graph/example-config.mdx
new file mode 100644
index 000000000..ec0232f76
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/graph/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: graph-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/graph.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/graph/index.md b/versioned_docs/version-7.x/dev/server/services/graph/index.md
new file mode 100644
index 000000000..1d18789ed
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/graph/index.md
@@ -0,0 +1,11 @@
+---
+title: Graph
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Graph" service_machine_name="graph" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/graph/info.mdx b/versioned_docs/version-7.x/dev/server/services/graph/info.mdx
new file mode 100644
index 000000000..174802593
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/graph/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: graph-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/graph_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/groups/_category_.json b/versioned_docs/version-7.x/dev/server/services/groups/_category_.json
new file mode 100644
index 000000000..59e8a2312
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/groups/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Groups",
+  "position": 17
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/groups/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/groups/env-vars.mdx
new file mode 100644
index 000000000..091fa2a4c
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/groups/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: groups-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/groups_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/groups/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/groups/example-config.mdx
new file mode 100644
index 000000000..3774d6917
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/groups/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: groups-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/groups.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/groups/index.md b/versioned_docs/version-7.x/dev/server/services/groups/index.md
new file mode 100644
index 000000000..0a19f385c
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/groups/index.md
@@ -0,0 +1,11 @@
+---
+title: Groups
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Groups" service_machine_name="groups" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/idm/_category_.json b/versioned_docs/version-7.x/dev/server/services/idm/_category_.json
new file mode 100644
index 000000000..c61bf1cf8
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/idm/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Idm",
+  "position": 18
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/idm/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/idm/env-vars.mdx
new file mode 100644
index 000000000..9100d2233
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/idm/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: idm-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/idm_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/idm/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/idm/example-config.mdx
new file mode 100644
index 000000000..ce70c343d
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/idm/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: idm-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/idm.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/idm/index.md b/versioned_docs/version-7.x/dev/server/services/idm/index.md
new file mode 100644
index 000000000..53c59ac9b
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/idm/index.md
@@ -0,0 +1,11 @@
+---
+title: IDM
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="IDM" service_machine_name="idm" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/idm/info.mdx b/versioned_docs/version-7.x/dev/server/services/idm/info.mdx
new file mode 100644
index 000000000..380116015
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/idm/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: idm-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/idm_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/idp/_category_.json b/versioned_docs/version-7.x/dev/server/services/idp/_category_.json
new file mode 100644
index 000000000..077892de0
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/idp/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Idp",
+  "position": 19
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/idp/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/idp/env-vars.mdx
new file mode 100644
index 000000000..9c216b055
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/idp/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: idp-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/idp_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/idp/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/idp/example-config.mdx
new file mode 100644
index 000000000..7653c5f85
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/idp/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: idp-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/idp.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/idp/index.md b/versioned_docs/version-7.x/dev/server/services/idp/index.md
new file mode 100644
index 000000000..6b6a894b9
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/idp/index.md
@@ -0,0 +1,11 @@
+---
+title: IDP
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="IDP" service_machine_name="idp" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/idp/info.mdx b/versioned_docs/version-7.x/dev/server/services/idp/info.mdx
new file mode 100644
index 000000000..e84b24cd0
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/idp/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: idp-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/idp_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/invitations/_category_.json b/versioned_docs/version-7.x/dev/server/services/invitations/_category_.json
new file mode 100644
index 000000000..c4fca62fe
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/invitations/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Invitations",
+  "position": 20
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/invitations/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/invitations/env-vars.mdx
new file mode 100644
index 000000000..df6bd120f
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/invitations/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: invitations-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/invitations_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/invitations/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/invitations/example-config.mdx
new file mode 100644
index 000000000..49023a856
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/invitations/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: invitations-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/invitations.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/invitations/index.md b/versioned_docs/version-7.x/dev/server/services/invitations/index.md
new file mode 100644
index 000000000..e25d40fd4
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/invitations/index.md
@@ -0,0 +1,11 @@
+---
+title: Invitations
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Invitations" service_machine_name="invitations" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/invitations/info.mdx b/versioned_docs/version-7.x/dev/server/services/invitations/info.mdx
new file mode 100644
index 000000000..cc3fe2811
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/invitations/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: invitations-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/invitations_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/nats/_category_.json b/versioned_docs/version-7.x/dev/server/services/nats/_category_.json
new file mode 100644
index 000000000..9360d681a
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/nats/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Nats",
+  "position": 21
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/nats/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/nats/env-vars.mdx
new file mode 100644
index 000000000..f65363752
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/nats/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: nats-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/nats_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/nats/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/nats/example-config.mdx
new file mode 100644
index 000000000..f8b2dcc1a
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/nats/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: nats-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/nats.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/nats/index.md b/versioned_docs/version-7.x/dev/server/services/nats/index.md
new file mode 100644
index 000000000..ec7a19b7d
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/nats/index.md
@@ -0,0 +1,11 @@
+---
+title: NATS
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="NATS" service_machine_name="nats" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/nats/info.mdx b/versioned_docs/version-7.x/dev/server/services/nats/info.mdx
new file mode 100644
index 000000000..2c994db0f
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/nats/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: nats-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/nats_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/notifications/_category_.json b/versioned_docs/version-7.x/dev/server/services/notifications/_category_.json
new file mode 100644
index 000000000..6083f7897
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/notifications/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Notifications",
+  "position": 22
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/notifications/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/notifications/env-vars.mdx
new file mode 100644
index 000000000..6fad47068
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/notifications/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: notifications-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/notifications_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/notifications/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/notifications/example-config.mdx
new file mode 100644
index 000000000..365806916
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/notifications/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: notifications-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/notifications.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/notifications/index.md b/versioned_docs/version-7.x/dev/server/services/notifications/index.md
new file mode 100644
index 000000000..7796028a3
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/notifications/index.md
@@ -0,0 +1,11 @@
+---
+title: Notifications
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Notifications" service_machine_name="notifications" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/notifications/info.mdx b/versioned_docs/version-7.x/dev/server/services/notifications/info.mdx
new file mode 100644
index 000000000..baeb23fc3
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/notifications/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: notifications-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/notifications_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/ocm/_category_.json b/versioned_docs/version-7.x/dev/server/services/ocm/_category_.json
new file mode 100644
index 000000000..0b3e0e623
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/ocm/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Ocm",
+  "position": 24
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/ocm/create-share-flow.md b/versioned_docs/version-7.x/dev/server/services/ocm/create-share-flow.md
new file mode 100644
index 000000000..edf31fe31
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/ocm/create-share-flow.md
@@ -0,0 +1,60 @@
+---
+title: Create Share Flow
+sidebar_position: 2
+---
+
+Ths diagram illustrates the flow of creating a share from Instance A to Instance B using the OCM (Open Cloud Mesh) protocol.
+
+```mermaid
+sequenceDiagram
+box Instance A
+participant osp as ocmsharesprovider
+participant gwa as Gateway A
+participant httpa as ocs
+end
+actor usera as User A
+box Instance B
+participant httpb as ocmd
+participant gwb as Gateway B
+participant ocmc as OCMCore
+end
+
+    Note over usera: A shares a resource with B
+    usera->>+httpa: CreateShare
+        httpa->>+gwa: GetInfoByDomain
+        Note left of gwa: GetInfoByDomain (ocmproviderauthorizer)
+        gwa-->>-httpa: return
+
+        httpa->>+gwa: GetAcceptedUser
+        Note left of gwa: GetAcceptedUser (ocminvitemanager)
+        gwa-->>-httpa: return
+
+        httpa->>+gwa: CreateOCMShare
+            gwa->>+osp: CreateOCMShare
+                osp->>+gwa: Stat
+                gwa-->>-osp: return
+
+                Note left of osp: store share in repo
+
+                osp->>+httpb: POST /shares
+                    httpb->>+gwb: IsProviderAllowed
+                    Note right of gwb: IsProviderAllowed (ocmproviderauthorizer)
+                    gwb-->>-httpb: return
+
+                    httpb->>+gwb: GetUser
+                    Note right of gwb: GetUser (userprovider)
+                    gwb-->>-httpb: return
+
+                    httpb->>+gwb: CreateOCMCoreShare
+                        gwb->>+ocmc: CreateOCMCoreShare
+                        Note right of ocmc: StoreReceivedShare
+                        ocmc-->>-gwb: return
+                    gwb-->>-httpb: return
+                httpb-->>-osp: return
+            osp-->>-gwa: return
+        gwa-->>-httpa: return
+        httpa->>+gwa: Stat
+            Note left of gwa: Stat (storageprovider)
+        gwa-->>-httpa: return
+    httpa-->>-usera: return
+```
diff --git a/versioned_docs/version-7.x/dev/server/services/ocm/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/ocm/env-vars.mdx
new file mode 100644
index 000000000..7fbe80a75
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/ocm/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 3
+id: ocm-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/ocm_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/ocm/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/ocm/example-config.mdx
new file mode 100644
index 000000000..bd89699a5
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/ocm/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 4
+id: ocm-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/ocm.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/ocm/index.md b/versioned_docs/version-7.x/dev/server/services/ocm/index.md
new file mode 100644
index 000000000..fb50d5474
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/ocm/index.md
@@ -0,0 +1,11 @@
+---
+title: OCM
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="OCM" service_machine_name="ocm" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/ocm/info.mdx b/versioned_docs/version-7.x/dev/server/services/ocm/info.mdx
new file mode 100644
index 000000000..575a80221
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/ocm/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: ocm-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/ocm_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/ocm/invitation-flow.md b/versioned_docs/version-7.x/dev/server/services/ocm/invitation-flow.md
new file mode 100644
index 000000000..2f88c8330
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/ocm/invitation-flow.md
@@ -0,0 +1,50 @@
+---
+title: Invitation Flow
+sidebar_position: 2
+---
+
+This diagram illustrates the flow of creating and accepting an invitation token between two instances (A and B) in a federated environment.
+
+```mermaid
+sequenceDiagram
+box Instance A
+participant ima as InviteManager A
+participant gwa as Gateway A
+participant httpa as HTTP Api A (ocm, sm)
+end
+actor usera as User A
+actor userb as User B
+box Instance B
+participant httpb as HTTP Api B (ocm, sm)
+participant gwb as Gateway B
+participant imb as InviteManager B
+end
+
+    Note over usera: A creates invitation token
+    usera->>+httpa: POST /generate-invite (sciencemesh)
+        httpa->>+gwa: GenerateInviteToken
+            gwa->>+ima: GenerateInviteToken
+                Note left of ima: store token in repo
+            ima-->>-gwa: return token
+        gwa-->>-httpa: return token
+    httpa-->>-usera: return token
+
+    Note over usera,userb: A passes token to B
+
+    Note over userb: B accepts invitation
+    userb->>+httpb: POST /accept-invite (sciencemesh)
+        httpb->>+gwb: ForwardInvite
+            gwb->>+imb: ForwardInvite
+                imb->>+httpa: POST /invite-accepted (ocm)
+                    httpa->>+gwa: AcceptInvite
+                        gwa->>+ima: AcceptInvite
+                             Note left of ima: get token from repo
+                             Note left of ima: add remote user
+                        ima-->>-gwa: return
+                    gwa-->>-httpa: return remote user
+                httpa->>-imb: return remote user
+                Note right of imb: add remote user
+            imb-->>-gwb: return
+        gwb-->>-httpb: return
+    httpb-->>-userb: return
+```
diff --git a/versioned_docs/version-7.x/dev/server/services/ocs/_category_.json b/versioned_docs/version-7.x/dev/server/services/ocs/_category_.json
new file mode 100644
index 000000000..c31abfc7c
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/ocs/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Ocs",
+  "position": 25
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/ocs/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/ocs/env-vars.mdx
new file mode 100644
index 000000000..85be8b55b
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/ocs/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: ocs-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/ocs_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/ocs/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/ocs/example-config.mdx
new file mode 100644
index 000000000..98d4dde3d
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/ocs/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: ocs-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/ocs.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/ocs/index.md b/versioned_docs/version-7.x/dev/server/services/ocs/index.md
new file mode 100644
index 000000000..424a11e61
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/ocs/index.md
@@ -0,0 +1,11 @@
+---
+title: OCS
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="OCS" service_machine_name="ocs" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/ocs/info.mdx b/versioned_docs/version-7.x/dev/server/services/ocs/info.mdx
new file mode 100644
index 000000000..b1169769b
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/ocs/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: ocs-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/ocs_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/policies/_category_.json b/versioned_docs/version-7.x/dev/server/services/policies/_category_.json
new file mode 100644
index 000000000..eaa510255
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/policies/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Policies",
+  "position": 26
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/policies/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/policies/env-vars.mdx
new file mode 100644
index 000000000..226a656fb
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/policies/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: policies-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/policies_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/policies/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/policies/example-config.mdx
new file mode 100644
index 000000000..e8024fa6a
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/policies/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: policies-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/policies.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/policies/index.md b/versioned_docs/version-7.x/dev/server/services/policies/index.md
new file mode 100644
index 000000000..2b3332cb4
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/policies/index.md
@@ -0,0 +1,11 @@
+---
+title: Policies
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Policies" service_machine_name="policies" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/policies/info.mdx b/versioned_docs/version-7.x/dev/server/services/policies/info.mdx
new file mode 100644
index 000000000..33c91ddc9
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/policies/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: policies-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/policies_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/postprocessing/_category_.json b/versioned_docs/version-7.x/dev/server/services/postprocessing/_category_.json
new file mode 100644
index 000000000..d5ef775d7
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/postprocessing/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Postprocessing",
+  "position": 27
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/postprocessing/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/postprocessing/env-vars.mdx
new file mode 100644
index 000000000..190900222
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/postprocessing/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: postprocessing-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/postprocessing_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/postprocessing/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/postprocessing/example-config.mdx
new file mode 100644
index 000000000..42daa4094
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/postprocessing/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: postprocessing-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/postprocessing.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/postprocessing/index.md b/versioned_docs/version-7.x/dev/server/services/postprocessing/index.md
new file mode 100644
index 000000000..4829ede37
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/postprocessing/index.md
@@ -0,0 +1,11 @@
+---
+title: Postprocessing
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Postprocessing" service_machine_name="postprocessing" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/postprocessing/info.mdx b/versioned_docs/version-7.x/dev/server/services/postprocessing/info.mdx
new file mode 100644
index 000000000..00ea80a2e
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/postprocessing/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: postprocessing-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/postprocessing_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/proxy/_category_.json b/versioned_docs/version-7.x/dev/server/services/proxy/_category_.json
new file mode 100644
index 000000000..962d7127c
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/proxy/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Proxy",
+  "position": 28
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/proxy/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/proxy/env-vars.mdx
new file mode 100644
index 000000000..40e5e6541
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/proxy/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: proxy-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/proxy_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/proxy/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/proxy/example-config.mdx
new file mode 100644
index 000000000..483c28a71
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/proxy/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: proxy-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/proxy.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/proxy/index.md b/versioned_docs/version-7.x/dev/server/services/proxy/index.md
new file mode 100644
index 000000000..cab5cc122
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/proxy/index.md
@@ -0,0 +1,11 @@
+---
+title: Proxy
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Proxy" service_machine_name="proxy" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/proxy/info.mdx b/versioned_docs/version-7.x/dev/server/services/proxy/info.mdx
new file mode 100644
index 000000000..098d544cd
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/proxy/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: proxy-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/proxy_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/search/_category_.json b/versioned_docs/version-7.x/dev/server/services/search/_category_.json
new file mode 100644
index 000000000..a24d93a51
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/search/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Search",
+  "position": 29
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/search/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/search/env-vars.mdx
new file mode 100644
index 000000000..beab455a5
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/search/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: search-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/search_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/search/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/search/example-config.mdx
new file mode 100644
index 000000000..7ee18a7b8
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/search/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: search-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/search.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/search/index.md b/versioned_docs/version-7.x/dev/server/services/search/index.md
new file mode 100644
index 000000000..7bd32849a
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/search/index.md
@@ -0,0 +1,11 @@
+---
+title: Search
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Search" service_machine_name="search" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/search/info.mdx b/versioned_docs/version-7.x/dev/server/services/search/info.mdx
new file mode 100644
index 000000000..df856e68b
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/search/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: search-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/search_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/settings/_category_.json b/versioned_docs/version-7.x/dev/server/services/settings/_category_.json
new file mode 100644
index 000000000..28b92e258
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/settings/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Settings",
+  "position": 30
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/settings/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/settings/env-vars.mdx
new file mode 100644
index 000000000..3dbb86da0
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/settings/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: settings-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/settings_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/settings/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/settings/example-config.mdx
new file mode 100644
index 000000000..7ea23e207
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/settings/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: settings-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/settings.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/settings/index.md b/versioned_docs/version-7.x/dev/server/services/settings/index.md
new file mode 100644
index 000000000..6c9cafd68
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/settings/index.md
@@ -0,0 +1,11 @@
+---
+title: Settings
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Settings" service_machine_name="settings" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/settings/info.mdx b/versioned_docs/version-7.x/dev/server/services/settings/info.mdx
new file mode 100644
index 000000000..705c8f463
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/settings/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: settings-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/settings_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/sharing/_category_.json b/versioned_docs/version-7.x/dev/server/services/sharing/_category_.json
new file mode 100644
index 000000000..f2c612a47
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/sharing/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Sharing",
+  "position": 31
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/sharing/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/sharing/env-vars.mdx
new file mode 100644
index 000000000..b42522e15
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/sharing/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: sharing-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/sharing_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/sharing/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/sharing/example-config.mdx
new file mode 100644
index 000000000..69fdf0c80
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/sharing/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: sharing-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/sharing.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/sharing/index.md b/versioned_docs/version-7.x/dev/server/services/sharing/index.md
new file mode 100644
index 000000000..05ca5eccc
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/sharing/index.md
@@ -0,0 +1,11 @@
+---
+title: Sharing
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Sharing" service_machine_name="sharing" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/sse/_category_.json b/versioned_docs/version-7.x/dev/server/services/sse/_category_.json
new file mode 100644
index 000000000..cd9dcebad
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/sse/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Sse",
+  "position": 32
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/sse/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/sse/env-vars.mdx
new file mode 100644
index 000000000..bd166e333
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/sse/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: sse-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/sse_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/sse/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/sse/example-config.mdx
new file mode 100644
index 000000000..f27cb4504
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/sse/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: sse-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/sse.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/sse/index.md b/versioned_docs/version-7.x/dev/server/services/sse/index.md
new file mode 100644
index 000000000..aa6d30132
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/sse/index.md
@@ -0,0 +1,11 @@
+---
+title: SSE
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="SSE" service_machine_name="sse" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/sse/info.mdx b/versioned_docs/version-7.x/dev/server/services/sse/info.mdx
new file mode 100644
index 000000000..b278a67f7
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/sse/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: sse-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/sse_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/storage-publiclink/_category_.json b/versioned_docs/version-7.x/dev/server/services/storage-publiclink/_category_.json
new file mode 100644
index 000000000..79ffd1e27
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/storage-publiclink/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Storage-publiclink",
+  "position": 33
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/storage-publiclink/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/storage-publiclink/env-vars.mdx
new file mode 100644
index 000000000..14b77ac66
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/storage-publiclink/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: storage-publiclink-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/storage-publiclink_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/storage-publiclink/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/storage-publiclink/example-config.mdx
new file mode 100644
index 000000000..11cc1af96
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/storage-publiclink/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: storage-publiclink-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/storage-publiclink.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/storage-publiclink/index.md b/versioned_docs/version-7.x/dev/server/services/storage-publiclink/index.md
new file mode 100644
index 000000000..f5189e75e
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/storage-publiclink/index.md
@@ -0,0 +1,11 @@
+---
+title: Storage Publiclink
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Storage Publiclink" service_machine_name="storage-publiclink" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/storage-shares/_category_.json b/versioned_docs/version-7.x/dev/server/services/storage-shares/_category_.json
new file mode 100644
index 000000000..a2a7ff964
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/storage-shares/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Storage-shares",
+  "position": 34
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/storage-shares/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/storage-shares/env-vars.mdx
new file mode 100644
index 000000000..5f2c51aaa
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/storage-shares/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: storage-shares-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/storage-shares_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/storage-shares/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/storage-shares/example-config.mdx
new file mode 100644
index 000000000..4ad738725
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/storage-shares/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: storage-shares-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/storage-shares.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/storage-shares/index.md b/versioned_docs/version-7.x/dev/server/services/storage-shares/index.md
new file mode 100644
index 000000000..ce18ad725
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/storage-shares/index.md
@@ -0,0 +1,11 @@
+---
+title: Storage Shares
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Storage Shares" service_machine_name="storage-shares" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/storage-system/_category_.json b/versioned_docs/version-7.x/dev/server/services/storage-system/_category_.json
new file mode 100644
index 000000000..087e60aec
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/storage-system/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Storage-system",
+  "position": 35
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/storage-system/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/storage-system/env-vars.mdx
new file mode 100644
index 000000000..86314cb69
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/storage-system/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: storage-system-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/storage-system_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/storage-system/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/storage-system/example-config.mdx
new file mode 100644
index 000000000..4e1e8ba39
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/storage-system/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: storage-system-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/storage-system.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/storage-system/index.md b/versioned_docs/version-7.x/dev/server/services/storage-system/index.md
new file mode 100644
index 000000000..e8f0d9213
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/storage-system/index.md
@@ -0,0 +1,11 @@
+---
+title: Storage System
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Storage System" service_machine_name="storage-system" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/storage-system/info.mdx b/versioned_docs/version-7.x/dev/server/services/storage-system/info.mdx
new file mode 100644
index 000000000..c568358cf
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/storage-system/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: storage-system-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/storage-system_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/storage-users/_category_.json b/versioned_docs/version-7.x/dev/server/services/storage-users/_category_.json
new file mode 100644
index 000000000..b5afad376
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/storage-users/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Storage-users",
+  "position": 36
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/storage-users/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/storage-users/env-vars.mdx
new file mode 100644
index 000000000..f8bd679a4
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/storage-users/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: storage-users-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/storage-users_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/storage-users/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/storage-users/example-config.mdx
new file mode 100644
index 000000000..0024e7c1f
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/storage-users/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: storage-users-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/storage-users.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/storage-users/index.md b/versioned_docs/version-7.x/dev/server/services/storage-users/index.md
new file mode 100644
index 000000000..713c617ab
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/storage-users/index.md
@@ -0,0 +1,11 @@
+---
+title: Storage Users
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Storage Users" service_machine_name="storage-users" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/storage-users/info.mdx b/versioned_docs/version-7.x/dev/server/services/storage-users/info.mdx
new file mode 100644
index 000000000..40b20bb52
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/storage-users/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: storage-users-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/storage-users_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/thumbnails/_category_.json b/versioned_docs/version-7.x/dev/server/services/thumbnails/_category_.json
new file mode 100644
index 000000000..123d2454a
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/thumbnails/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Thumbnails",
+  "position": 37
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/thumbnails/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/thumbnails/env-vars.mdx
new file mode 100644
index 000000000..c2880e21e
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/thumbnails/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: thumbnails-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/thumbnails_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/thumbnails/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/thumbnails/example-config.mdx
new file mode 100644
index 000000000..94086ef13
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/thumbnails/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: thumbnails-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/thumbnails.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/thumbnails/index.md b/versioned_docs/version-7.x/dev/server/services/thumbnails/index.md
new file mode 100644
index 000000000..00b807602
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/thumbnails/index.md
@@ -0,0 +1,11 @@
+---
+title: Thumbnails
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Thumbnails" service_machine_name="thumbnails" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/thumbnails/info.mdx b/versioned_docs/version-7.x/dev/server/services/thumbnails/info.mdx
new file mode 100644
index 000000000..111cc4bdb
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/thumbnails/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: thumbnails-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/thumbnails_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/userlog/_category_.json b/versioned_docs/version-7.x/dev/server/services/userlog/_category_.json
new file mode 100644
index 000000000..ff7efe7d7
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/userlog/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Userlog",
+  "position": 38
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/userlog/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/userlog/env-vars.mdx
new file mode 100644
index 000000000..1788b7b68
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/userlog/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: userlog-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/userlog_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/userlog/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/userlog/example-config.mdx
new file mode 100644
index 000000000..245a53282
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/userlog/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: userlog-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/userlog.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/userlog/index.md b/versioned_docs/version-7.x/dev/server/services/userlog/index.md
new file mode 100644
index 000000000..bd56f2383
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/userlog/index.md
@@ -0,0 +1,11 @@
+---
+title: User Log
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="User Log" service_machine_name="userlog" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/userlog/info.mdx b/versioned_docs/version-7.x/dev/server/services/userlog/info.mdx
new file mode 100644
index 000000000..8417669d9
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/userlog/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: userlog-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/userlog_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/users/_category_.json b/versioned_docs/version-7.x/dev/server/services/users/_category_.json
new file mode 100644
index 000000000..d4a77d51c
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/users/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Users",
+  "position": 39
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/users/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/users/env-vars.mdx
new file mode 100644
index 000000000..2c45e122b
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/users/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: users-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/users_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/users/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/users/example-config.mdx
new file mode 100644
index 000000000..d6f1ad231
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/users/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: users-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/users.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/users/index.md b/versioned_docs/version-7.x/dev/server/services/users/index.md
new file mode 100644
index 000000000..6366a6c91
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/users/index.md
@@ -0,0 +1,11 @@
+---
+title: Users
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Users" service_machine_name="users" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/web/_category_.json b/versioned_docs/version-7.x/dev/server/services/web/_category_.json
new file mode 100644
index 000000000..d7ceec044
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/web/_category_.json
@@ -0,0 +1,5 @@
+{
+  "label": "Web",
+  "position": 40,
+  "key": "dev-server-services-web"
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/web/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/web/env-vars.mdx
new file mode 100644
index 000000000..92815fdb2
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/web/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: web-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/web_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/web/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/web/example-config.mdx
new file mode 100644
index 000000000..3d990b6f5
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/web/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: web-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/web.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/web/index.md b/versioned_docs/version-7.x/dev/server/services/web/index.md
new file mode 100644
index 000000000..fc17a62a5
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/web/index.md
@@ -0,0 +1,11 @@
+---
+title: Web
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Web" service_machine_name="web" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/web/info.mdx b/versioned_docs/version-7.x/dev/server/services/web/info.mdx
new file mode 100644
index 000000000..a77363ee9
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/web/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: web-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/web_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/webdav/_category_.json b/versioned_docs/version-7.x/dev/server/services/webdav/_category_.json
new file mode 100644
index 000000000..01a700a55
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/webdav/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Webdav",
+  "position": 41
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/webdav/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/webdav/env-vars.mdx
new file mode 100644
index 000000000..603c83c91
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/webdav/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: webdav-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/webdav_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/webdav/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/webdav/example-config.mdx
new file mode 100644
index 000000000..318009d56
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/webdav/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: webdav-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/webdav.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/webdav/index.md b/versioned_docs/version-7.x/dev/server/services/webdav/index.md
new file mode 100644
index 000000000..dbac327b0
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/webdav/index.md
@@ -0,0 +1,11 @@
+---
+title: WebDAV
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="WebDAV" service_machine_name="webdav" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/webdav/info.mdx b/versioned_docs/version-7.x/dev/server/services/webdav/info.mdx
new file mode 100644
index 000000000..55a046fae
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/webdav/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: webdav-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/webdav_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/server/services/webfinger/_category_.json b/versioned_docs/version-7.x/dev/server/services/webfinger/_category_.json
new file mode 100644
index 000000000..b0e2debbb
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/webfinger/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Webfinger",
+  "position": 42
+}
diff --git a/versioned_docs/version-7.x/dev/server/services/webfinger/env-vars.mdx b/versioned_docs/version-7.x/dev/server/services/webfinger/env-vars.mdx
new file mode 100644
index 000000000..7ea2aa56f
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/webfinger/env-vars.mdx
@@ -0,0 +1,12 @@
+---
+sidebar_position: 2
+id: webfinger-envvars
+slug: environment-variables
+title: Environment Variables
+---
+
+import Envvars from '../../../../_static/env-vars/webfinger_configvars.md';
+
+<small>
+  <Envvars />
+</small>
diff --git a/versioned_docs/version-7.x/dev/server/services/webfinger/example-config.mdx b/versioned_docs/version-7.x/dev/server/services/webfinger/example-config.mdx
new file mode 100644
index 000000000..93aff1b00
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/webfinger/example-config.mdx
@@ -0,0 +1,11 @@
+---
+sidebar_position: 3
+id: webfinger-example
+slug: yaml-config
+title: Yaml Config
+---
+
+import yamlContent from '!!raw-loader!../../../../_static/env-vars/webfinger.yaml';
+import CodeBlock from '@theme/CodeBlock';
+
+<CodeBlock language="yaml">{yamlContent}</CodeBlock>
diff --git a/versioned_docs/version-7.x/dev/server/services/webfinger/index.md b/versioned_docs/version-7.x/dev/server/services/webfinger/index.md
new file mode 100644
index 000000000..5bdf388dd
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/webfinger/index.md
@@ -0,0 +1,11 @@
+---
+title: Webfinger
+sidebar_position: 1
+---
+
+import DocCardList from '@theme/DocCardList';
+import ServiceOverview from '@site/static/templates/service-overview.md';
+
+<ServiceOverview service_name="Webfinger" service_machine_name="webfinger" />
+
+<DocCardList />
diff --git a/versioned_docs/version-7.x/dev/server/services/webfinger/info.mdx b/versioned_docs/version-7.x/dev/server/services/webfinger/info.mdx
new file mode 100644
index 000000000..7b79b388d
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/server/services/webfinger/info.mdx
@@ -0,0 +1,10 @@
+---
+sidebar_position: 1
+id: webfinger-info
+slug: information
+title: General Information
+---
+
+import Info from '../../../../_static/env-vars/webfinger_readme.md';
+
+<Info />
diff --git a/versioned_docs/version-7.x/dev/web/_category_.json b/versioned_docs/version-7.x/dev/web/_category_.json
new file mode 100644
index 000000000..7d5a81e22
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/_category_.json
@@ -0,0 +1,5 @@
+{
+  "label": "Web",
+  "position": 3,
+  "key": "dev-web"
+}
diff --git a/versioned_docs/version-7.x/dev/web/design-system.md b/versioned_docs/version-7.x/dev/web/design-system.md
new file mode 100644
index 000000000..fcc0445fd
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/design-system.md
@@ -0,0 +1,6 @@
+---
+title: Design System
+sidebar_position: 6
+---
+
+The design system documentation can be found <a href="/design-system" target="_blank">here</a>.
diff --git a/versioned_docs/version-7.x/dev/web/development/_category_.json b/versioned_docs/version-7.x/dev/web/development/_category_.json
new file mode 100644
index 000000000..5bed99fc3
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/development/_category_.json
@@ -0,0 +1,9 @@
+{
+  "label": "Development",
+  "position": 2,
+  "link": {
+    "type": "generated-index",
+    "description": "\uD83D\uDC69\u200D\uD83D\uDCBB Development",
+    "slug": "dev/web/development/"
+  }
+}
diff --git a/versioned_docs/version-7.x/dev/web/development/conventions.md b/versioned_docs/version-7.x/dev/web/development/conventions.md
new file mode 100644
index 000000000..c6fb493ab
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/development/conventions.md
@@ -0,0 +1,57 @@
+---
+title: 'Conventions'
+sidebar_position: 3
+id: conventions
+---
+
+This is a collection of tips and conventions to follow when working on the [OpenCloud Web frontend](https://github.com/opencloud-eu/web).
+Since it is a living document, please open a PR if you find something missing.
+
+## Contributing to OpenCloud Web
+
+Everyone is invited to contribute. Simply fork the [codebase](https://github.com/opencloud-eu/web/),
+check the [issues](https://github.com/opencloud-eu/web/issues?q=is%3Aopen%20is%3Aissue%20label%3AType%3AGood-First-Issue)
+for a suitable one and open a pull request!
+
+### Formal checks
+
+To make sure your pull request can be efficiently reviewed and won't need a lot of changes down the road, please run all formal checks (linter, formatter, type checks and unit tests) via `pnpm check:all` locally. Our [CI](https://ci.opencloud.eu/repos/6) will run on
+pull requests and report back any problems after that. For a further introduction on how we handle testing, please head to
+the [testing docs](../testing/running-tests).
+
+## Code Conventions
+
+### Early Returns
+
+We're trying to stick with early returns in our code to make it more performant and simpler to reason about it.
+
+### Translations
+
+Use `$gettext` (or a variation of it) inside HTML tags (instead of a `<translate tag="h1">` or similar) in order to translate strings.
+
+### TypeScript
+
+We're using TypeScript which allows us to catch bugs at transpile time. Clean types make sure our IDEs can support us in reasoning about our ever-growing, complex codebase.
+
+### Composition API and script setup
+
+We prefer using Vue's Composition API in combination with [script setup](https://vuejs.org/api/sfc-script-setup) over the traditional options API. This integrates nicely with TypeScript and allows us to use composables and reactive APIs more effectively.
+
+That being said, due to the fact that we are still in the process of migrating our codebase, you might find some files using the options API or even composition API without script setup. We are working on this and will eventually migrate all files.
+
+### Composables
+
+We make heavy use of composables to encapsulate reusable logic. This allows us to share code between components and keep our components clean and focused on their specific tasks.
+
+### Split large components
+
+If a component is getting too big, consider splitting it into smaller components. This will make it easier to read and maintain. A good rule of thumb is to keep components under 300 lines of code.
+
+### Services
+
+We try to avoid services when possible and rather use composables instead. If writing a service is necessary, it should be instantiated once via the `web-runtime` package and then made available via a `useYourService` composable.
+
+### Dependencies
+
+To keep the bundle size small and reduce the risk of introducing security problems for our users, we try to limit
+the amount of dependencies in our code base and keep them as up-to-date as possible.
diff --git a/versioned_docs/version-7.x/dev/web/development/repo-structure.md b/versioned_docs/version-7.x/dev/web/development/repo-structure.md
new file mode 100644
index 000000000..f25797b44
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/development/repo-structure.md
@@ -0,0 +1,124 @@
+---
+title: 'Repo structure and (published) packages'
+sidebar_position: 2
+id: repo-structure
+---
+
+## Repository Structure
+
+From a developer's perspective, the most important parts of the [OpenCloud Web repo](https://github.com/opencloud-eu/web) are the following files and folders:
+
+### dev Folder and docker-compose.yml File
+
+The `/dev` folder contains all the configuration files that are needed in the `docker-compose.yml` file. This docker compose stack
+contains all the backend and testing related infrastructure that is needed for an out-of-the-box usable localhost development setup,
+as described in the [tooling section](./tooling).
+
+### packages Folder
+
+We're using the [OpenCloud Web repo](https://github.com/opencloud-eu/web) as a mono repo. It contains a variety of packages. Some of them get
+published to [npmjs.com](https://npmjs.com), others define the core packages, apps and extensions that are the foundation of
+the `OpenCloud Web` release artifact.
+
+Having these packages side by side within the `/packages` folder of the repo is possible because of a `pnpm` feature called `Workspaces`. You can learn more about that by visiting the [pnpm docs](https://pnpm.io/workspaces).
+
+### tests Folder
+
+We're using [Playwright](https://playwright.dev) for UI testing. The UI tests are located in `/tests/e2e`. You can read more about testing in our [testing docs](../testing/running-tests).
+
+### package.json File
+
+This is probably no surprise: the root level `package.json` file defines the project information, build scripts, dependencies and some more details.
+Each package in `/packages` can and most likely will contain another `package.json` which does the same for the respective package.
+
+### vite.config.ts
+
+We're working with [Vite](https://vitejs.dev) as a local development server and build tool. `vite.config.ts` is the main configuration file for that.
+You can read more about the usage in our [tooling section](./tooling).
+
+## Packages
+
+Each package in the `/packages` folder can - not exclusively, but most commonly - consist of
+
+- source code (`/src`),
+- unit tests (`/tests`),
+- translations (`/l10n`) and
+- a `package.json` file for package specific details and dependencies.
+
+### Code Style and Build Config
+
+Some of our packages in `/packages` are pure helper packages which ensure a common code style and build configuration for all our
+internal (mono repo) and external packages. We encourage you to make use of the very same packages. This helps the community
+understand code more easily, even when coming from different developers or vendors in the OpenCloud Web ecosystem.
+
+Namely those packages are
+
+- `/packages/eslint-config`
+- `/packages/extension-sdk`
+- `/packages/prettier-config`
+- `/packages/tsconfig`
+
+### OpenCloud Design System
+
+The OpenCloud Design System (`/packages/design-system`) is a collection of components, design tokens and styles which ensure a
+unique and consistent look and feel and branding throughout the OpenCloud Web ecosystem. We hope that you use it, too, so that your
+very own apps and extensions will blend in with all the others. Documentation and code examples can be found in
+the [design system documentation](https://docs.opencloud.eu/design-system/).
+
+The OpenCloud Design System is a standalone project that gets published on npmjs.com as [@opencloud-eu/design-system](https://www.npmjs.com/package/@opencloud-eu/design-system). Since it's bundled with OpenCloud Web, you should not bundle it with your app or extension. However, you can add it as a dev dependency for better IDE support.
+
+### web-client
+
+The client package (`/packages/web-client`) serves as an abstraction layer for the various OpenCloud APIs, like
+[LibreGraph](https://docs.opencloud.eu/apis/http/graph/), [WebDAV](https://docs.opencloud.eu/server/next/developer_manual/webdav_api/) and
+[OCS](https://docs.opencloud.eu/server/next/developer_manual/core/apis/ocs-capabilities.html). The package provides TypeScript
+interfaces for various entities (like files, folders, shares and spaces) and makes sure that raw API responses are properly
+transformed so that you can deal with more useful objects. The web-client package gets published
+on npmjs.com as [@opencloud-eu/web-client](https://www.npmjs.com/package/@opencloud-eu/web-client).
+
+Dedicated documentation for the `web-client` package is not available, yet, since our extension system is still work in progress. However, the package's [README.md](https://github.com/opencloud-eu/web/blob/main/packages/web-client/README.md) gives you a few examples on how to use it.
+
+### web-pkg
+
+The web-pkg package (`/packages/web-pkg`) is a collection of opinionated components, composables, types and other helpers that aim
+at making your app and extension developer experience as easy and seamless as possible. The web-pkg package gets published on
+npmjs.com as [@opencloud-eu/web-pkg](https://www.npmjs.com/package/@opencloud-eu/web-pkg).
+
+Dedicated documentation for the `web-pkg` package is not available, yet, since our extension system is still work in progress.
+
+### web-runtime
+
+At the very heart of OpenCloud Web, the `web-runtime` is responsible for dependency injection, app bootstrapping, configuration,
+authentication, data preloading and much more.
+It is very likely that you will never get in touch with it as most of the developer-facing features are exposed via `web-pkg`. If you
+have more questions about this package, please write an issue in our [issue tracker](https://github.com/opencloud-eu/web/issues).
+
+### Standalone Core Apps
+
+The repo also includes some standalone apps which are bundled with the default OpenCloud Web release artifact.
+
+- `web-app-activities`
+- `web-app-admin-settings`
+- `web-app-app-store`
+- `web-app-files`
+- `web-app-ocm`
+- `web-app-search`
+- `web-app-webfinger`
+
+### Viewer and Editor Apps
+
+Apps which fall into the categories `viewer` or `editor` can be opened from the context of a file or folder. This mostly happens from
+within the `files` app. We currently bundle the following apps with the default OpenCloud Web release artifact:
+
+- `web-app-epub-reader` a simple reader for `.epub` files
+- `web-app-external` an iframe integration of all the apps coming from the app provider
+  (e.g. Collabora Online, OnlyOffice and others)
+- `web-app-pdf-viewer` a viewer for `.pdf` files, which relies on native PDF rendering support from the browser
+- `web-app-preview` a viewer for various media files (audio / video / image formats)
+- `web-app-text-editor` a simple editor for `.txt`, `.md` and other plain text files
+
+If you're interested in writing your own viewer or editor app for certain file types, please have a look at the [extension system docs](../extension-system/).
+
+### Testing
+
+Basic setup and helpers for unit testing lives in `web-test-helpers`. This package gets published on npmjs.com as [@opencloud-eu/web-test-helpers](https://www.npmjs.com/package/@opencloud-eu/web-test-helpers) to ensure its functionality can be used anywhere inside the OpenCloud Web ecosystem.
diff --git a/versioned_docs/version-7.x/dev/web/development/tooling.md b/versioned_docs/version-7.x/dev/web/development/tooling.md
new file mode 100644
index 000000000..7ecda429d
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/development/tooling.md
@@ -0,0 +1,59 @@
+---
+title: 'Tooling'
+sidebar_position: 1
+id: tooling
+---
+
+## Packaging
+
+Web is using [pnpm](https://pnpm.io/) as package manager and [vite](https://vitejs.dev/) as build tool. The latter is built on top of [rollup](https://rollupjs.org/) and brings some additional features such as instant hot-reloading.
+
+## Development Setup
+
+### Prerequisites
+
+Please make sure you have the following tools installed on your system:
+
+- docker
+- docker-compose (if not already included in your docker installation)
+- node
+- pnpm (we recommend the installation via `corepack` which is included in newer node versions)
+
+:::note
+If you’re not using Docker Desktop, you might have to modify your `/etc/hosts` and add `127.0.0.1 host.docker.internal` to make `host.docker.internal` links work.
+:::
+
+:::note
+This setup currently doesn't work on Windows out of the box.
+
+<details>
+  <summary>Workaround</summary>
+  
+  One of our contributors has opened a PR to a dependency that prevents us from successfully bundling the frontend.
+  Feel free to check out [their changes](https://github.com/egoist/rollup-plugin-postcss/pull/384) and build them locally if you absolutely want to work on Windows.
+</details>
+:::
+
+### Installing Dependencies
+
+After cloning the source code, install the dependencies via `pnpm install`.
+
+### Starting the Server
+
+You can start the OpenCloud server by running `docker compose up opencloud -d`. If you want to run the full stack, you can run `docker compose up -d` instead. This will also start the wopi service and an instance of Collabora.
+
+### Building and Accessing Web
+
+After starting the docker containers, you can build Web by running `pnpm build:w`. This command compiles the project and includes support for hot-reloading, allowing you to see changes as you make them. However, note that the rebuild process may take some time.
+
+For a faster development experience, consider enabling instant hot-reloading. Details on how to set this up are provided below.
+
+Now you can access Web via [https://host.docker.internal:9200](https://host.docker.internal:9200).
+
+### Using Instant Hot-Reload via Vite
+
+To work with instant hot-reloading, you can also build Web by running `pnpm vite`. The port to access Web is slightly different then: [https://host.docker.internal:9201](https://host.docker.internal:9201). Also note that the initial page load may take a bit longer than usual. This is normal and to be expected.
+
+:::note
+Make sure that you ran `pnpm build` once before starting the server with `pnpm vite`. Also, you need to accept the self-signed certificate in your browser for [https://host.docker.internal:9200](https://host.docker.internal:9200) _and_ [https://host.docker.internal:9201](https://host.docker.internal:9201).
+:::
diff --git a/versioned_docs/version-7.x/dev/web/embed-mode.md b/versioned_docs/version-7.x/dev/web/embed-mode.md
new file mode 100644
index 000000000..ad0b32832
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/embed-mode.md
@@ -0,0 +1,149 @@
+---
+title: 'Embed Mode'
+sidebar_position: 4
+---
+
+The OpenCloud Web can be consumed by another application in a stripped down version called "Embed mode". This mode is supposed to be used in the context of selecting or sharing resources.
+
+## Getting started
+
+To integrate OpenCloud Web into your application, add an iframe element pointing to your OpenCloud Web deployed instance with additional query parameter `embed=true`.
+
+```html
+<iframe src="<web-url>?embed=true"></iframe>
+```
+
+## Communication
+
+To establish seamless cross-origin communication between the embedded instance and the parent application, our approach involves emitting events using the `postMessage` method. These events can be conveniently captured by utilizing the standard `window.addEventListener('message', listener)` pattern.
+
+### Target origin
+
+By default, the `postMessage` method does not specify the `targetOrigin` parameter. However, it is recommended best practice to explicitly pass in the URI of the iframe origin (not the parent application). To enhance security, you can specify this value by modifying the config option `options.embed.messagesOrigin`.
+
+### Events
+
+To maintain uniformity and ease of handling, each event encapsulates the same structure within its payload: `{ name: string, data: any }`.
+
+| Name                            | Data                                        | Description                                                                                                       |
+| ------------------------------- | ------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
+| **opencloud-embed:select**      | `Resource[]`                                | Gets emitted when user selects resources or location via the select action                                        |
+| **opencloud-embed:share-links** | `Array<{ url: string, password?: string }>` | Gets emitted when user shares resources via the "Share links" action. Includes passwords when applicable.         |
+| **opencloud-embed:share**       | `string[]`                                  | **(Deprecated)** Gets emitted when user shares resources. Use `opencloud-embed:share-links` for password support. |
+| **opencloud-embed:cancel**      | `null`                                      | Gets emitted when user attempts to close the embedded instance via "Cancel" action                                |
+
+### Example
+
+```html
+<iframe src="https://my-opencloud-web-instance?embed=true"></iframe>
+
+<script>
+  function selectEventHandler(event) {
+    if (event.data?.name !== 'opencloud-embed:select') {
+      return;
+    }
+
+    const resources = event.data.data;
+
+    doSomethingWithSelectedResources(resources);
+  }
+
+  function shareLinksEventHandler(event) {
+    if (event.data?.name !== 'opencloud-embed:share-links') {
+      return;
+    }
+
+    const links = event.data.data; // Array<{ url: string, password?: string }>
+
+    links.forEach((link) => {
+      console.log('Shared link:', link.url, link.password);
+    });
+
+    doSomethingWithSharedLinks(links);
+  }
+
+  window.addEventListener('message', selectEventHandler);
+  window.addEventListener('message', shareLinksEventHandler);
+</script>
+```
+
+## Location picker
+
+By default, the Embed mode allows users to select resources. In certain cases (e.g. uploading a file), this needs to be changed to allow selecting a location. This can be achieved by running the embed mode with additional parameter `embed-target=location`. With this parameter, resource selection is disabled and the selected resources array always includes the current folder as the only item.
+In special scenarios you also want the user to set a file name, this can be achieved by adding the `embed-choose-file-name=true` parameter, or if you also want to set a default file name, you can use `embed-choose-file-name-suggestion=my file.text`.
+
+### Example
+
+```html
+<iframe src="https://my-opencloud-web-instance?embed=true&embed-target=location"></iframe>
+
+<script>
+  function selectEventHandler(event) {
+    if (event.data?.name !== 'opencloud-embed:select') {
+      return;
+    }
+
+    const resources = event.data.data[0];
+
+    doSomethingWithSelectedResources(resources);
+  }
+
+  window.addEventListener('message', selectEventHandler);
+</script>
+```
+
+## File picker
+
+The File Picker mode in OpenCloud Web is designed for embedding an interface that allows users to pick a single file.
+This mode can be configured to restrict the file types that users can select. To enable the File Picker mode, you need
+to include the embed-target=file query parameter in the iframe URL. Furthermore, you can specify allowed file types
+using the embed-file-types parameter. The file types can be specified using file extensions, MIME types, or a
+combination of both. If the embed-file-types parameter is not provided, all file types will be selectable by default.
+
+### Example
+
+```html
+<iframe
+  src="https://my-opencloud-web-instance?embed=true&embed-target=file&embed-file-types=txt,image/png"
+></iframe>
+
+<script>
+  function selectEventHandler(event) {
+    if (event.data?.name !== 'opencloud-embed:file-pick') {
+      return;
+    }
+
+    const file = event.data.data;
+
+    doSomethingWithPickedFile(file);
+  }
+
+  window.addEventListener('message', selectEventHandler);
+</script>
+```
+
+## Delegate authentication
+
+If you already have a valid `access_token` that can be used to call the API from within the Embed mode and do not want to force the user to authenticate again, you can delegate the authentication. Delegating authentication will disable internal login form in OpenCloud Web and will instead use events to obtain the token and update it.
+
+### Configuration
+
+To allow authentication delegation, you need to set the config option `options.embed.delegateAuthentication` to `true`. This can be achieved via query parameter `embed-delegate-authentication=true`. Because we are using the `postMessage` method to communicate across different origins, it is best practice to verify that the event originated from a known origin and not from some malicious site. We highly recommend to allow this check in production environments. You can enable it by setting the config option `options.embed.delegateAuthenticationOrigin` via query parameter `embed-delegate-authentication-origin=my-origin`. The value of this parameter will be compared against the `MessageEvent.origin` value and if they do not match, the token will be rejected.
+
+### Events
+
+#### Opening Embed mode
+
+As already mentioned, we're using the `postMessage` method to allow communication between the Embed mode and the parent application. When the Embed mode is opened for the first time, the user gets redirected to the `/web-oidc-callback` page where a message with payload `{ name: 'opencloud-embed:request-token', data: undefined }` is sent to request the `access_token` from the parent application. The parent application should set an event listener before opening the Embed mode and once received, it should send a message with payload `{ name: 'opencloud-embed:update-token', data: { access_token: '<bearer-token>' } }`. Once the Embed mode receives this message, it will save the token in the application state and will automatically authenticate the user.
+
+:::note
+When passing the token in the message payload, use only the token itself without `Bearer` string as that will be added automatically in the Embed mode.
+:::
+
+:::note
+To save unnecessary duplication of messages with only different names, the name in the message payload above is exactly the same for both the initial authentication and subsequent token updates after renewal.
+:::
+
+#### Updating the token
+
+When authentication is delegated, the automatic renewal of the token inside of OpenCloud Web is disabled. In order to update the token, a listener is created which awaits a message with payload `{ name: 'opencloud-embed:update-token', data: { access_token: '<bearer-token>' } }`. The token will then be replaced inside of the Embed mode automatically.
diff --git a/versioned_docs/version-7.x/dev/web/extension-system/_category_.json b/versioned_docs/version-7.x/dev/web/extension-system/_category_.json
new file mode 100644
index 000000000..3a3a12d9d
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/extension-system/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Extension System",
+  "position": 5
+}
diff --git a/versioned_docs/version-7.x/dev/web/extension-system/extension-types/_category_.json b/versioned_docs/version-7.x/dev/web/extension-system/extension-types/_category_.json
new file mode 100644
index 000000000..29c8e97d1
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/extension-system/extension-types/_category_.json
@@ -0,0 +1,4 @@
+{
+  "label": "Extension Types",
+  "position": 2
+}
diff --git a/versioned_docs/version-7.x/dev/web/extension-system/extension-types/action-extensions.md b/versioned_docs/version-7.x/dev/web/extension-system/extension-types/action-extensions.md
new file mode 100644
index 000000000..d726150fc
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/extension-system/extension-types/action-extensions.md
@@ -0,0 +1,90 @@
+---
+title: 'Action extensions'
+sidebar_position: 1
+id: action-extensions
+---
+
+## Action extension type
+
+Actions are one of the possible extension types. Registered actions get rendered in various places across the UI, depending on their scope and targets.
+
+### Configuration
+
+This is what the `ActionExtension` interface looks like:
+
+```typescript
+interface ActionExtension {
+  id: string;
+  type: 'action';
+  extensionPointIds?: string[];
+  action: Action; // Please check the Action section below
+}
+```
+
+For `id`, `type`, and `extensionPointIds`, please see [extension base section](../#extension-base-configuration) in the top level docs.
+
+#### Action
+
+The most important configuration options are:
+
+- `icon` - The icon to be displayed, can be picked from [Remix Icon](https://remixicon.com/)
+- `name` - The name of the action (not displayed in the UI)
+- `label` - The text to be displayed
+- `route` - The string/route to navigate to. The nav item will be a `<router-link>` tag.
+- `href` - The URL to navigate to. The nav item will be a `<a>`tag.
+- `handler` - The action to perform upon click. The nav item will be a `<button>` tag.
+- `isVisible` - Determines whether the action is displayed to the user
+
+Please check the [`Action` type](https://github.com/opencloud-eu/web/blob/236c185540fc6758dc7bd84985c8834fa4145530/packages/web-pkg/src/composables/actions/types.ts#L6) for a full list of configuration options.
+
+### Example
+
+The following example shows how an action extension for downloading files could look like. Note that the extension is wrapped inside a Vue composable so it can easily be reused. All helper types and composables are being provided via the [web-pkg](https://github.com/opencloud-eu/web/tree/master/packages/web-pkg) package.
+
+```typescript
+export const useDownloadFilesExtension = () => {
+  const { $gettext } = useGettext();
+
+  const extension = computed<ActionExtension>(() => ({
+    id: 'com.github.opencloud-eu.web.files.download-action',
+    extensionPointIds: ['global.files.context-actions'],
+    type: 'action',
+    action: {
+      name: 'download-files',
+      icon: 'download',
+      class: 'oc-files-actions-download-files',
+      label: () => $gettext('Download'),
+      isVisible: ({ space, resources }) => {
+        if (resources.length === 0) {
+          return false;
+        }
+
+        return true;
+      },
+      handler: ({ space, resources }) => {
+        console.log('Triggering download...');
+      }
+    }
+  }));
+
+  return { extension };
+};
+```
+
+The extension could then be registered in any app like so:
+
+```typescript
+export default defineWebApplication({
+  setup() {
+    const { extension } = useFileActionDownloadFiles();
+
+    return {
+      appInfo: {
+        name: $gettext('Download app'),
+        id: 'download-app'
+      },
+      extensions: computed(() => [unref(extension)])
+    };
+  }
+});
+```
diff --git a/versioned_docs/version-7.x/dev/web/extension-system/extension-types/app-menu-item-extensions.md b/versioned_docs/version-7.x/dev/web/extension-system/extension-types/app-menu-item-extensions.md
new file mode 100644
index 000000000..fa2c6f2fd
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/extension-system/extension-types/app-menu-item-extensions.md
@@ -0,0 +1,73 @@
+---
+title: 'Application menu item extensions'
+sidebar_position: 2
+id: app-menu-item-extensions
+---
+
+## Extension Type AppMenuItem
+
+This extension type allows apps to register links to internal or external pages within the application switcher menu on the top left.
+
+### Configuration
+
+The Interface for an `AppMenuItemExtension` looks like so:
+
+```typescript
+interface AppMenuItemExtension {
+  id: string;
+  type: 'appMenuItem';
+  extensionPointIds?: string[];
+  label: () => string;
+  color?: string;
+  handler?: () => void;
+  icon?: string;
+  path?: string;
+  priority?: number;
+  url?: string;
+}
+```
+
+For `id`, `type`, and `extensionPointIds`, please see [extension base section](../#extension-base-configuration) in the top level docs.
+
+A `handler` will result in a `<button>` element. This is necessary when an action should be performed when clicking the menu item (e.g. opening a file editor).
+
+A `path` will result in an `<a>` element that links to an internal page via the vue router. That means the given path needs to exist within the application.
+
+A `url` will result in an `<a>` element that links to an external page. External pages always open in a new tab or window.
+
+At least one of these properties has to be provided when registering an extension. If you define more than one, the priority order is `handler` > `path` > `url`.
+
+`priority` specifies the order of the menu items. 50 is a good number to start with, then go up/down based on where the item should be placed. Defaults to the highest possible number, so the item will most likely end up at the bottom of the list if you don't specify a `priority`. Leave it empty if unsure what to pick.
+
+## Example
+
+The following example shows how an app creates an extension that registers an app menu item, linking to an internal page. All helper types and composables are being provided via the [web-pkg](https://github.com/opencloud-eu/web/tree/main/packages/web-pkg) package.
+
+```typescript
+export default defineWebApplication({
+  setup() {
+    const { $gettext } = useGettext();
+    const appId = 'my-cool-app';
+
+    const menuItems = computed<AppMenuItemExtension[]>(() => [
+      {
+        id: 'com.github.opencloud-eu.web.my-cool-app.menu-item',
+        type: 'appMenuItem',
+        label: () => $gettext('My cool app'),
+        path: urlJoin(appId),
+        icon: 'star',
+        color: '#0D856F',
+        priority: 60
+      }
+    ]);
+
+    return {
+      appInfo: {
+        name: $gettext('My cool app'),
+        id: appId
+      },
+      extensions: menuItems
+    };
+  }
+});
+```
diff --git a/versioned_docs/version-7.x/dev/web/extension-system/extension-types/custom-component-extensions.md b/versioned_docs/version-7.x/dev/web/extension-system/extension-types/custom-component-extensions.md
new file mode 100644
index 000000000..d55be79a7
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/extension-system/extension-types/custom-component-extensions.md
@@ -0,0 +1,47 @@
+---
+title: 'Custom component extensions'
+sidebar_position: 3
+id: custom-component-extensions
+---
+
+## Extension Type CustomComponent
+
+CustomComponent extensions need to define one or multiple `extensionPointId`s as render target. A `CustomComponentTarget` component for this very
+extension point needs to be mounted in the current view.
+
+### Configuration
+
+To define a custom component extension, you implement the `CustomComponentExtension` interface.
+Here's what it looks like:
+
+```typescript
+interface CustomComponentExtension {
+  id: string;
+  type: 'customComponent';
+  extensionPointIds?: string[];
+  content: Slot | Component;
+}
+```
+
+For `id`, `type`, and `extensionPointIds`, please see [extension base section](../#extension-base-configuration) in the top level docs.
+
+The `content` property specifies a render function or a Component for the target extension point.
+
+### Example
+
+A simple example for a custom component extension could be a `NyanCat` progress bar component, being
+targeted at the `global-progress-bar` extension point as render target.
+
+```typescript
+const extension = {
+  id: 'com.github.opencloud-eu.web.app.progress-bars.nyan-cat',
+  type: 'customComponent',
+  extensionPointIds: ['app.runtime.global-progress-bar'],
+  content: (slots) => [h(NyanCat, slots)],
+  userPreference: {
+    optionLabel: $gettext('Nyan Cat progress bar')
+  }
+};
+```
+
+The `content` property in this example can also be defined as `content: NyanCat`.
diff --git a/versioned_docs/version-7.x/dev/web/extension-system/extension-types/floating-action-button-extensions.md b/versioned_docs/version-7.x/dev/web/extension-system/extension-types/floating-action-button-extensions.md
new file mode 100644
index 000000000..8b6772897
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/extension-system/extension-types/floating-action-button-extensions.md
@@ -0,0 +1,70 @@
+---
+title: 'Floating Action Button extensions'
+sidebar_position: 8
+id: floating-action-button-extensions
+---
+
+## Extension Type FloatingActionButton
+
+This extension type allows apps to register actions either displayed within the left sidebar (for desktop resolutions) or as a floating action button (for mobile resolutions). The extension point for this extension type is `app.${appId}.floating-action-button`.
+
+:::warning
+You need to take care of the visibility of your floating action button extension via the `isActive` property, otherwise you might end up overwriting other extensions' action buttons. In most cases, it makes sense to only display the button when your app is currently active.
+:::
+
+### Configuration
+
+To define a floating action button extension, you implement the `FloatingActionButtonExtension` interface. Here's what it looks like:
+
+```typescript
+interface FloatingActionButtonExtension {
+  id: string;
+  type: 'floatingActionButton';
+  extensionPointIds?: string[];
+  label: () => string;
+  isActive: () => boolean;
+  isDisabled?: () => boolean;
+  color?: string;
+  icon?: string;
+  mode: () => 'drop' | 'handler';
+  handler?: () => Promise<void> | void;
+  dropComponent?: Component;
+}
+```
+
+For `id`, `type`, and `extensionPointIds`, please see [extension base section](../#extension-base-configuration) in the top level docs.
+
+The `mode` property determines whether the floating action button triggers a handler function or renders a `dropComponent` when clicked. If mode returns `handler`, the click handler function is executed, if it returns `drop`, the specified `dropComponent` is shown instead.
+
+`isDisabled` controls the disabled state of the button whereas `isActive` determines if the button is showing at all.
+
+`icon` is an icon name string that can be picked from [Remix Icon](https://remixicon.com/).
+
+### Example
+
+The following example shows how the files app is registering a floating action button extension for creating new files or folders. Note that the example assumes you're in a Vue injection context (e.g. within the `setup` method of your app's `defineWebApplication` call).
+
+```typescript
+import { useGettext } from 'vue3-gettext';
+import CreateOrUploadMenu from './components/CreateOrUploadMenu.vue';
+import { useIsFilesAppActive, useResourcesStore } from '@opencloud-eu/web-pkg';
+
+const { $gettext } = useGettext();
+const isFilesAppActive = useIsFilesAppActive();
+const resourcesStore = useResourcesStore();
+
+const extension = {
+  id: 'com.github.opencloud-eu.web.files.floating-action-button',
+  extensionPointIds: ['app.files.floating-action-button'],
+  type: 'floatingActionButton',
+  icon: 'add',
+  label: () => $gettext('New'),
+  isActive: () => {
+    return unref(isFilesAppActive);
+  },
+  isDisabled: () => {
+    return !resourcesStore.currentFolder?.canUpload();
+  },
+  dropComponent: CreateOrUploadMenu
+};
+```
diff --git a/versioned_docs/version-7.x/dev/web/extension-system/extension-types/folder-view-extensions.md b/versioned_docs/version-7.x/dev/web/extension-system/extension-types/folder-view-extensions.md
new file mode 100644
index 000000000..f18d81654
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/extension-system/extension-types/folder-view-extensions.md
@@ -0,0 +1,80 @@
+---
+title: 'Folder view extensions'
+sidebar_position: 4
+id: folder-view-extensions
+---
+
+## Folder view extension type
+
+The folder view is one of the possible extension types. Registered folder view can be used to render multiple resources (folders, files, spaces) in the UI.
+
+### Configuration
+
+This is what the FolderViewExtension interface looks like:
+
+```typescript
+interface FolderViewExtension {
+  id: string;
+  type: 'folderView';
+  extensionPointIds?: string[];
+  folderView: FolderView; // See FolderView section below
+}
+```
+
+For `id`, `type`, and `extensionPointIds`, please see [extension base section](../#extension-base-configuration) in the top level docs.
+
+#### FolderView
+
+For the folderView object, you have the following configuration options:
+
+- `name` - The name of the action (not displayed in the UI)
+- `label` - The text to be displayed to the user when switching between different FolderView options
+- `icon` - Object, expecting an icon `name` and a corresponding `IconFillType`, see [Remix Icon](https://remixicon.com/) for available options
+- `isScrollable` - Optional boolean, determines whether the user can scroll inside the component or it statically fills the viewport
+- `component` - The Vue component to render the resources. It should expect a prop of type `Resource[]`
+- `componentAttrs` - Optional additional configuration for the component mentioned above
+
+### Example
+
+The following example shows how an extension for a custom folder view could look like. Note that the extension is wrapped inside a Vue composable so it can easily be reused. All helper types and composables are being provided via the [web-pkg](https://github.com/opencloud-eu/web/tree/main/packages/web-pkg) package.
+
+```typescript
+export const useCustomFolderViewExtension = () => {
+  const { $gettext } = useGettext();
+
+  const extension = computed<FolderViewExtension>(() => ({
+    id: 'com.github.opencloud-eu.web.files.folder-view.custom',
+    type: 'folderView',
+    extensionPointIds: ['app.files.folder-views.folder'],
+    folderView: {
+      name: 'custom-table',
+      label: $gettext('Switch to custom folder view'),
+      icon: {
+        name: 'menu-line',
+        fillType: 'none'
+      },
+      component: YourCustomFolderViewComponent
+    }
+  }));
+
+  return { extension };
+};
+```
+
+The extension could then be registered in any app like so:
+
+```typescript
+export default defineWebApplication({
+  setup() {
+    const { extension } = useCustomFolderViewExtension();
+
+    return {
+      appInfo: {
+        name: $gettext('Custom folder view app'),
+        id: 'custom-folder-view-app'
+      },
+      extensions: computed(() => [unref(extension)])
+    };
+  }
+});
+```
diff --git a/versioned_docs/version-7.x/dev/web/extension-system/extension-types/index.md b/versioned_docs/version-7.x/dev/web/extension-system/extension-types/index.md
new file mode 100644
index 000000000..a6f04677d
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/extension-system/extension-types/index.md
@@ -0,0 +1,6 @@
+---
+title: 'Extension Types'
+---
+
+This section is a guide about the different predefined extension types of OpenCloud Web. Please refer to the respective
+subpages to learn more about the individual extension types.
diff --git a/versioned_docs/version-7.x/dev/web/extension-system/extension-types/left-sidebar-menu-item-extensions.md b/versioned_docs/version-7.x/dev/web/extension-system/extension-types/left-sidebar-menu-item-extensions.md
new file mode 100644
index 000000000..7d7e171e0
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/extension-system/extension-types/left-sidebar-menu-item-extensions.md
@@ -0,0 +1,92 @@
+---
+title: 'Left sidebar menu item extensions'
+sidebar_position: 5
+id: left-sidebar-menu-item-extensions
+---
+
+## Left sidebar menu item extension type
+
+One possible extension type is left sidebar menu items. Registered left sidebar menu items get rendered in the left sidebar, as long as there is more than one available.
+
+### Configuration
+
+To define a left sidebar menu item, you implement the SidebarNavExtension interface.
+It looks like this:
+
+```typescript
+interface SidebarNavExtension {
+    id: string
+    type: 'sidebarNav'
+    extensionPointIds?: string[]
+    navItem: AppNavigationItem // Please check the AppNavigationItem section below
+    }
+}
+```
+
+For `id`, `type`, and `extensionPointIds`, please see [extension base section](../#extension-base-configuration) in the top level docs.
+
+#### AppNavigationItem
+
+The most important configuration options are:
+
+- `icon` - The icon to be displayed, can be picked from [Remix Icon](https://remixicon.com/)
+- `name` - The text to be displayed
+- `route` - The string/route to navigate to, if the nav item should be a `<router-link>` (Mutually exclusive with `handler`)
+- `handler` - The action to perform upon click, if the nav item should be a `<button>` (Mutually exclusive with `route`)
+
+Please check the [`AppNavigationItem` type](https://github.com/opencloud-eu/web/blob/f069ce44919cde5d112c68a519d433e015a4a011/packages/web-pkg/src/apps/types.ts#L14) for a full list of configuration options.
+
+### Example
+
+The following example shows an extension that adds a left sidebar nav item inside the files app, linking to a custom page. Note that the extension is wrapped inside a Vue composable so it can easily be reused. All helper types and composables are being provided via the [web-pkg](https://github.com/opencloud-eu/web/tree/main/packages/web-pkg) package.
+
+```typescript
+export const useCustomPageExtension = () => {
+  const { $gettext } = useGettext();
+
+  const extension = computed<SidebarNavExtension>(() => ({
+    id: 'com.github.opencloud-eu.web.files.left-nav.custom-page',
+    extensionPointIds: ['app.files.navItems'],
+    type: 'sidebarNav',
+    action: {
+      name: $gettext('Custom page'),
+      icon: 'world',
+      priority: 100,
+      isActive: () => true,
+      isVisible: () => true,
+      route: {
+        path: '/files/custom-page'
+      },
+      activeFor: [{ path: '/files/custom-page' }]
+    }
+  }));
+
+  return { extension };
+};
+```
+
+The extension could then be registered in any app like so:
+
+```typescript
+export default defineWebApplication({
+  setup() {
+    const { extension } = useCustomPageExtension();
+
+    return {
+      appInfo: {
+        name: $gettext('Custom page app'),
+        id: 'custom-page-app'
+      },
+      routes: {
+        path: '/files/custom-page',
+        name: 'files-custom-page',
+        component: CustomPageComponent,
+        meta: {
+          title: $gettext('Custom Page')
+        }
+      },
+      extensions: computed(() => [unref(extension)])
+    };
+  }
+});
+```
diff --git a/versioned_docs/version-7.x/dev/web/extension-system/extension-types/right-sidebar-panel-extensions.md b/versioned_docs/version-7.x/dev/web/extension-system/extension-types/right-sidebar-panel-extensions.md
new file mode 100644
index 000000000..91baa35fb
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/extension-system/extension-types/right-sidebar-panel-extensions.md
@@ -0,0 +1,130 @@
+---
+title: 'Right sidebar panel extensions'
+sidebar_position: 6
+id: right-sidebar-panel-extensions
+---
+
+## Extension Type SideBarPanel
+
+The right sidebar is supposed to show information and make context specific actions available for single or multiple selected items.
+
+It is structured in a hierarchical way:
+
+- Panels which are defined as `root` panels get rendered as immediate members of the right sidebar.
+- Panels which are defined as non-`root` panels receive a navigation item below the `root` panels so that users can navigate into the respective
+  sub panel.
+
+### Configuration
+
+To define a right sidebar panel extension, you implement the `SidebarPanelExtension` interface.
+It can be found below:
+
+```typescript
+interface SidebarPanelExtension<R extends Item, P extends Item, T extends Item> {
+  id: string;
+  type: 'sidebarPanel';
+  extensionPointIds?: string[];
+  panel: SideBarPanel<R, P, T>; // Please check the SideBarPanel section below
+}
+```
+
+For `id`, `type`, and `extensionPointIds`, please see [extension base section](../#extension-base-configuration) in the top level docs.
+
+The `panel` object configures the actual sidebar panel. It consists of different properties and functions, where all the functions get called with a
+`SideBarPanelContext` entity from the integrating extension points.
+
+#### SideBarPanelContext
+
+```typescript
+interface SideBarPanelContext<R extends Item, P extends Item, T extends Item> {
+  root?: R;
+  parent?: P;
+  items?: T[];
+}
+```
+
+- `items` - The most important member of the panel context, which denotes all selected items. That can mean all selected files in a files listing,
+  all selected users in a user listing, the individual current file in a file editor.
+- `parent` - The immediate parent of the selected items. For example, if the user selects a file in a file listing, the parent is the parent folder,
+  or if being in a root of a space, the space itself. Can be `null` for non-hierarchical contexts, e.g. a user listing.
+- `root` - The uppermost parent of the selected items. For example, if the user selects a file in a file listing, the root is always the space in which
+  the selected files reside. Can be `null` for non-hierarchical contexts, e.g. a user listing.
+
+#### SideBarPanel
+
+```typescript
+interface SideBarPanel<R extends Item, P extends Item, T extends Item> {
+  name: string;
+  icon: string;
+  iconFillType?: IconFillType;
+  title(context: SideBarPanelContext<R, P, T>): string;
+  isVisible(context: SideBarPanelContext<R, P, T>): boolean;
+  component: Component;
+  componentAttrs?(context: SideBarPanelContext<R, P, T>): any;
+  isRoot?(context: SideBarPanelContext<R, P, T>): boolean;
+}
+```
+
+- `name` - A human readable id for the panel.
+- `icon`, `iconFillType` and `title` - Properties which are used to render the panel itself or right sidebar navigation items for navigating into that panel.
+- `isVisible` - Determines if the panel is available for the given panel context.
+- `component` - Provides a component that renders the actual sidebar panel.
+- `componentAttrs` - Defines additional props for the component with the given panel context.
+- `isRoot` - Determines if the panel is a root panel for the given panel context.
+
+## Extension Point FileSideBar
+
+In the context of files (e.g. file listing, text editor for a single file, etc.) we have a dedicated component `FileSideBar` which can be
+toggled (shown/hidden) with a button in the top bar. The component queries all extensions of the type `sideBarPanel` from the extension
+registry that also fulfill the scope `resource`. By registering an custom extension of type `sideBarPanel` and scope `resource`, your extension
+will automatically become available in all environments that display the `FileSideBar` (i.e. any file viewer, file editor, file listing).
+
+## Example
+
+The following example shows how a sidebar panel for displaying exif data for a resource could look like. Note that the extension is wrapped inside a Vue composable so it can easily be reused. All helper types and composables are being provided via the [web-pkg](https://github.com/opencloud-eu/web/tree/main/packages/web-pkg) and the [web-client](https://github.com/opencloud-eu/web/tree/main/packages/web-client) packages.
+
+```typescript
+export const useExifDataPanelExtension = () => {
+  const { $gettext } = useGettext();
+
+  const extension = computed<SidebarPanelExtension<SpaceResource, Resource, Resource>>(() => ({
+    id: 'com.github.opencloud-eu.web.files.sidebar-panel.exif-data',
+    type: 'sidebarPanel',
+    extensionPointIds: ['global.files.sidebar'],
+    panel: {
+      name: 'exif-data',
+      icon: 'image',
+      title: () => $gettext('EXIF data'),
+      component: ExifDataPanelComponent,
+      isRoot: () => true,
+      isVisible: ({ items }) => {
+        if (items?.length !== 1) {
+          return false;
+        }
+
+        return true;
+      }
+    }
+  }));
+
+  return { extension };
+};
+```
+
+The extension can then be registered in any app like so:
+
+```typescript
+export default defineWebApplication({
+  setup() {
+    const { extension } = useExifDataPanelExtension();
+
+    return {
+      appInfo: {
+        name: $gettext('Exif panel app'),
+        id: 'exif-panel-app'
+      },
+      extensions: computed(() => [unref(extension)])
+    };
+  }
+});
+```
diff --git a/versioned_docs/version-7.x/dev/web/extension-system/extension-types/search-extensions.md b/versioned_docs/version-7.x/dev/web/extension-system/extension-types/search-extensions.md
new file mode 100644
index 000000000..aa59eb46b
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/extension-system/extension-types/search-extensions.md
@@ -0,0 +1,122 @@
+---
+title: 'Search extensions'
+sidebar_position: 7
+id: search-extensions
+---
+
+## Search extensions
+
+One possible extension type is search. Registered search extensions are available when using the search field in the topbar. A search extension can consist of a
+`list` and a `preview` search. The result of a `preview` search is shown below the search input field while the `list` search result is
+
+### Configuration
+
+An example of a search extension configuration can be found below:
+
+```typescript
+interface SearchExtension {
+  id: string;
+  type: 'search';
+  extensionPointIds?: string[];
+  searchProvider: {
+    id: string;
+    available: boolean;
+    displayName?: string;
+    previewSearch?: SearchPreview; // See SearchPreview section below
+    listSearch?: SearchList; // See SearchList section below
+  };
+}
+```
+
+For `id`, `type`, and `extensionPointIds`, please see [extension base section](../#extension-base-configuration) in the top level docs.
+
+The `searchProvider` object configures the actual provider. It consist of the following:
+
+- `id` - Since your extension has an `id` and can only have one searchProvider, you can reuse the same value
+- `available` - Can be used to programmatically disable/enable any searchProvider, e.g. by dynamically checking backend capabilities
+- `displayName` - Optional, used to add a small hint to indicate the connection between search providers and their corresponding results
+- `previewSearch` - See below
+- `listSearch` - See below
+
+#### ListSearch
+
+The listSearch object consists of:
+
+- `component` - Vue component that can render the values from the SearchResult below
+- `search(term: string)` - Function that executes the search, based on a given term. The term is formatted in [KQL](https://docs.opencloud.eu/services/search/#query-language). Please note that the returned values needs to be formatted to fit either `SearchResource` or `GenericSearchResultItem` type
+
+#### PreviewSearch
+
+The previewSearch object extends the listSearch with one additional attribute:
+
+- `available` - Indicates whether a preview underneath the search bar is available for this search provider
+
+## Example
+
+The following example shows how a search extension that queries a Solr search engine could look like. Note that the extension is wrapped inside a Vue composable so it can easily be reused. All helper types and composables are being provided via the [web-pkg](https://github.com/opencloud-eu/web/tree/main/packages/web-pkg) and the [web-client](https://github.com/opencloud-eu/web/tree/main/packages/web-client) packages.
+
+```typescript
+export const useSolrSearchExtension = () => {
+  const { $gettext } = useGettext();
+
+  const previewSearch: SearchPreview = {
+    component: SolarSearchComponent, // see the next example snippet
+    available: () => true,
+    search: (term) => {
+      // actual search implementation
+      console.log('Querying solr search engine...');
+    }
+  };
+
+  const searchProvider: SearchProvider = {
+    id: 'solr-search',
+    available: true,
+    displayName: 'Solr Search',
+    previewSearch
+  };
+
+  const extension = computed<SearchExtension>(() => ({
+    id: 'com.github.opencloud-eu.web.solr-search',
+    type: 'search',
+    searchProvider
+  }));
+
+  return { extension };
+};
+```
+
+The search component for the preview search container may look like this:
+
+```html
+<template>
+  <resource-list-item :resource="resource" />
+</template>
+
+<script setup lang="ts">
+  import { computed } from 'vue';
+  import { Resource } from '@opencloud-eu/web-client';
+  import { SearchResultValue, ResourceListItem } from '@opencloud-eu/web-pkg';
+
+  const { searchResult } = defineProps<{ searchResult: SearchResultValue }>();
+
+  const resource = computed<Resource>(() => searchResult.data);
+</script>
+```
+
+The extension can then be registered in any app like so:
+
+```typescript
+export default defineWebApplication({
+  setup() {
+    const { extension } = useSolrSearchExtension();
+
+    return {
+      appInfo: {
+        name: $gettext('Solr search app'),
+        id: 'solrs-search-app'
+      },
+      extensions: computed(() => [unref(extension)])
+    };
+  }
+});
+```
diff --git a/versioned_docs/version-7.x/dev/web/extension-system/index.md b/versioned_docs/version-7.x/dev/web/extension-system/index.md
new file mode 100644
index 000000000..5962d994a
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/extension-system/index.md
@@ -0,0 +1,188 @@
+---
+title: 'Extension system'
+---
+
+## Concepts and Building Blocks
+
+OpenCloud Web can be extended through various entry points with custom **apps** and **extensions**.
+
+### Distinction between Apps and Extensions
+
+An Application in the context of OpenCloud Web is an artifact which can be installed in an OpenCloud instance.
+It serves two main purposes:
+
+1. It makes the full app viewport (everything below the top bar) available to the application developer for any custom
+   application code. This includes the ability to define views with routes, navigation items for the left sidebar, and more.
+2. Through the `extensions` key in the application interface you can register extensions of any extension type. Those extensions
+   are then available in standardized extension points. Additionally, they can be queried from the extension registry for
+   your own purposes.
+
+Both parts are optional. This means that an application can be a file editor without any custom extensions, or even contain
+no custom application code at all and only host extensions to be registered in the extension registry, or a combination of both.
+
+### Examples
+
+You can find open source examples for apps and extensions in our [curated list of OpenCloud apps and extensions](https://github.com/opencloud-eu/awesome-apps).
+Feel free to contribute or just be inspired for your own apps or extensions.
+
+### Apps
+
+Apps define a `src/index.ts` file which acts as an entrypoint. Below is the most basic example of its content:
+
+```typescript
+import {
+  AppWrapperRoute,
+  ApplicationFileExtension,
+  defineWebApplication
+} from '@opencloud-eu/web-pkg'
+
+
+export default defineWebApplication({
+  setup({ applicationConfig }) {
+    // Here, you have access to the full injection context, meaning you can use all composables that we provide via web-pkg
+
+    // Needs to be unique within all installed applications in any OpenCloud web instance
+    // Should be short, unique and expressive as it is used as prefix on all routes within your application
+    const appId = 'your-extension'
+
+    // See extensions section below
+    const extensions = [
+        ...
+    ]
+
+    // See details below
+    const navItems = [
+      ...
+    ]
+
+    // See details below
+    const routes = [
+        ...
+    ]
+
+    return {
+      appInfo: {
+        name: $gettext('Your application name'),
+        id: appId,
+        icon: 'aliens', // See https://remixicon.com/ for available options
+      },
+      extensions,
+      navItems,
+      routes
+    }
+  }
+})
+```
+
+By defining an application via `defineWebApplication` you can provide the following:
+
+- `appInfo` - the application metadata, which is used to make the application available via the app switcher and the app registry.
+- `navItems` - the statically defined navigation items for the left sidebar. Only gets rendered when more than 1 navigation item exists at runtime.
+  Additional dynamic navigation items can be registered via the extension registry.
+- `routes` - the routes to the different views of your application. May be referenced within the `navItems`. Authentication requirements can be defined per item.
+- `extensions` - the extensions to be registered in the extension registry. For more details see the [Extensions](#extensions) section below.
+
+#### Creating a new app
+
+Please check out the [web-app-skeleton repository](https://github.com/opencloud-eu/web-app-skeleton) for a boilerplate application to get started with your own application. In addition to that, if you want to learn how to implement an app for viewing and editing specific file types, please consult the [relevant documentation](./viewer-editor-apps) for detailed instructions and guidance.
+
+To learn how to integrate an app into OpenCloud Web, please refer to the [Web Application admin docs](../../../admin/configuration/web-applications).
+
+### Extensions
+
+In contrast to applications, extensions usually have a rather small scope and dedicated functionality.
+
+#### Extension Registry
+
+The globally available extension registry provided by the OpenCloud Web runtime can be used to both register and query extensions. All extensions
+which are being made available via an `app` get registered in the extension registry automatically. In your custom application code you can
+then query any of the available extensions by providing an `extensionPoint` entity. Throughout the OpenCloud Web platform
+and most prominently also in the `files` app we have defined some extension points which automatically use certain extensions, see the
+`Extension Points` section below.
+
+#### Extension Types
+
+For building an extension you can choose from the types predefined by the OpenCloud Web extension system. See the full list of available extension types below.
+
+1. `ActionExtension` (type `action`) - An extension that can register `Action` items which then get shown in various places (e.g. context menus, batch actions), depending on the
+   extension points referenced in the extension respectively. Most commonly used for file and folder actions (e.g. copy, rename, delete, etc.). For details, please refer to the [action docs](./extension-types/action-extensions)
+2. `SearchExtension` (type `search`) - An extension that can register additional search providers. For details, please refer to the [search docs](./extension-types/search-extensions).
+3. `SidebarNavExtension` (type `sidebarNav`) - An extension that can register additional navigation items for the left sidebar. These can be scoped to specific apps, and programmatically enabled/disabled.
+   For details, please refer to the [sidebar nav docs](./extension-types/left-sidebar-menu-item-extensions).
+4. `SidebarPanelExtension`, (type `sidebarPanel`) - An extension that can register panels for the right sidebar. For details, please refer to the [sidebar panel docs](./extension-types/right-sidebar-panel-extensions).
+5. `FolderViewExtension` (type `folderView`) - An extension that can register additional ways of displaying the content of a folder (resources like spaces, folders or files) to the user.
+   For details, please refer to the [folder view docs](./extension-types/folder-view-extensions).
+6. `CustomComponentExtension` (type `customComponent`) - An extension that can register a custom component for a render target. For details, please refer to the
+   [custom component docs](./extension-types/custom-component-extensions)
+7. `FloatingActionButtonExtension` (type `floatingActionButton`) - An extension that can register one or multiple actions, either displayed within the left sidebar (for desktop resolutions) or as a floating action button (for mobile resolutions). For details, please refer to the
+   [floating action button docs](./extension-types/floating-action-button-extensions).
+
+You're free to introduce your own extension types within your application code and use the extension registry to query the available ones. However, if you have the impression
+that an important extension type is missing and would be beneficial for the platform, please reach out to us by opening a [GitHub issue](https://github.com/opencloud-eu/web/issues/new/choose).
+
+#### Extension Base Configuration
+
+Any extension is required to define at least an `id` and a `type` in order to fulfill the generic `Extension` interface.
+
+The `id` is supposed to be unique throughout the OpenCloud Web ecosystem. In order to keep `id`s readable for humans we didn't want to enforce uniqueness through e.g. uuids.
+Instead, we chose to use dot-formatted namespaces like e.g. `com.github.opencloud-eu.web.files.search`. We'd like to encourage you to follow the same format for your own extensions.
+
+For the `type` you can choose from the ones listed above or define a custom one.
+
+In addition, you can also pass optional `extensionPointIds` to further limit the usage of an extension. With the right click context menu and the batch actions being
+two different extension points, this could mean that a file action extension is only allowed in the context menu, but not in the batch actions.
+You can find predefined extension point ids in the extension points section below.
+
+#### Extension Points
+
+There are standardized components and places where extensions are being used automatically. The following ones are currently provided by the OpenCloud Web runtime or
+the `files` app. If you decide to develop an extension which fulfills the type and registers itself for the extensionPointId of the respective extension point,
+your extension will be used automatically.
+
+1. Left Sidebar for Navigation.
+   1. Floating Action Button (FAB). ExtensionPointId `app.${appName}.floating-action-button` (dynamically created for each app). Mounts extensions of type `floatingActionButton`.
+   2. Additional nav items. ExtensionPointId `app.${appName}.navItems` (dynamically created for each app). Mounts extensions of type `sidebarNav`.
+   3. Sidebar main area below nav items. ExtensionPointId `app.${appName}.sidebar-nav.main` (dynamically created for each app). Mounts extensions of type `customComponent`.
+   4. Sidebar bottom area above version info. ExtensionPointId `app.${appName}.sidebar-nav.bottom` (dynamically created for each app). Mounts extensions of type `customComponent`.
+2. Global top bar
+   1. Center area. ExtensionPointId `app.runtime.header.center`. Mounts extensions of type `customComponent`.
+   2. Left area. ExtensionPointId `app.runtime.header.left`. Mounts extensions of type `customComponent`.
+   3. Right area. ExtensionPointId `app.runtime.header.right`. Mounts extensions of type `customComponent`.
+   4. Progress bar for the global loading state. ExtensionPointId `app.runtime.global-progress-bar`. Mounts a single extension of type `customComponent`. If multiple exist, the user can choose via the account page.
+3. Files app
+   1. Right sidebar.
+      1. Panels. ExtensionPointId `app.files.sidebar`. Mounts extensions of type `sidebarPanel`. Used in any file(s) context (files app, file viewer apps, file editor apps).
+      2. File details table. ExtensionPointId `app.files.sidebar.file-details.table`. Mounts extensions of type `customComponent`. Properties `space` and `resource` can be retrieved via injection context.
+      3. Space details table. ExtensionPointId `app.files.sidebar.space-details.table`. Mounts extensions of type `customComponent`. Properties `space` and `resource` can be retrieved via injection context.
+      4. Shares panel people list top section. ExtensionPointId `app.files.sidebar.shares-panel.shared-with.top`. Mounts extensions of type `customComponent`. Properties `space` and `resource` can be retrieved via injection context.
+      5. Shares panel people list bottom section. ExtensionPointId `app.files.sidebar.shares-panel.shared-with.bottom`. Mounts extensions of type `customComponent`. Properties `space` and `resource` can be retrieved via injection context.
+   2. Folder views for regular folders. ExtensionPointId `app.files.folder-views.folder`. Mounts extensions of type `folderView`.
+   3. Folder views for the project spaces overview. ExtensionPointId `app.files.folder-views.project-spaces`. Mounts extensions of type `folderView`.
+   4. Folder views for the favorites page. ExtensionPointId `app.files.folder-views.favorites`. Mounts extensions of type `folderView`.
+   5. Right click context menu. ExtensionPointId `global.files.context-actions`. Mounts extensions of type `action`.
+   6. Batch actions in the app bar above file lists. ExtensionPointId `global.files.batch-actions`. Mounts extensions of type `action`.
+   7. Default actions (left click) on a file. ExtensionPointId `global.files.default-actions`. Mounts extensions of type `action`.
+   8. Upload menu. ExtensionPointId `app.files.upload-menu`. Mounts extensions of type `action`.
+   9. Quick actions. ExtensionPointId `app.files.quick-actions`. Mounts extensions of type `action`.
+   10. Quick actions for the trash overview. ExtensionPointId `app.files.trash-quick-actions`. Mounts extensions of type `action`.
+4. Global search providers. ExtensionPointId `app.search.providers`. Utilizes extensions of type `search` as search engines for the search input in the global top bar.
+5. User preference panels. ExtensionPointId `app.runtime.preferences.panels`. Mounts extensions of type `customComponent`.
+
+#### User Preferences for Extensions
+
+To allow users to configure extensions, extension points can define user preferences. User preferences are defined as an object on the extension point configuration.
+Whenever an extension point declares to accept user preferences, it will get listed with a dropdown on the Preferences page (reachable via top right user menu).
+The user can then select one out of all the extensions which have been registered for this extension point.
+
+#### Creating a new extension
+
+Please check out the [web-app-skeleton repository](https://github.com/opencloud-eu/web-app-skeleton) for a boilerplate application that also includes an extension. In addition to that, the [extension types docs](./extension-types/) provide instructions and examples on how to implement the different extension types.
+
+### Helpful packages
+
+We currently offer the following packages that can be integrated into your app, providing useful utilities and types.
+
+- `extension-sdk` - This package provides a default vite config that can be used when developing applications and extensions for the OpenCloud Web ecosystem. For details, please refer to the package's [README.md](https://github.com/opencloud-eu/web/blob/main/packages/extension-sdk/README.md).
+- `web-client` - This package serves as an abstraction layer between the server APIs and an app or extension. It converts raw API data into objects with helpful types and utilities. For details, please refer to the package's [README.md](https://github.com/opencloud-eu/web/blob/main/packages/web-client/README.md).
+- `web-pkg` - This package provides utilities, most importantly a variety of components and composables, that can be useful when developing apps and extensions. For details, please refer to the package's [README.md](https://github.com/opencloud-eu/web/blob/main/packages/web-pkg/README.md).
+- `web-test-helpers` - This package provides utilities for writing unit tests. For details, please refer to the package's [README.md](https://github.com/opencloud-eu/web/blob/main/packages/web-test-helpers/README.md).
diff --git a/versioned_docs/version-7.x/dev/web/extension-system/viewer-editor-apps.md b/versioned_docs/version-7.x/dev/web/extension-system/viewer-editor-apps.md
new file mode 100644
index 000000000..b70535907
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/extension-system/viewer-editor-apps.md
@@ -0,0 +1,116 @@
+---
+title: 'Viewer and editor apps'
+sidebar_position: 1
+---
+
+## Viewer and editor apps
+
+OpenCloud Web allows developers to implement apps for viewing and editing specific file types. For instance, the built-in preview app serves as the default application for opening media files like images, videos, or audio.
+
+This section will guide you through the process of implementing such an app within OpenCloud Web.
+
+### Basic app structure
+
+An app is essentially a distinct package that must be specified as an external application in the Web configuration.
+
+The structure of an app is quite simple and straightforward. Consider, for example, the [pdf-viewer app](https://github.com/opencloud-eu/web/tree/main/packages/web-app-pdf-viewer). It consists of a `package.json` file, a `src` directory containing all the source code, and a `l10n` directory for translations. Optionally, you may also include a `tests` directory if your application requires testing.
+
+To learn more about apps in general, please refer to the [Web app docs](../extension-system/).
+
+### App setup
+
+Inside the `src` folder you will need an `index.ts` file that sets up the app so it can be registered by the Web runtime. It follows the basic structure as described in [the apps section](../extension-system/), so it may look like this:
+
+```typescript
+import { AppWrapperRoute, defineWebApplication, AppMenuItemExtension } from '@opencloud-eu/web-pkg';
+import translations from '../l10n/translations.json';
+import { useGettext } from 'vue3-gettext';
+import { computed } from 'vue';
+
+// This is the base component of your app.
+import App from './App.vue';
+
+export default defineWebApplication({
+  setup() {
+    // The ID of your app.
+    const appId = 'advanced-pdf-viewer';
+
+    const { $gettext } = useGettext();
+
+    // This creates a route under which your app can be opened.
+    // Later, this route will be bound to one or more file extensions.
+    const routes = [
+      {
+        name: 'advanced-pdf-viewer',
+        path: '/:driveAliasAndItem(.*)?',
+        component: AppWrapperRoute(App, {
+          applicationId: appId
+        }),
+        meta: {
+          authContext: 'hybrid',
+          title: $gettext('Advanced PDF Viewer'),
+          patchCleanPath: true
+        }
+      }
+    ];
+
+    // if you want your app to be present in the app menu on the top left.
+    const menuItems = computed<AppMenuItemExtension[]>(() => [
+      {
+        label: () => $gettext('Advanced PDF Viewer'),
+        type: 'appMenuItem',
+        handler: () => {
+          // do stuff...
+        }
+      }
+    ]);
+
+    return {
+      appInfo: {
+        name: 'Advanced PDF Viewer',
+        id: appId,
+        defaultExtension: 'pdf',
+        extensions: [
+          // This makes sure all files with the "pdf" extension will be routed to your app when being opened.
+          // See the `ApplicationFileExtension` interface down below for a list of all possible properties.
+          {
+            extension: 'pdf',
+            routeName: 'advanced-pdf-viewer',
+
+            // Add this if you want your app to be present in the "New" file menu.
+            newFileMenu: {
+              menuTitle() {
+                return $gettext('PDF document');
+              }
+            }
+          }
+        ]
+      },
+      routes,
+      translations,
+      extensions: menuItems
+    };
+  }
+});
+```
+
+Here is the interface defining the `extensions` property of the `appInfo` object.
+
+```typescript
+interface ApplicationFileExtension {
+  app?: string;
+  extension?: string;
+  createFileHandler?: (arg: {
+    fileName: string;
+    space: SpaceResource;
+    currentFolder: Resource;
+  }) => Promise<Resource>;
+  hasPriority?: boolean;
+  label?: string;
+  name?: string;
+  icon?: string;
+  mimeType?: string;
+  newFileMenu?: { menuTitle: () => string };
+  routeName?: string;
+}
+```
diff --git a/versioned_docs/version-7.x/dev/web/getting-started.md b/versioned_docs/version-7.x/dev/web/getting-started.md
new file mode 100644
index 000000000..2524a93b5
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/getting-started.md
@@ -0,0 +1,108 @@
+---
+title: 'Getting Started'
+sidebar_position: 1
+---
+
+## Source Code
+
+The source code is hosted at [https://github.com/opencloud-eu/web](https://github.com/opencloud-eu/web).
+
+## Installation
+
+To install and setup the Web client on your local machine, please refer to the [development setup docs](./development/tooling#development-setup).
+
+## Configuration
+
+Web can be configured using a configuration file in `json` format. Sample configuration files are available in the [config folder](https://github.com/opencloud-eu/web/tree/main/config) of the OpenCloud Web Git repository. Below is a detailed overview of all available configuration options.
+
+### `server`
+
+Specifies the server URL, e.g. `https://host.docker.internal:9200`.
+
+### `theme`
+
+Specifies the URL for the theme to be loaded, e.g. `https://host.docker.internal:9200/themes/opencloud/theme.json`.
+
+### `options`
+
+General options that control the behavior of the Web client. Expects an object with the following possible options:
+
+- `options.accountEditLink` This accepts an object with the following optional fields to have a link on the account page:
+  - `options.accountEditLink.href` Set a different target URL for the edit link. Make sure to prepend it with `http(s)://`.
+- `options.sharingRecipientsPerPage` Sets the amount of users shown as recipients in the dropdown when sharing resources. Default amount is 200.
+- `options.runningOnEos` Set this option to `true` if running on an [EOS storage backend](https://eos-web.web.cern.ch/eos-web/) to enable its specific features. Defaults to `false`.
+- `options.cernFeatures` Enabling this will activate CERN-specific features. Defaults to `false`.
+- `options.editor.autosaveEnabled` Specifies if the autosave for the editor apps is enabled.
+- `options.editor.autosaveInterval` Specifies the time interval for the autosave of editor apps in seconds.
+- `options.editor.openAsPreview` Specifies if non-personal files i.e. files in shares, spaces or public links are being opened in read only mode so the user needs to manually switch to edit mode. Can be set to `true`, `false` or an array of web app/editor names.
+- `options.contextHelpersReadMore` Specifies whether the "Read more" link should be displayed or not.
+- `options.tokenStorageLocal` Specifies whether the access token will be stored in the local storage when set to `true` or in the session storage when set to `false`. If stored in the local storage, login state will be persisted across multiple browser tabs, means no additional logins are required. Defaults to `true`.
+- `options.loginUrl` Specifies the target URL to the login page. This is helpful when an external IdP is used. This option is disabled by default. Example URL like: '[https://www.myidp.com/login](https://www.myidp.com/login)'.
+- `options.logoutUrl` Adds a link to the user's profile page to point him to an external page, where he can manage his session and devices. This is helpful when an external IdP is used. This option is disabled by default.
+- `options.userListRequiresFilter` Defines whether one or more filters must be set in order to list users in the Web admin settings. Set this option to 'true' if running in an environment with a lot of users and listing all users could slow down performance. Defaults to `false`.
+- `options.concurrentRequests` This accepts an object with the following optional fields to customize the maximum number of concurrent requests in code paths where we limit concurrent requests
+  - `resourceBatchActions` Concurrent number of file/folder/space batch actions like e.g. accepting shares. Defaults to 4.
+  - `sse` Concurrent number of SSE event handlers. Defaults to 4.
+  - `shares` Accepts an object regarding the following sharing related options:
+    - `create` Concurrent number of share invites. Defaults to 4.
+    - `list` Concurrent number of individually loaded shares. Defaults to 2.
+
+### `apps`
+
+Controls the Web apps to be loaded. This is not for adding external apps, but for specifying which of the internal apps that are shipped with Web should be loaded. Expects a list of strings, e.g.:
+
+```json
+[
+  "files",
+  "text-editor",
+  "pdf-viewer",
+  "search",
+  "external",
+  "admin-settings",
+  "epub-reader",
+  "app-store",
+  "preview"
+]
+```
+
+### `openIdConnect`
+
+The Web client forwards all configuration options under `openIdConnect` to the [oidc-client-ts library](https://authts.github.io/oidc-client-ts/). Setting the following 3 options however won't have any effect, as they get discovered automatically via the `/.well-known/webfinger` endpoint:
+
+- `client_id`
+- `scope`
+- `authority`
+
+See the [oidc-client-ts documentation](https://authts.github.io/oidc-client-ts/interfaces/OidcClientSettings.html) for information on the available configuration options for the library.
+
+### `customTranslations`
+
+Specify custom translations to overwrite existing ones. Expects an array of objects that specify a `url` attribute, like `[{url: "https://host.docker.internal:9200/customTranslations.json"}]`.
+
+### `styles`
+
+Additional CSS files to further customize the user experience and adapt it to your specific needs. Expects an array of objects that specify a `href` attribute, pointing to the path/URL of your stylesheet, like `[{ "href": "css/custom.css" }]`.
+
+### `scripts`
+
+Additional JavaScript files to further customize the user experience and adapt it to your specific needs. Expects an array of objects that specify a `src` attribute, pointing to the path/URL of your script, and an optional `async` attribute (defaults to false), like `[{ "src": "js/custom.js", "async": true }]`.
+
+:::note
+Check out the [extension system docs](./extension-system/) for a more convenient way to add functionality to the Web client.
+:::
+
+### `sentry`
+
+Web supports [Sentry](https://sentry.io/welcome/) to provide monitoring and error tracking.
+To enable sending data to a Sentry instance, you can use the following configuration keys:
+
+- `sentry.dsn` Should contain the DSN for your sentry project.
+- `sentry.environment`: Lets you specify the environment to use in Sentry. Defaults to `production`.
+
+Any other key under `sentry` will be forwarded to the Sentry initialization. You can find out more
+settings in the [Sentry docs](https://docs.sentry.io/platforms/javascript/configuration/).
+
+:::note
+If you are using an old version of Sentry (9 and before), you might want to add the setting `sentry.autoSessionTracking: false` to avoid errors related to breaking changes introduced in the
+integration libraries.
+:::
diff --git a/versioned_docs/version-7.x/dev/web/index.md b/versioned_docs/version-7.x/dev/web/index.md
new file mode 100644
index 000000000..ee78d28c9
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/index.md
@@ -0,0 +1,7 @@
+---
+title: 'Web UI'
+---
+
+This is the next generation OpenCloud frontend.
+If you're new here, head over to the the [getting started guide](./getting-started)
+for a quick introduction.
diff --git a/versioned_docs/version-7.x/dev/web/testing/_category_.json b/versioned_docs/version-7.x/dev/web/testing/_category_.json
new file mode 100644
index 000000000..296ff9a78
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/testing/_category_.json
@@ -0,0 +1,9 @@
+{
+  "label": "Testing",
+  "position": 3,
+  "link": {
+    "type": "generated-index",
+    "description": "✅ Testing",
+    "slug": "dev/web/testing/"
+  }
+}
diff --git a/versioned_docs/version-7.x/dev/web/testing/e2e-testing-standards.md b/versioned_docs/version-7.x/dev/web/testing/e2e-testing-standards.md
new file mode 100644
index 000000000..49cd8b2e5
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/testing/e2e-testing-standards.md
@@ -0,0 +1,308 @@
+---
+title: 'End-to-End (E2E) Test Standards'
+sidebar_position: 2
+id: e2e-testing-standards
+---
+
+## Introduction
+
+In OpenCloud, we use Playwright for webUI test automation. We benefit from lower barriers to entry, readability, and usability when test standards are consistent across repositories. For example:
+
+- **Reusability:** Enhances reusability by making it easier to reuse functions, locators, shared steps, and other test code. Finding the necessary components and functionalities will be simple for someone working on a test resulting in reduced duplication and the requirement for rework after the initiation of a code review.
+
+- **Facilitates reviews:** Code can be examined more quickly. Since you can quickly determine what the test code is doing, it eases the mental strain of code review.
+
+- **Faster onboarding:** By following naming conventions, new contributors are onboarded more rapidly and feel comfortable enough to contribute to the codebase.
+
+Here are the test standards and guidelines we adhere to when creating Playwright tests at OpenCloud.
+
+## Folder Structure
+
+- `tests/:`
+  - `e2e/`: Main folder containing all (end-to-end) E2E test-related files.
+    - `cucumber/`: Main folder containing all Cucumber(BDD) test-related files.
+      - `features/`: Contains Gherkin feature files.
+        - `<test-suite-folder>/`: Collection house for "**related"** feature files.
+          - `<aFeatureFile>.feature`: A feature file.
+
+      - `steps/`: Holds the step definition files for mapping Gherkin steps to code.
+        - `<stepDefinition>.ts`: Step definitions for each feature.
+
+      - `hooks/`: Cucumber hooks for setting up and tearing down test environments.
+        - `hooks.ts`: Contains `Before`, `After`, and other lifecycle hooks.
+
+    - `support/`: Playwright (Test implementation)
+      - `api/`: Contains API-related test files and configurations.
+        - `<api-folder>/`: Specific API tests for a particular service.
+
+      - `objects/`: Contains the Page Object classes.
+        - `<specific-page-object-folder>/`: Collection house for related page objects for each webpage or component.
+          - `<individualPageObject>.ts`: Page Object for each webpage or component.
+
+      - `utils/`: Utility functions and common helpers.
+        - `helpers.ts`: Common utility functions (e.g., date formatting, data generation).
+
+      - `test-data/`: Static test data files or folders for upload.
+        - `filesForUpload/`: Static test data files for upload.
+
+    - `config/`: Configuration files for Playwright and other tools.
+      - `playwright.config.ts`: Playwright configuration.
+
+    - `reports/`: Generated test reports (e.g., HTML, JSON).
+      - `screenshots/`: Captured screenshots during test execution.
+
+      - `videos/`: Recorded videos of test runs.
+
+## Test Structure - Arrange, Act, Assert
+
+We can follow the AAA (Arrange, Act, Assert) pattern when structuring the tests. In most cases, the Arrange step can be included in a Before block(hook).
+Consider including comments defining each section to ease readability.
+
+```typescript
+// arrange, set up the initial conditions for the test
+// create a property
+await createProperty();
+
+// act, perform the action that you want to test
+// raise a charge
+// this could involve calling methods or functions defined in your page objects
+await raiseCharge();
+
+// assert, verify that the action had the expected outcome
+// confirm charge has been raised
+expect(charge).toBe('raised');
+```
+
+## Page Object Model (POM)
+
+Every page should possess one POM file to enhance maintainability and scalability of our tests. It should include all the selectors and functions which are needed to interact with the UI page or component(s).
+
+All interactions should be done using the page objects, no selectors in your tests.
+
+All assertions should be in your test, no assertion in the POM
+
+DO 👍
+
+```typescript
+// POM file './pageOobjects/foo/'
+// add all locators and functions related to the page.
+// allowing all tests to reuse
+
+import { expect, Locator, Page } from '@playwright/test';
+
+export class FooPage {
+  readonly errorMessage: Locator;
+
+  constructor(page: Page) {
+    this.page = page;
+    this.errorMessage = page.locator('.error-message');
+  }
+}
+
+// test file './steps/foo.ts'
+import { FooPage } from './pageObjects/foo';
+
+let fooPage: FooPage;
+
+Then('error message should be visible', async function ({ page }) {
+  const fooPage = new FooPage({ page });
+  await expect(fooPage.errorMessage).toBeVisible();
+});
+```
+
+DO NOT ⚔️
+
+```typescript
+// test file './steps/foo.ts'
+// include locators directly in test
+import { Locator, Page } from '@playwright/test';
+
+Then('error message should be visible', async function ({ page }) {
+  await expect(page.locator('.error-message')).toBeVisible();
+});
+```
+
+## Waiting
+
+Playwright uses auto-waiting, so we avoid artificial waiting, the exception being if it is really necessary.
+
+DO NOT ⚔️
+
+```typescript
+await page.waitForTimeout(5000);
+```
+
+This can cause flaky tests as we can rarely be certain the amount of wait time is enough. It can also unnecessarily increase the test run time. Instead, we can try:
+
+DO 👍
+
+```typescript
+await page.goto(fooBarURL, {
+  waitUntil: 'domcontentloaded'
+});
+```
+
+DO 👍
+
+```typescript
+const element = page.locator('some-locator-path');
+element.waitFor({ visible: true });
+```
+
+DO 👍
+
+```typescript
+await fooPage.buttonFoo.click();
+await expect(fooPage.titlePage).toBeVisible();
+```
+
+## Selectors
+
+Avoid selectors tied to implementation and page structure.
+
+Instead, we can prioritize the below, based on [testing-library guiding principles](https://testing-library.com/docs/queries/about/#priority)
+
+- `getByRole` (this aids accessibility, reflects how users and assistive technology perceive the page)
+
+- `getByText`
+
+- `getByTestId` (add them when needed)
+
+DO NOT ⚔️
+
+```javascript
+page.locator('.opt-u > div > .summary > div:nth-child(4) > div');
+```
+
+DO 👍
+
+```javascript
+page.locator('#foo-button');
+page.getByText('OK');
+```
+
+## Naming Conventions
+
+### Files and folders
+
+- **Files**: Declare in **_camelCase_**
+- **Folders**: Declare in **_kebab-case_**
+
+### Variables
+
+Declare in **_camelCase_**.
+
+### Booleans
+
+Start with ‘is’, ‘has’, ‘are’, ‘have’. This helps spot that this is a boolean while skimming the code. Still declared in **_camelCase_**.
+
+```typescript
+let isTurnedOn = false;
+```
+
+### Page Objects / Classes
+
+Declare in **_PascalCase_**.
+
+Use descriptive naming, which can help the reader quickly identify what page or page component this is covering. Use as much context as needed from your product to make the name meaningful.
+
+DO NOT ⚔️
+
+```typescript
+export class newModal
+```
+
+DO 👍
+
+```typescript
+export class AddWorksOrderModal
+```
+
+### Locators
+
+Use descriptive naming, which can help the reader quickly identify what element the locator is targeting.
+
+As an example, you can use a naming structure that contains **_“action / name of element” + “type of element”_**.
+
+**_Defining type of element_** - These are your basic HTML element types, they’ll be defined and named in the design system, or as a team you can align on a consistent naming of the elements. Example: checkbox, tickbox, button, tooltip
+
+**_Defining action / name -_** Think about what action this element will perform when interacted with. Or any existing name/text of the element
+
+DO 👍
+
+```typescript
+// This element is a submit button for the user registration form
+const submitButton = await page.locator('<locator-path>');
+```
+
+DO 👍
+
+```typescript
+// This element is a button for uploading a profile picture
+const uploadProfilePictureButton = await page.locator('<locator-path>');
+```
+
+### Function names
+
+Always start function names with a **_“verb”_**, followed by the **_“component context”_** that the function is interacting with i.e. what entity it is having an effect on.
+
+DO 👍
+
+```typescript
+getWorksOrder();
+printTransactions();
+deleteProperty();
+```
+
+## Gherkin Best Practices: Do's and Don'ts for Effective Features & Scenarios
+
+### Writing Features
+
+DO 👍
+
+- **Be Descriptive:** Use clear and descriptive language that accurately reflects the functionality.
+- **Keep It Concise:** Avoid overly long titles or descriptions. Aim for brevity while maintaining clarity.
+- **Use Active Voice:** Write in an active voice to make it clear who is performing the action.
+- **Contextual Information:** If applicable, provide context about the user role or the scenario to clarify who benefits from the feature.
+
+DO NOT ⚔️
+
+- **Avoid Vague Titles:** Titles like "Test Feature" or "Feature 1" do not provide meaningful information.
+- **Neglect User Perspective:** Failing to mention the user role can make it unclear who the feature is intended for.
+
+Example of a well-written feature:
+
+```gherkin
+Feature: Password Management for Registered Users
+  As a registered user
+  I want to set a new password
+  So that I can secure my account
+```
+
+### Writing Scenarios
+
+- **Use Clear and Descriptive Scenario Titles:** Ensure that each scenario title clearly conveys the action being tested and the expected outcome.
+
+```gherkin
+Scenario: User successfully registers with valid details
+```
+
+- **Use Clear Given/When/Then Steps:** Clearly define the context, action, and expected outcome(success or error messages if any).
+
+```gherkin
+Given the user is on the registration page
+When the user enters valid details
+Then the user should see a confirmation message "Registration successful! Welcome to our platform."
+```
+
+- **Use "tries to" for Negation:** This syntax is effective for scenarios where an action is expected to fail.
+
+```gherkin
+Scenario: User tries to log in with incorrect credentials
+Given the user is on the registration page
+When the user tries to log in with username "Alice" and password "wrongPassword"
+Then the user should see an error message
+  """
+  Incorrect username or password.
+  """
+```
diff --git a/versioned_docs/version-7.x/dev/web/testing/running-tests.md b/versioned_docs/version-7.x/dev/web/testing/running-tests.md
new file mode 100644
index 000000000..ce557c9fc
--- /dev/null
+++ b/versioned_docs/version-7.x/dev/web/testing/running-tests.md
@@ -0,0 +1,146 @@
+---
+title: 'Running tests'
+sidebar_position: 1
+id: running-tests
+---
+
+## Introduction
+
+In order to allow us to make changes quickly, often and with a high level of confidence, we heavily rely on tests within the `web` repository.
+
+This section assumes you have the Web development stack up and running. Please check out the [development setup docs](../development/tooling#development-setup) if you haven't.
+
+### Unit Tests
+
+We have a steadily growing coverage of unit tests. You can run them locally via
+
+```bash
+pnpm test:unit
+```
+
+You can also specify which tests to run by giving a path param, like so: `pnpm test:unit packages/<app-name>/tests/unit/path/to/test.spec.ts`.
+
+#### Unit Test File Structure
+
+Our unit tests spec files follow a simple structure:
+
+- fixtures and mocks at the top
+- helper functions at the bottom
+- tests in between
+
+We usually organize tests with nested `describe` blocks. If you would like to get feedback from the core team about
+the structure, scope and goals of your unit tests before actually writing some, we invite you to make a pull request
+with only `describe` blocks and nested `it.todo("put your test description here")` lines.
+
+### E2E Tests (Playwright)
+
+Our end-to-end test suite is built upon the [Playwright Framework](https://github.com/microsoft/playwright),
+which makes it easy to write tests, debug them and have them run cross-browser with minimal overhead.
+
+#### Bundling Web
+
+Make sure the Web frontend has been bundled with the following command since the dev server won't work:
+
+```bash
+pnpm build:w
+```
+
+#### Run E2E Tests
+
+The following command will run all available e2e tests:
+
+```bash
+pnpm test:e2e:cucumber 'tests/e2e/cucumber/**/*.feature'
+```
+
+#### Options
+
+To run a particular test, simply add the feature file and line number to the test command, e.g. `pnpm test:e2e:cucumber tests/e2e/cucumber/features/smoke/admin-settings/users.feature:84`
+
+Various options are available via ENV variables, e.g.
+
+- `OC_BASE_URL` # use your OpenCloud URL. Default value: host.docker.internal:9200
+- `BASIC_AUTH=true` use basic authorization for api requests.
+- `RETRY=n` to retry failures `n` times
+- `SLOW_MO=n` to slow the execution time by `n` milliseconds
+- `TIMEOUT=n` to set tests to timeout after `n` milliseconds
+- `HEADLESS=bool` to open the browser while the tests run (defaults to true => headless mode)
+- `BROWSER=name` to run tests against a specific browser. Defaults to chromium, available are chromium, firefox, webkit, chromium
+- `ADMIN_PASSWORD` to set administrator password. By default, the `admin` password is used in the test
+- `PARALLEL` for parallel test execution
+
+For debugging reasons, you may want to record a video or traces of your test run.
+Again, you can use the following ENV variables in your command:
+
+- `REPORT_DIR=another/path` to set a directory for your recorded files (defaults to "reports")
+- `REPORT_VIDEO=true` to record a video of the test run
+- `REPORT_HAR=true` to save request information from the test run
+- `REPORT_TRACING=true` to record traces from the test run
+
+To then open e.g. the tracing from the `REPORT_DIR`, run
+
+```bash
+npx playwright show-trace path/to/file.zip
+```
+
+#### Lint E2E Test Code
+
+Run the following command to find out the lint issues early in the test codes:
+
+```bash
+pnpm lint
+```
+
+And to fix the lint problems run the following command:
+
+```bash
+pnpm lint --fix
+```
+
+If the lint problems are not fixed by `--fix` option, we have to manually fix the code.
+
+### Analyze the Test Report
+
+The cucumber library is used as the test runner for e2e tests. The report generator script lives inside the `tests/e2e/cucumber/report` folder. If you want to create a report after the tests are done, run the command:
+
+```bash
+node tests/e2e/cucumber/report --report-input=tests/e2e/cucumber/report/report.json
+```
+
+By default, the report gets generated to reports/e2e/cucumber/releaseReport/cucumber_report.html.
+The location can be changed by adding the `--report-location` flag.
+
+To see all available options run
+
+```bash
+node tests/e2e/cucumber/report --help
+```
+
+### E2E Tests on OpenCloud With Keycloak
+
+We can run some of the e2e tests on OpenCloud setup with Keycloak as an external idp. To run tests against locally, please follow the steps below:
+
+#### Run OpenCloud With Keycloak
+
+There's a documentation to serve [OpenCloud with Keycloak](../../../admin/configuration/authentication-and-user-management/keycloak.md). Please follow each step to run **OpenCloud with Keycloak**.
+
+#### Options
+
+Following environment variables come in use while running e2e tests on OpenCloud with Keycloak:
+
+- `KEYCLOAK=true` runs the tests with Keycloak. Default value: false
+- `KEYCLOAK_HOST=your_keycloak_host` sets Keycloak url. Default value: keycloak.opencloud.test
+- `KEYCLOAK_ADMIN_USER=admin` keycloak admin username
+- `KEYCLOAK_ADMIN_PASSWORD=password` keycloak admin password
+- `KEYCLOAK_REALM=your_realm` keycloak realm name. Default value: openCloud
+
+#### Run E2E Tests
+
+```bash
+KEYCLOAK=true \
+KEYCLOAK_HOST=keycloak.opencloud.test \
+KEYCLOAK_ADMIN_USER=kcadmin \
+KEYCLOAK_ADMIN_PASSWORD=admin \
+OC_BASE_URL=cloud.opencloud.test \
+pnpm run test:e2e:cucumber tests/e2e/cucumber/features/keycloak
+```
diff --git a/versioned_docs/version-7.x/user/admin/_category_.json b/versioned_docs/version-7.x/user/admin/_category_.json
new file mode 100644
index 000000000..fa26efddc
--- /dev/null
+++ b/versioned_docs/version-7.x/user/admin/_category_.json
@@ -0,0 +1,8 @@
+{
+  "label": "Administration of OpenCloud",
+  "position": 9,
+  "link": {
+    "type": "doc",
+    "id": "admin-overview"
+  }
+}
diff --git a/versioned_docs/version-7.x/user/admin/app-tokens.md b/versioned_docs/version-7.x/user/admin/app-tokens.md
new file mode 100644
index 000000000..01e706f17
--- /dev/null
+++ b/versioned_docs/version-7.x/user/admin/app-tokens.md
@@ -0,0 +1,71 @@
+---
+sidebar_position: 2
+id: app-tokens
+title: App Tokens
+description: App Tokens in OpenCloud
+draft: false
+---
+
+# App Tokens
+
+App Tokens allow you to connect external apps and services (such as WebDAV clients) without using your main password.
+
+This improves security in several ways:
+
+- You never need to expose your login password to third-party applications.
+- App tokens can be revoked. If you think one has been compromised, just delete it.
+- App tokens have a configurable expiry date. This reduces the risk of misuse.
+
+In addition to improved security, App Tokens also maximize compatibility with third-party applications. Many applications do not support modern login flows like OpenID Connect, but only accept standard logins with a username and password instead. Your username together with any of your App Tokens works as the login credentials.
+
+:::important
+App Tokens allow third-party applications to access all your data. Make sure that you create
+one App Token per application and use a reasonable expiration period. If you do not want to
+expose access to all your data, consider using a public link instead.
+:::
+
+## Create an App Token
+
+- Go to the App Tokens section in your OpenCloud account settings.
+- Click on “+ New” to create a new token.
+
+  <img src={require("./img/app-tokens/create.png").default} alt="Create App Token" width="1920"/>
+
+- Enter a name for the token (e.g., "WebDAV Client").
+- Select an expiration date for added security.
+- Click Confirm.
+  <img src={require("./img/app-tokens/enter-name.png").default} alt="Enter the name and expiration date" width="1920"/>
+
+## Copy the App Token
+
+- Once the token is created, it will be shown only once.
+- Copy it immediately and store it in a secure place.
+
+  <img src={require("./img/app-tokens/copy-token.png").default} alt="Copy Token" width="1920"/>
+
+:::note
+If you lose the token, you need to delete it and create a new one.
+:::
+
+## Use the App Token
+
+You can now use the token in place of your password when connecting:
+
+- WebDAV
+- External apps
+- Third-party services
+
+:::info
+The username is usually the same as the one you use for your regular login.  
+However, if the identity provider is operating in autoprovisioning mode, only the UUID can be used.  
+You can find this UUID in the Preferences overview page.
+:::
+
+## Delete the App Token
+
+If a token is no longer needed:
+
+- Go back to the App Tokens section.
+- Click the trash icon next to the token to remove it.
+
+This ensures unused tokens cannot be misused.
diff --git a/versioned_docs/version-7.x/user/admin/img/app-tokens/copy-token.png b/versioned_docs/version-7.x/user/admin/img/app-tokens/copy-token.png
new file mode 100644
index 000000000..f485045fd
Binary files /dev/null and b/versioned_docs/version-7.x/user/admin/img/app-tokens/copy-token.png differ
diff --git a/versioned_docs/version-7.x/user/admin/img/app-tokens/create.png b/versioned_docs/version-7.x/user/admin/img/app-tokens/create.png
new file mode 100644
index 000000000..0100ac803
Binary files /dev/null and b/versioned_docs/version-7.x/user/admin/img/app-tokens/create.png differ
diff --git a/versioned_docs/version-7.x/user/admin/img/app-tokens/enter-name.png b/versioned_docs/version-7.x/user/admin/img/app-tokens/enter-name.png
new file mode 100644
index 000000000..0b70c8dfb
Binary files /dev/null and b/versioned_docs/version-7.x/user/admin/img/app-tokens/enter-name.png differ
diff --git a/versioned_docs/version-7.x/user/admin/img/settings/admin_general.png b/versioned_docs/version-7.x/user/admin/img/settings/admin_general.png
new file mode 100644
index 000000000..cca8a5567
Binary files /dev/null and b/versioned_docs/version-7.x/user/admin/img/settings/admin_general.png differ
diff --git a/versioned_docs/version-7.x/user/admin/img/settings/admin_groups.png b/versioned_docs/version-7.x/user/admin/img/settings/admin_groups.png
new file mode 100644
index 000000000..1f34893ff
Binary files /dev/null and b/versioned_docs/version-7.x/user/admin/img/settings/admin_groups.png differ
diff --git a/versioned_docs/version-7.x/user/admin/img/settings/admin_settings.png b/versioned_docs/version-7.x/user/admin/img/settings/admin_settings.png
new file mode 100644
index 000000000..948dffbbb
Binary files /dev/null and b/versioned_docs/version-7.x/user/admin/img/settings/admin_settings.png differ
diff --git a/versioned_docs/version-7.x/user/admin/img/settings/admin_spaces.png b/versioned_docs/version-7.x/user/admin/img/settings/admin_spaces.png
new file mode 100644
index 000000000..3c49e4eac
Binary files /dev/null and b/versioned_docs/version-7.x/user/admin/img/settings/admin_spaces.png differ
diff --git a/versioned_docs/version-7.x/user/admin/img/settings/admin_users.png b/versioned_docs/version-7.x/user/admin/img/settings/admin_users.png
new file mode 100644
index 000000000..27e3ef4d9
Binary files /dev/null and b/versioned_docs/version-7.x/user/admin/img/settings/admin_users.png differ
diff --git a/versioned_docs/version-7.x/user/admin/img/webdav/preferences.png b/versioned_docs/version-7.x/user/admin/img/webdav/preferences.png
new file mode 100644
index 000000000..6d829d55f
Binary files /dev/null and b/versioned_docs/version-7.x/user/admin/img/webdav/preferences.png differ
diff --git a/versioned_docs/version-7.x/user/admin/img/webdav/webdav-url.png b/versioned_docs/version-7.x/user/admin/img/webdav/webdav-url.png
new file mode 100644
index 000000000..bcf70941b
Binary files /dev/null and b/versioned_docs/version-7.x/user/admin/img/webdav/webdav-url.png differ
diff --git a/versioned_docs/version-7.x/user/admin/index.md b/versioned_docs/version-7.x/user/admin/index.md
new file mode 100644
index 000000000..37abeb0ae
--- /dev/null
+++ b/versioned_docs/version-7.x/user/admin/index.md
@@ -0,0 +1,20 @@
+---
+sidebar_position: 0
+id: admin-overview
+title: Administration of OpenCloud
+---
+
+# Administration of OpenCloud
+
+This section explains the administration features available in OpenCloud. Depending on your permissions, you can manage account settings, administer users, groups, and spaces, create app tokens, and connect external tools such as WebDAV clients.
+
+## In this section
+
+- [Settings](./settings.md)  
+  View the administration area and manage users, groups, and spaces, depending on your permissions.
+
+- [App Tokens](./app-tokens.md)  
+  Create and manage secure tokens for third-party applications and WebDAV clients.
+
+- [WebDAV](./web-dav.md)  
+  Connect OpenCloud files and spaces to your operating system or file manager using WebDAV.
diff --git a/versioned_docs/version-7.x/user/admin/settings.md b/versioned_docs/version-7.x/user/admin/settings.md
new file mode 100644
index 000000000..d1e0174df
--- /dev/null
+++ b/versioned_docs/version-7.x/user/admin/settings.md
@@ -0,0 +1,62 @@
+---
+sidebar_position: 1
+id: settings
+title: Settings
+description: Settings
+draft: false
+---
+
+# Admin area overview
+
+The admin area of OpenCloud provides the main tools for managing your organization. The most important areas are shown below.
+
+<img src={require("./img/settings/admin_settings.png").default} alt="Admin settings" width="1920"/>
+
+## General
+
+- Version overview:  
+  In the General section, you can view your current OpenCloud version and check whether a newer version is available.  
+  <img src={require("./img/settings/admin_general.png").default} alt="Admin general" width="1920"/>
+
+:::note
+If a security-critical upgrade is available, administrators may also see a warning in the lower-left corner of the web interface.
+An administrator may disable the version check. If this option is turned off, information about newer versions will not be displayed.
+:::
+
+## Users
+
+- User overview:  
+  Here you can see all users in your OpenCloud instance.
+- User management:  
+  Depending on your user management settings, you can:
+  - create or delete users
+  - edit users, for example change rights or settings
+  - change user quotas
+  - add or remove users from groups
+  - allow or block logins for individual users
+    <img src={require("./img/settings/admin_users.png").default} alt="Admin users" width="1920"/>
+
+:::note
+If OpenCloud is connected to an external IdP, you can still see the users here, but user management must be done in the IdP.
+:::
+
+## Groups
+
+- Group overview:  
+  Here you can see the existing groups in your OpenCloud instance.
+- Group management:  
+  You can create, edit, or delete local groups and add or remove members.
+- Imported groups:  
+  External groups that were imported through an external user management system cannot be edited here. These groups are marked with a lock symbol to show that they are locked.
+  <img src={require("./img/settings/admin_groups.png").default} alt="Admin groups" width="1920"/>
+
+## Spaces
+
+- Space overview:  
+  Here you can see all existing Spaces in your OpenCloud instance.
+- Space management:  
+  As an administrator, you can:
+  - edit Spaces, including rename, subtitle and quota
+  - deactivate or activate Spaces
+  - delete Spaces
+    <img src={require("./img/settings/admin_spaces.png").default} alt="Admin spaces" width="1920"/>
diff --git a/versioned_docs/version-7.x/user/admin/web-dav.md b/versioned_docs/version-7.x/user/admin/web-dav.md
new file mode 100644
index 000000000..608197aaf
--- /dev/null
+++ b/versioned_docs/version-7.x/user/admin/web-dav.md
@@ -0,0 +1,76 @@
+---
+sidebar_position: 3
+id: web-dav
+title: WebDAV
+description: Connect to a Space via WebDAV
+draft: false
+---
+
+# Connect to a Space via WebDAV
+
+With WebDAV, you can connect OpenCloud Spaces and folders as network drives on your device and manage your files directly from your file manager without using the browser.
+
+## Prerequisites
+
+- A valid OpenCloud account with WebDAV information enabled in the account settings
+- Access to a resource in OpenCloud, either a Space, a folder, or the root of your account
+- A WebDAV client, for example built-in OS support or [Mountain Duck](https://mountainduck.io/)
+- If your WebDAV client requires it, an App Token  
+  → [How to create an App Token](./app-tokens)
+
+## Step-by-Step Guide
+
+### Enable WebDAV info in the UI
+
+To display WebDAV information for a Space:
+
+- Open Account Settings.
+- Enable "Show WebDAV info in details view".
+
+  <img src={require("./img/webdav/preferences.png").default} alt="Enable WebDAV info" width="1920"/>
+
+### Get the WebDAV URL
+
+Open the info panel of the Space, folder, or account root you want to access in the OpenCloud web interface.
+
+You will see a section labeled WebDAV. Copy the full WebDAV URL. It looks like this:
+
+`https://cloud.example.com/remote.php/dav/spaces/12345678-abcd-efgh-ijkl-987654321000/`
+
+<img src={require("./img/webdav/webdav-url.png").default} alt="WebDAV URL" width="1920"/>
+
+### Connect via WebDAV
+
+Now connect your device using the WebDAV URL:
+
+- Username: your OpenCloud username
+- Password: your OpenCloud password or an App Token, depending on your setup
+
+You can use various clients depending on your operating system:
+
+## Windows
+
+- Open File Explorer.
+- Click on "This PC" and choose "Map network drive".
+- Enter the WebDAV URL.
+- Authenticate with your username and password or App Token.
+
+## macOS
+
+- In Finder, choose "Go" > "Connect to Server...".
+- Enter the WebDAV URL.
+- Log in with your credentials or App Token.
+
+## Linux
+
+- Use your file manager’s "Connect to Server" option.
+- Format the URL as:
+  `davs://cloud.example.com/remote.php/dav/spaces/<SPACE-ID>/`
+
+:::note
+Once connected, your Space behaves like a normal folder.
+
+- If your client supports OIDC, you may not need an App Token.
+- Use `https://` to ensure secure access.
+
+  :::
diff --git a/versioned_docs/version-7.x/user/android-app/_category_.json b/versioned_docs/version-7.x/user/android-app/_category_.json
new file mode 100644
index 000000000..37b070912
--- /dev/null
+++ b/versioned_docs/version-7.x/user/android-app/_category_.json
@@ -0,0 +1,8 @@
+{
+  "label": "OpenCloud Android App",
+  "position": 8,
+  "link": {
+    "type": "doc",
+    "id": "android-app-overview"
+  }
+}
diff --git a/versioned_docs/version-7.x/user/android-app/files-and-folders/_category_.json b/versioned_docs/version-7.x/user/android-app/files-and-folders/_category_.json
new file mode 100644
index 000000000..2fa5e6de3
--- /dev/null
+++ b/versioned_docs/version-7.x/user/android-app/files-and-folders/_category_.json
@@ -0,0 +1,10 @@
+{
+  "label": "Files and Folders",
+  "position": 2,
+  "key": "android-files-folders",
+  "link": {
+    "type": "generated-index",
+    "description": "Tutorials for managing your files and folders in the OpenCloud Android App.",
+    "slug": "user/android-app/files-and-folders/"
+  }
+}
diff --git a/versioned_docs/version-7.x/user/android-app/files-and-folders/create-rename-move.md b/versioned_docs/version-7.x/user/android-app/files-and-folders/create-rename-move.md
new file mode 100644
index 000000000..3585dbf21
--- /dev/null
+++ b/versioned_docs/version-7.x/user/android-app/files-and-folders/create-rename-move.md
@@ -0,0 +1,85 @@
+---
+sidebar_position: 1
+id: create-rename-move
+title: Create - Rename - Move
+description: Create - Rename - Move
+draft: false
+---
+
+# Create, Rename, and Move Files and Folders
+
+The OpenCloud Android App makes it easy to manage your content. You can create new folders and files, rename items, and move them to different locations — all directly from your Android phone or tablet.
+
+## Creating Files and Folders
+
+Tap the “+” button in the bottom right corner.
+
+<img src={require("../img/files-and-folders/create-rename-move-android/create-new.png").default} alt="Create new" height="400"/>
+
+Choose what you want to create from the menu:
+
+### Create a Folder
+
+- Tap "New folder"
+- Enter a name for your folder
+- Tap "OK"
+
+<img src={require("../img/files-and-folders/create-rename-move-android/create-folder.png").default} alt="Create folder" height="400"/>
+
+### Create a Document (Requires Collabora)
+
+If Collabora Online is enabled in your OpenCloud instance:
+
+- Tap "New document"
+- Choose the document type (text, spreadsheet, presentation)
+- Enter a filename and confirm
+
+<img src={require("../img/files-and-folders/create-rename-move-android/choose-file-type.png").default} alt="Choose file type" height="400"/>
+
+The document will open in a built-in browser window using **Collabora** for editing.
+
+<img src={require("../img/files-and-folders/create-rename-move-android/open-collabora.png").default} alt="Open Collabora" height="400"/>
+<img src={require("../img/files-and-folders/create-rename-move-android/edit-collabora.png").default} alt="Edit Collabora" height="400"/>
+
+## Rename Files or Folders
+
+To rename a file or folder in the OpenCloud Android App:
+
+- Tap the "three dots (...)" next to the item you want to rename
+
+<img src={require("../img/files-and-folders/create-rename-move-android/three-dots.png").default} alt="Click on the three dots menu" height="400"/>
+
+- Select "Rename" from the menu
+
+<img src={require("../img/files-and-folders/create-rename-move-android/select-rename.png").default} alt="Select rename" height="400"/>
+
+- Enter the new name for the file or folder
+
+<img src={require("../img/files-and-folders/create-rename-move-android/enter-rename.png").default} alt="Enter the new name" height="400"/>
+
+- Tap "OK"to apply the changes
+
+<img src={require("../img/files-and-folders/create-rename-move-android/tap-ok.png").default} alt="Tap OK" height="400"/>
+<img src={require("../img/files-and-folders/create-rename-move-android/new-name-applied.png").default} alt="New applied name" height="400"/>
+
+The new name will be saved immediately.
+
+## Move Files or Folders
+
+To move a file or folder in the OpenCloud Android App:
+
+- Tap the "three dots (...)" next to the file or folder you want to move
+
+<img src={require("../img/files-and-folders/create-rename-move-android/three-dots-move.png").default} alt="Select the three dot menu" height="400"/>
+
+- Select "Move" or "Copy" from the menu
+
+<img src={require("../img/files-and-folders/create-rename-move-android/select-move-or-copy.png").default} alt="Select move or copy" height="400"/>
+
+Navigate to the destination folder
+Tap "Move here" or "Copy here"
+
+<img src={require("../img/files-and-folders/create-rename-move-android/select-paste.png").default} alt="Select paste" height="400"/>
+<img src={require("../img/files-and-folders/create-rename-move-android/file-moved.png").default} alt="File is moved" height="400"/>
+
+The file or folder will now appear in the new location.
diff --git a/versioned_docs/version-7.x/user/android-app/files-and-folders/upload-make-available-offline.md b/versioned_docs/version-7.x/user/android-app/files-and-folders/upload-make-available-offline.md
new file mode 100644
index 000000000..fbf1dcd57
--- /dev/null
+++ b/versioned_docs/version-7.x/user/android-app/files-and-folders/upload-make-available-offline.md
@@ -0,0 +1,64 @@
+---
+sidebar_position: 2
+id: upload-make-available-offline
+title: Upload - Make available offline
+description: Upload files in Android
+draft: false
+---
+
+# Upload Files in Android
+
+With the OpenCloud Android App, you can easily upload files and make them available for offline use.
+
+## Upload Files
+
+### Open the Desired Folder
+
+Navigate to the folder where you want to upload a file.
+
+### Tap the “+” icon in the bottom right corner
+
+and choose "Upload"
+<img src={require("../img/files-and-folders/upload-make-available-offline-android/upload-plus-button.png").default} alt="Plus Button" height="400"/>
+
+### Choose an Upload Option
+
+From the menu, you can choose:
+
+- "Upload" – upload a file from your device storage
+- "Picture from camera" – upload a photo or video from smartphone or tablet camera
+
+<img src={require("../img/files-and-folders/upload-make-available-offline-android/upload-options.png").default} alt="Upload Options" height="400"/>
+
+### Confirm the Selection
+
+Choose the file or media you want to upload. The upload will begin automatically.
+
+## Make Files Available Offline
+
+You can make files available offline so you can access them even without an internet connection.
+
+### Tap the three dots (...) next to the file
+
+<img src={require("../img/files-and-folders/upload-make-available-offline-android/three-dots.png").default} alt="Three dots menu" height="400"/>
+
+### Select “Set as available offline”
+
+The file will be downloaded and saved locally on your device.
+
+<img src={require("../img/files-and-folders/upload-make-available-offline-android/make-available-offline.png").default} alt="Make available offline" height="400"/>
+
+:::info
+Offline files are marked with a pink circle containing a white checkmark.
+:::
+
+<img src={require("../img/files-and-folders/upload-make-available-offline-android/marked-offline.png").default} alt="Marked offline" height="400"/>
+
+## Remove Offline Availability
+
+To free up space:
+
+- Tap the three dots (...) on an offline file
+- Select “Unset as available offline”
+
+These features help you stay productive — even when you’re offline!
diff --git a/versioned_docs/version-7.x/user/android-app/general/_category_.json b/versioned_docs/version-7.x/user/android-app/general/_category_.json
new file mode 100644
index 000000000..474684fea
--- /dev/null
+++ b/versioned_docs/version-7.x/user/android-app/general/_category_.json
@@ -0,0 +1,10 @@
+{
+  "label": "General",
+  "position": 1,
+  "key": "android-general",
+  "link": {
+    "type": "generated-index",
+    "description": "Tutorials about installing, setup and overview of the OpenCloud Android App.",
+    "slug": "user/android-app/general/"
+  }
+}
diff --git a/versioned_docs/version-7.x/user/android-app/general/installation.md b/versioned_docs/version-7.x/user/android-app/general/installation.md
new file mode 100644
index 000000000..37ecbead0
--- /dev/null
+++ b/versioned_docs/version-7.x/user/android-app/general/installation.md
@@ -0,0 +1,37 @@
+---
+sidebar_position: 1
+id: installation
+title: Install OpenCloud Android app
+description: Install OpenCloud Android app
+draft: false
+---
+
+# Install OpenCloud Android app
+
+Tutorial how to install the OpenCloud Android App.
+
+## Play Store
+
+Open the Play Store on your Android Smartphone or Tablet.
+
+## OpenCloud
+
+Search for "OpenCloud" or click the following link to go directly to the app:
+
+[OpenCloud on the Play Store](https://play.google.com/store/apps/details?id=eu.opencloud.android)
+
+<img src={require(".././img/installation/android-installation.png").default} alt="Android Installation" height="400"/>
+
+## Install
+
+Tap "Get" to install the app.
+
+## App Icon
+
+After installation, you will find the OpenCloud app on your home screen.
+
+<img src={require(".././img/installation/icon-on-screen.png").default} alt="Icon" height="400"/>
+
+## Set it up
+
+Open the app and follow the on-screen instructions to set it up.
diff --git a/versioned_docs/version-7.x/user/android-app/general/overview/_category_.json b/versioned_docs/version-7.x/user/android-app/general/overview/_category_.json
new file mode 100644
index 000000000..946ecf661
--- /dev/null
+++ b/versioned_docs/version-7.x/user/android-app/general/overview/_category_.json
@@ -0,0 +1,10 @@
+{
+  "label": "Overview",
+  "position": 3,
+  "key": "android-overview",
+  "link": {
+    "type": "generated-index",
+    "description": "Overview of the user interface of the OpenCloud Android App.",
+    "slug": "user/android-app/general/overview/"
+  }
+}
diff --git a/versioned_docs/version-7.x/user/android-app/general/overview/account-fileslist.md b/versioned_docs/version-7.x/user/android-app/general/overview/account-fileslist.md
new file mode 100644
index 000000000..5459bbee8
--- /dev/null
+++ b/versioned_docs/version-7.x/user/android-app/general/overview/account-fileslist.md
@@ -0,0 +1,61 @@
+---
+sidebar_position: 2
+id: account-fileslist
+title: Fileslist Menu
+description: Fileslist Menu
+draft: false
+---
+
+# Here a is an overview of the fileslist menu in the OpenCloud Android-App
+
+This section explains the core interface elements of the OpenCloud Android app and their functionality.
+
+<img src={require("../../img/overview/fileslist.png").default} alt="Fileslist-Overview" style={{ width: '400px', marginRight: '60px' }} />
+
+## 1. Account Menu
+
+Provides access to account settings.
+
+## 2. Search
+
+Lets the user search for files, folders, or shared items within the app.
+
+## 3. Manage Accounts
+
+Lets the user see the active account and add another account.
+
+## 4. Sort by
+
+Lets the user sort files by name, date, size, or other criteria.
+
+## 5. View Mode
+
+Allows switching between different view modes.
+
+## 6. Files List
+
+Shows the contents of the current folder as a list of files and folders.
+
+## 7. Add Button
+
+Opens options to upload files, create folders, or add new content.
+
+## 8. Personal
+
+Allows quick switch to personal space.
+
+## 9. Shares
+
+Allows quick switch to shares list.
+
+## 10. Spaces
+
+Allows quick switch to spaces list.
+
+## 11. Uploads
+
+Allows quick switch to uploads list.
+
+## 12. Offline
+
+Allows quick switch to a list where files and folders are available offline.
diff --git a/versioned_docs/version-7.x/user/android-app/general/overview/account-overview.md b/versioned_docs/version-7.x/user/android-app/general/overview/account-overview.md
new file mode 100644
index 000000000..cc1647fb7
--- /dev/null
+++ b/versioned_docs/version-7.x/user/android-app/general/overview/account-overview.md
@@ -0,0 +1,43 @@
+---
+sidebar_position: 1
+id: account-overview
+title: Account Menu
+description: Overview of the Account Menu
+draft: false
+---
+
+# Account Menu
+
+Here a is a overview of the account-menue in the OpenCloud Android-App
+
+<img src={require("../../img/overview/account-1.png").default} alt="Account Menue Button" style={{ width: '300px', marginRight: '60px' }} />
+
+<img src={require("../../img/overview/account-2.png").default} alt="Account Menue" style={{ width: '300px', marginRight: '60px' }} />
+
+## 1. Account Menu Item
+
+Opens the main account options and settings.
+
+## 2. Active Account
+
+Shows which user account is currently active.
+
+## 3. Settings Menu Item
+
+Opens the general settings and configuration options.
+
+## 4. Feedback Item
+
+Here you can send us feedback about your experience with the OpenCloud Android app.
+
+## 5. Help Menu Item
+
+Here you will find links to our documentation page and help links.
+
+## 6. Privacy Policy Item
+
+A full entry on our privacy policy can be found here.
+
+## 7. Used Quota
+
+Displays the quota you have used so far.
diff --git a/versioned_docs/version-7.x/user/android-app/general/set-up.md b/versioned_docs/version-7.x/user/android-app/general/set-up.md
new file mode 100644
index 000000000..ca279a0a2
--- /dev/null
+++ b/versioned_docs/version-7.x/user/android-app/general/set-up.md
@@ -0,0 +1,46 @@
+---
+sidebar_position: 2
+id: set-up
+title: Set up OpenCloud Android app
+description: Set up OpenCloud Android app
+draft: false
+---
+
+# Setting Up Your OpenCloud Account
+
+After installing the app, you can now set up your OpenCloud account.
+
+## Start the Setup
+
+- When you first start the OpenCloud Android app, you will see the following screen.
+
+  <img src={require(".././img/set-up/start-setup.png").default} alt="Start setup" height="400"/>
+
+- To set up an additional account, click on the 'Manage accounts' button and select 'Add account'.
+
+  <img src={require(".././img/set-up/additional-account.png").default} alt="Additional account" height="400"/>
+
+## Enter Your Server URL
+
+- Enter your OpenCloud Server URL (e.g., `https://cloud.example.com`)
+- Tap ">" to continue.
+
+  <img src={require(".././img/set-up/enter-server-url.png").default} alt="Enter server URL" height="400"/>
+
+## The Login Page
+
+- The Login Page will be opening and you musst type in your username and password.
+- Then tap "Log in".
+
+- In the following screen, grant the app permission to access your user information and maintain continuous access by tapping the "Allow" button.
+
+  <img src={require(".././img/set-up/open-login-page.png").default} alt="Open Login Page" height="400"/>
+  <img src={require(".././img/set-up/continue-sign-in.png").default} alt="Continue sign in" height="400"/>
+
+## Finalize Setup
+
+Once login is complete, your account will be added to the app
+
+Your OpenCloud account is now fully set up and ready to use!
+
+<img src={require(".././img/set-up/account-set-up.png").default} alt="Account is set up" height="400"/>
diff --git a/versioned_docs/version-7.x/user/android-app/general/settings.md b/versioned_docs/version-7.x/user/android-app/general/settings.md
new file mode 100644
index 000000000..4daf8e487
--- /dev/null
+++ b/versioned_docs/version-7.x/user/android-app/general/settings.md
@@ -0,0 +1,89 @@
+---
+sidebar_position: 4
+id: settings
+title: Settings
+description: Settings in OpenCloud Android app
+draft: false
+---
+
+# Settings
+
+In the Android app settings changes can be made, such as
+
+    - Security
+    - Manage notifications
+    - Logging
+    - Advanced settings
+    and more
+
+<img src={require(".././img/settings/settings.png").default} alt="Settings" width="400"/>
+
+## Userinterface
+
+### 1. Security
+
+Here you can set locks to access the app and allow touches with other visible windows.
+
+### 2. Manage notifications
+
+Here you can allow notifications from the OpenCloud Android app.
+
+### 3. Logging
+
+Here you can activate and deactivate the logging function and specify the storage location of the log file.
+
+### 4. Automatic picture uploads
+
+Here you can manage location and behavior of the pictures uploaded automatically.
+
+### 5. Automatic video uploads
+
+Here you can manage location and behavior of the videos uploaded automatically.
+
+### 6. Advanced
+
+Here you can set the following options:<br/>
+
+#### Show hidden files
+
+- Enable or disable the display of hidden files.
+
+#### Delete local copies
+
+- Remove automatically downloaded files that are not available offline, when the time since their last usage exceeds the selected time.
+
+### 7. More
+
+Here you can set the following options:<br/>
+
+#### Help
+
+- Here you will find links to our documentation page and help links.
+
+#### Sync you contacts, calendars and tasks
+
+- Here you can set what you will sync with the OpenCloud Android app.
+
+#### Access document provider
+
+- Suggested app to browse the files on your device via the Android native file explorer.
+
+#### Send feedback
+
+- Here you can send us a feedback of your experience with the OpenCloud Android app.
+
+#### Recommend to a friend
+
+- Here you can forward a link to download the Android app.
+
+### 8. Privacy Policy
+
+A full entry on our privacy policy can be found here.
+
+### 9. What's new in the latest version?
+
+Here you can find informations about the changes and new stuff in the latest version of the OpenCloud Android app.
+
+### 10. App version
+
+Here you can see which app version is being used.
diff --git a/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/choose-file-type.png b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/choose-file-type.png
new file mode 100644
index 000000000..c332d51ac
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/choose-file-type.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/create-folder.png b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/create-folder.png
new file mode 100644
index 000000000..fe378e07f
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/create-folder.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/create-new.png b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/create-new.png
new file mode 100644
index 000000000..27f5c999f
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/create-new.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/edit-collabora.png b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/edit-collabora.png
new file mode 100644
index 000000000..a45531129
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/edit-collabora.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/enter-rename.png b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/enter-rename.png
new file mode 100644
index 000000000..bd21dc413
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/enter-rename.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/file-moved.png b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/file-moved.png
new file mode 100644
index 000000000..1e3e7882d
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/file-moved.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/new-name-applied.png b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/new-name-applied.png
new file mode 100644
index 000000000..9cd1a3bf7
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/new-name-applied.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/open-collabora.png b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/open-collabora.png
new file mode 100644
index 000000000..2cd160b02
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/open-collabora.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/select-move-or-copy.png b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/select-move-or-copy.png
new file mode 100644
index 000000000..7502f321e
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/select-move-or-copy.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/select-paste.png b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/select-paste.png
new file mode 100644
index 000000000..d4ad9ec67
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/select-paste.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/select-rename.png b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/select-rename.png
new file mode 100644
index 000000000..a7b912180
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/select-rename.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/tap-ok.png b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/tap-ok.png
new file mode 100644
index 000000000..e03c214c8
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/tap-ok.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/three-dots-move.png b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/three-dots-move.png
new file mode 100644
index 000000000..1e0a44267
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/three-dots-move.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/three-dots.png b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/three-dots.png
new file mode 100644
index 000000000..1e0a44267
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/create-rename-move-android/three-dots.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/make-available-offline.png b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/make-available-offline.png
new file mode 100644
index 000000000..48deeab38
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/make-available-offline.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/marked-offline.png b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/marked-offline.png
new file mode 100644
index 000000000..4fcffecdb
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/marked-offline.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/three-dots.png b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/three-dots.png
new file mode 100644
index 000000000..081c1bf88
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/three-dots.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/upload-options.png b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/upload-options.png
new file mode 100644
index 000000000..1079de399
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/upload-options.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/upload-plus-button.png b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/upload-plus-button.png
new file mode 100644
index 000000000..cfabce3fd
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/files-and-folders/upload-make-available-offline-android/upload-plus-button.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/installation/android-installation.png b/versioned_docs/version-7.x/user/android-app/img/installation/android-installation.png
new file mode 100644
index 000000000..b516c104e
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/installation/android-installation.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/installation/icon-on-screen.png b/versioned_docs/version-7.x/user/android-app/img/installation/icon-on-screen.png
new file mode 100644
index 000000000..1d0422dec
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/installation/icon-on-screen.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/overview/account-1.png b/versioned_docs/version-7.x/user/android-app/img/overview/account-1.png
new file mode 100644
index 000000000..c153b76aa
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/overview/account-1.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/overview/account-2.png b/versioned_docs/version-7.x/user/android-app/img/overview/account-2.png
new file mode 100644
index 000000000..f4415c9a0
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/overview/account-2.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/overview/fileslist.png b/versioned_docs/version-7.x/user/android-app/img/overview/fileslist.png
new file mode 100644
index 000000000..3a11d07e4
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/overview/fileslist.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/search/search-result.png b/versioned_docs/version-7.x/user/android-app/img/search/search-result.png
new file mode 100644
index 000000000..8bf41bec2
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/search/search-result.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/search/search-symbol.png b/versioned_docs/version-7.x/user/android-app/img/search/search-symbol.png
new file mode 100644
index 000000000..f5f78e601
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/search/search-symbol.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/search/searchbar.png b/versioned_docs/version-7.x/user/android-app/img/search/searchbar.png
new file mode 100644
index 000000000..2b85d863c
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/search/searchbar.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/set-up/account-set-up.png b/versioned_docs/version-7.x/user/android-app/img/set-up/account-set-up.png
new file mode 100644
index 000000000..6ca0dc7cd
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/set-up/account-set-up.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/set-up/additional-account.png b/versioned_docs/version-7.x/user/android-app/img/set-up/additional-account.png
new file mode 100644
index 000000000..639edd194
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/set-up/additional-account.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/set-up/continue-sign-in.png b/versioned_docs/version-7.x/user/android-app/img/set-up/continue-sign-in.png
new file mode 100644
index 000000000..6128f26e0
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/set-up/continue-sign-in.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/set-up/enter-server-url.png b/versioned_docs/version-7.x/user/android-app/img/set-up/enter-server-url.png
new file mode 100644
index 000000000..35d49b60d
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/set-up/enter-server-url.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/set-up/open-login-page.png b/versioned_docs/version-7.x/user/android-app/img/set-up/open-login-page.png
new file mode 100644
index 000000000..ac3243f44
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/set-up/open-login-page.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/set-up/start-setup.png b/versioned_docs/version-7.x/user/android-app/img/set-up/start-setup.png
new file mode 100644
index 000000000..cb68cc513
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/set-up/start-setup.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/settings/settings.png b/versioned_docs/version-7.x/user/android-app/img/settings/settings.png
new file mode 100644
index 000000000..fb087e6b3
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/settings/settings.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/shares/invite/invite-menue.png b/versioned_docs/version-7.x/user/android-app/img/shares/invite/invite-menue.png
new file mode 100644
index 000000000..cf6edd318
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/shares/invite/invite-menue.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/shares/invite/invite-option.png b/versioned_docs/version-7.x/user/android-app/img/shares/invite/invite-option.png
new file mode 100644
index 000000000..2eeb23f15
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/shares/invite/invite-option.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/shares/invite/permissions.png b/versioned_docs/version-7.x/user/android-app/img/shares/invite/permissions.png
new file mode 100644
index 000000000..bd1be6770
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/shares/invite/permissions.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/shares/invite/searchbar.png b/versioned_docs/version-7.x/user/android-app/img/shares/invite/searchbar.png
new file mode 100644
index 000000000..cf83b2fb7
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/shares/invite/searchbar.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/shares/invite/shared-with.png b/versioned_docs/version-7.x/user/android-app/img/shares/invite/shared-with.png
new file mode 100644
index 000000000..25e881a5b
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/shares/invite/shared-with.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/shares/invite/sharing-button.png b/versioned_docs/version-7.x/user/android-app/img/shares/invite/sharing-button.png
new file mode 100644
index 000000000..2e025f7fb
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/shares/invite/sharing-button.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/shares/invite/three-dot-menue.png b/versioned_docs/version-7.x/user/android-app/img/shares/invite/three-dot-menue.png
new file mode 100644
index 000000000..667b47de3
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/shares/invite/three-dot-menue.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/shares/links/create-link-button.png b/versioned_docs/version-7.x/user/android-app/img/shares/links/create-link-button.png
new file mode 100644
index 000000000..aa0f502f6
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/shares/links/create-link-button.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/shares/links/create-link-options.png b/versioned_docs/version-7.x/user/android-app/img/shares/links/create-link-options.png
new file mode 100644
index 000000000..77bff0c7b
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/shares/links/create-link-options.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/shares/links/created-link.png b/versioned_docs/version-7.x/user/android-app/img/shares/links/created-link.png
new file mode 100644
index 000000000..6491ab9f4
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/shares/links/created-link.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/shares/links/expiration-date.png b/versioned_docs/version-7.x/user/android-app/img/shares/links/expiration-date.png
new file mode 100644
index 000000000..3ff37f3ab
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/shares/links/expiration-date.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/shares/links/password.png b/versioned_docs/version-7.x/user/android-app/img/shares/links/password.png
new file mode 100644
index 000000000..b949382dd
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/shares/links/password.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/shares/links/share-button.png b/versioned_docs/version-7.x/user/android-app/img/shares/links/share-button.png
new file mode 100644
index 000000000..d2d3a4352
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/shares/links/share-button.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/shares/links/sharing-button.png b/versioned_docs/version-7.x/user/android-app/img/shares/links/sharing-button.png
new file mode 100644
index 000000000..2e025f7fb
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/shares/links/sharing-button.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/shares/links/three-dot-menue.png b/versioned_docs/version-7.x/user/android-app/img/shares/links/three-dot-menue.png
new file mode 100644
index 000000000..667b47de3
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/shares/links/three-dot-menue.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/shortcuts/create-button.png b/versioned_docs/version-7.x/user/android-app/img/shortcuts/create-button.png
new file mode 100644
index 000000000..153f12615
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/shortcuts/create-button.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/shortcuts/created-shortcut.png b/versioned_docs/version-7.x/user/android-app/img/shortcuts/created-shortcut.png
new file mode 100644
index 000000000..0e78f28f1
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/shortcuts/created-shortcut.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/shortcuts/plus-button.png b/versioned_docs/version-7.x/user/android-app/img/shortcuts/plus-button.png
new file mode 100644
index 000000000..41268f1a8
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/shortcuts/plus-button.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/shortcuts/shortcut-menue.png b/versioned_docs/version-7.x/user/android-app/img/shortcuts/shortcut-menue.png
new file mode 100644
index 000000000..b3b0e52b6
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/shortcuts/shortcut-menue.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/shortcuts/shortcut-name.png b/versioned_docs/version-7.x/user/android-app/img/shortcuts/shortcut-name.png
new file mode 100644
index 000000000..e5869e75d
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/shortcuts/shortcut-name.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/shortcuts/url.png b/versioned_docs/version-7.x/user/android-app/img/shortcuts/url.png
new file mode 100644
index 000000000..2b595881f
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/shortcuts/url.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/spaces/Search-menue.png b/versioned_docs/version-7.x/user/android-app/img/spaces/Search-menue.png
new file mode 100644
index 000000000..996affaef
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/spaces/Search-menue.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/spaces/search-button.png b/versioned_docs/version-7.x/user/android-app/img/spaces/search-button.png
new file mode 100644
index 000000000..51cb9a766
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/spaces/search-button.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/spaces/spaces-button.png b/versioned_docs/version-7.x/user/android-app/img/spaces/spaces-button.png
new file mode 100644
index 000000000..49706c6b7
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/spaces/spaces-button.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/spaces/spaces-overview.png b/versioned_docs/version-7.x/user/android-app/img/spaces/spaces-overview.png
new file mode 100644
index 000000000..ca0964dca
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/spaces/spaces-overview.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/spaces/spaces-plus-symbol-menue.png b/versioned_docs/version-7.x/user/android-app/img/spaces/spaces-plus-symbol-menue.png
new file mode 100644
index 000000000..44e50695e
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/spaces/spaces-plus-symbol-menue.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/img/spaces/spaces-plus-symbol.png b/versioned_docs/version-7.x/user/android-app/img/spaces/spaces-plus-symbol.png
new file mode 100644
index 000000000..d6bcb82a4
Binary files /dev/null and b/versioned_docs/version-7.x/user/android-app/img/spaces/spaces-plus-symbol.png differ
diff --git a/versioned_docs/version-7.x/user/android-app/index.md b/versioned_docs/version-7.x/user/android-app/index.md
new file mode 100644
index 000000000..a576c6f64
--- /dev/null
+++ b/versioned_docs/version-7.x/user/android-app/index.md
@@ -0,0 +1,18 @@
+---
+sidebar_position: 0
+id: android-app-overview
+title: OpenCloud Android App
+---
+
+# OpenCloud Android App
+
+The OpenCloud Android app provides mobile access to your files, spaces, and shares. It is designed for quick access on the go, with support for setup, search, shortcuts, and file management.
+
+## What you will find here
+
+- [General](./general/) - Install the app, set it up, and learn the main interface and settings.
+- [Files and folders](./files-and-folders/) - Create and edit content, upload files, and make items available offline.
+- [Spaces](./spaces.md) - Work with Spaces and their available actions on Android.
+- [Search](./search.md) - Find files and folders from within the Android app.
+- [Shortcuts](./shortcuts.md) - Create shortcuts to files or web links.
+- [Shares](./shares/) - Invite people and create share links from the Android app.
diff --git a/versioned_docs/version-7.x/user/android-app/search.md b/versioned_docs/version-7.x/user/android-app/search.md
new file mode 100644
index 000000000..538158a8e
--- /dev/null
+++ b/versioned_docs/version-7.x/user/android-app/search.md
@@ -0,0 +1,29 @@
+---
+sidebar_position: 4
+id: search
+title: Search
+description: Search
+draft: false
+---
+
+# Search function
+
+Here we explain how to use the search function in the OpenCloud Android app
+
+## Search icon
+
+Move to the Space where you want to search and click on the search icon to open the search function
+
+<img src={require("./img/search/search-symbol.png").default} alt="Magnifying glass icon" width="300"/>
+
+## Search bar
+
+You can search for file or folder names in the search bar
+
+<img src={require("./img/search/searchbar.png").default} alt="Search bar" width="300"/>
+
+## Search result
+
+This area displays the search results
+
+<img src={require("./img/search/search-result.png").default} alt="Search results" width="300"/>
diff --git a/versioned_docs/version-7.x/user/android-app/shares/_category_.json b/versioned_docs/version-7.x/user/android-app/shares/_category_.json
new file mode 100644
index 000000000..c251f8e26
--- /dev/null
+++ b/versioned_docs/version-7.x/user/android-app/shares/_category_.json
@@ -0,0 +1,10 @@
+{
+    "label": "Shares",
+    "position": 3,
+    "key": "android-shares",
+    "link": {
+      "type": "generated-index",
+      "description": "Tutorials about creating shares the OpenCloud Android App.",
+      "slug": "user/android-app/shares/"
+    }
+  }
\ No newline at end of file
diff --git a/versioned_docs/version-7.x/user/android-app/shares/invite.md b/versioned_docs/version-7.x/user/android-app/shares/invite.md
new file mode 100644
index 000000000..85ed20c10
--- /dev/null
+++ b/versioned_docs/version-7.x/user/android-app/shares/invite.md
@@ -0,0 +1,55 @@
+---
+sidebar_position: 1
+id: invite
+title: Invite to share
+description: Invite to share
+draft: false
+---
+
+# Share files and folders with people and groups via invitation
+
+Here we explain how to share files and folders via invitation with other people and groups within your OpenCloud in the OpenCloud Android app
+
+## Three-dot-menu
+
+Click the "three-dot menu" next to the file or folder
+
+<img src={require("../img/shares/invite/three-dot-menue.png").default} alt="Three-dot menue" height="400"/>
+
+## Share
+
+Now select the menue item "Share"
+
+<img src={require("../img/shares/invite/sharing-button.png").default} alt="Shareing-Button" height="400"/>
+
+## Users and Groups
+
+In the following selection, click on the Plus at "Users and Groups"
+
+<img src={require("../img/shares/invite/invite-option.png").default} alt="Share with" height="400"/>
+
+## Share menu
+
+The Share menu opens, where you can use the search bar to search for people or groups you want to invite
+
+<img src={require("../img/shares/invite/invite-menue.png").default} alt="Share with menue" height="400"/>
+<img src={require("../img/shares/invite/searchbar.png").default} alt="Search bar" height="400"/>
+
+## Permissions
+
+To configure the sharing permissions, click the pencil icon located next to the trash bin icon
+
+<img src={require("../img/shares/invite/permissions.png").default} alt="Permissions" height="400"/>
+
+- Create:  
+  Users can create and upload files and folders.
+- Change:  
+  Users can edit files and folders
+- Delete:  
+  Users can delete files and folders.
+
+## Created
+
+Once the invitation is created, you will see it in the file or folder overview
+
+<img src={require("../img/shares/invite/shared-with.png").default} alt="Shared with" height="400"/>
diff --git a/versioned_docs/version-7.x/user/android-app/shares/links.md b/versioned_docs/version-7.x/user/android-app/shares/links.md
new file mode 100644
index 000000000..fc44295dc
--- /dev/null
+++ b/versioned_docs/version-7.x/user/android-app/shares/links.md
@@ -0,0 +1,63 @@
+---
+sidebar_position: 2
+id: links
+title: Share via link
+description: Share via link
+draft: false
+---
+
+# Share files and folders via link
+
+Here we explain how to share files and folders with others via link in the OpenCloud Android app
+
+## Three dot menu
+
+Click the three-dot menu next to the file or folder
+
+<img src={require("../img/shares/links/three-dot-menue.png").default} alt="Three-dot menue" height="400"/>
+
+## Share
+
+Now select the menue item “Share”
+
+<img src={require("../img/shares/links/sharing-button.png").default} alt="Share" height="400"/>
+
+## Public link
+
+In the following selection, click on "Public links"
+
+<img src={require("../img/shares/links/create-link-button.png").default} alt="Create link" height="400"/>
+
+## Create link
+
+Here you can select and specify several options for the link to be created
+
+<img src={require("../img/shares/links/create-link-options.png").default} alt="Overview link menue" height="400"/>
+
+- Link name
+
+  Enter a name for your link here
+
+- Password
+
+A password is required. Please enter one to proceed.
+
+<img src={require("../img/shares/links/password.png").default} alt="Password" height="400"/>
+
+- Expiration
+
+Here you can specify a period of time for which the link should be available
+
+<img src={require("../img/shares/links/expiration-date.png").default} alt="Link expiration date" height="400"/>
+
+## Save Link
+
+To create the link you must now click on "Save"
+
+<img src={require("../img/shares/links/share-button.png").default} alt="Share" height="400"/>
+
+## Created link
+
+Once the link is created, you will see it with the assigned name in the file or folder overview
+
+<img src={require("../img/shares/links/created-link.png").default} alt="created link" height="400"/>
diff --git a/versioned_docs/version-7.x/user/android-app/shortcuts.md b/versioned_docs/version-7.x/user/android-app/shortcuts.md
new file mode 100644
index 000000000..6dabb5a91
--- /dev/null
+++ b/versioned_docs/version-7.x/user/android-app/shortcuts.md
@@ -0,0 +1,47 @@
+---
+sidebar_position: 5
+id: shortcuts
+title: Shortcut in the OpenCloud Android app
+description: Shortcut
+draft: false
+---
+
+# Shortcut in the OpenCloud Android app
+
+Here we show you how to create shortcuts in the Android app
+
+## Plus symbol
+
+Click on the "Plus symbol" and select "New Shortcut"
+
+<img src={require("./img/shortcuts/plus-button.png").default} alt="Plus button" width="300"/>
+
+## Shortcut menu
+
+A menue opens with options for shortcuts
+
+<img src={require("./img/shortcuts/shortcut-menue.png").default} alt="Shortcut menue" width="300"/>
+
+## Enter URL
+
+To create a shortcut to a website, enter the address of the website under "URL"
+
+<img src={require("./img/shortcuts/url.png").default} alt="URL" width="300"/>
+
+## Enter Shortcut name
+
+Here you enter a name for the shortcut with which it will be displayed
+
+<img src={require("./img/shortcuts/shortcut-name.png").default} alt="Name of the shortcut" width="300"/>
+
+## Create button
+
+To create the shortcut, click on "Create"
+
+<img src={require("./img/shortcuts/create-button.png").default} alt="Create button" width="300"/>
+
+## Created shortcut
+
+Your created shortcut is now displayed and can be used
+
+<img src={require("./img/shortcuts/created-shortcut.png").default} alt="Shortcut" width="300"/>
diff --git a/versioned_docs/version-7.x/user/android-app/spaces.md b/versioned_docs/version-7.x/user/android-app/spaces.md
new file mode 100644
index 000000000..4589d7c88
--- /dev/null
+++ b/versioned_docs/version-7.x/user/android-app/spaces.md
@@ -0,0 +1,56 @@
+---
+sidebar_position: 6
+id: spaces
+title: Spaces
+description: Spaces in OpenCloud Android app
+draft: false
+---
+
+# The "Spaces" Section in the OpenCloud Android App
+
+The "Spaces" section provides a central place for collaboration in groups or teams. In a Space, multiple users can access files and folders together, organize content, and track changes
+
+## Spaces Overview
+
+To open the Spaces Overview, tap the "Spaces button" in the bottom line of the the screen.
+
+<img src={require("./img/spaces/spaces-button.png").default} alt="Spaces Button" style={{ width: '300px', marginRight: '60px' }} />
+
+Afterwards, the Spaces Overview appears, listing all Spaces you are a member of or have created yourself.
+
+<img src={require("./img/spaces/spaces-overview.png").default} alt="Spaces Overview" style={{ width: '300px', marginRight: '60px' }} />
+
+## Search Function
+
+By tapping the **search icon**, the searchbar and the search menu for Spaces will open.
+<img src={require("./img/spaces/search-button.png").default} alt="Search Function" style={{ width: '300px', marginRight: '60px' }} />
+
+<img src={require("./img/spaces/Search-menue.png").default} alt="Search Menue" style={{ width: '300px', marginRight: '60px' }} />
+
+## Functions within a Space
+
+By tapping the plus icon, the available functions within a Space appear.
+
+<img src={require("./img/spaces/spaces-plus-symbol.png").default} alt="Plus Icon" style={{ width: '300px', marginRight: '60px' }} />
+
+<img src={require("./img/spaces/spaces-plus-symbol-menue.png").default} alt="Functions in Spaces" style={{ width: '400px', marginRight: '60px' }} />
+
+## Create Menu
+
+This section describes the available actions in the create menu of a Space.
+
+### 1. Upload
+
+Select files from your device and upload them to the Space.
+
+### 2. New Folder
+
+Create new folders to organize and structure content clearly.
+
+### 3. New Document
+
+Create a new document directly within the Space without using a separate app.
+
+### 4. New Shortcut
+
+Create a shortcut to a file or folder within the Space for quick access.
diff --git a/versioned_docs/version-7.x/user/collabora.md b/versioned_docs/version-7.x/user/collabora.md
new file mode 100644
index 000000000..5a726bdb6
--- /dev/null
+++ b/versioned_docs/version-7.x/user/collabora.md
@@ -0,0 +1,39 @@
+---
+sidebar_position: 10
+id: collabora
+title: Collabora in OpenCloud
+description: Collabora in OpenCloud
+draft: false
+---
+
+# Collabora Online in OpenCloud
+
+Collabora Online allows you to to create / edit documents (text, spreadsheets, presentations) directly in your browser without any additional software.  
+The integration with OpenCloud provides seamless access to your files and enables real-time collaboration.
+
+## Features in OpenCloud
+
+### Open files directly from the cloud
+
+All documents stored in OpenCloud can be opened directly in Collabora.
+
+### Collaborative editing
+
+Multiple users can work on the same document simultaneously, with real-time synchronization of changes.
+
+### Insert images from OpenCloud
+
+You can insert images stored in OpenCloud directly into your documents.
+
+### Auto-Save and versioning
+
+Changes are saved automatically, and all versions are retained within OpenCloud.
+
+### Supported formats
+
+Collabora Online supports common office formats such as `.odt`, `.docx`, `.ods`, `.xlsx`, `.odp`, and more.
+
+## Notes
+
+- Performance depends on your internet connection and the size of the document.
+- For advanced features or detailed instructions, we refer to the [official Collabora Online documentation](https://www.collaboraoffice.com/collabora-online/).
diff --git a/versioned_docs/version-7.x/user/common-issues.md b/versioned_docs/version-7.x/user/common-issues.md
new file mode 100644
index 000000000..98f097a3a
--- /dev/null
+++ b/versioned_docs/version-7.x/user/common-issues.md
@@ -0,0 +1,60 @@
+---
+sidebar_position: 11
+id: common-issues
+title: Common Issues & Help
+description: Common issues & help
+draft: false
+---
+
+# Common Issues & Help
+
+## Symlinks are not synchronized with the Desktop Client
+
+### Problem
+
+Symbolic links (symlinks) are not synchronized by the OpenCloud Desktop Client. Users often wonder why linked folders or files are missing or not accessible.
+
+### Reasoning
+
+Symlinks are deliberately excluded from synchronization for several important reasons:
+
+- Not portable: Symlinks often point to paths that only exist on the original machine. On another device, the target path likely doesn't exist.
+- Not usable in the web interface: The web interface cannot interpret or display symlinks.
+- Problematic on Windows: Symlink support on Windows is limited and inconsistent.
+- Risk of circular references: Symlinks could point to each other in loops, causing infinite synchronization cycles.
+- Loss of identity: If the client were to follow the link and synchronize the target, it would become a regular copy of the data. The original nature of the symlink would be lost.
+
+### Solution
+
+Sync Folders Outside the Sync Root Using Symlinks
+
+If you want to synchronize a folder that is located outside your sync root, you can still achieve this by moving the folder into your sync root and replacing the original location with a symlink.
+
+#### Example
+
+You want to synchronize the folder `/foo/A`, but your sync root is `/home/bar/OpenCloud/Personal`.
+
+1. Move the folder into (a sub-folder of) your sync root:
+
+   ```bash
+   mkdir -p /home/bar/OpenCloud/Personal/foo/
+   mv /foo/A /home/bar/OpenCloud/Personal/foo/A
+   ```
+
+2. Create a symlink in the original place:
+
+   ```bash
+   ln -s /home/bar/OpenCloud/Personal/foo/A /foo/A
+   ```
+
+## Files with "~$" in the name will not be synchronized
+
+The OpenCloud Desktop Client does not synchronize files starting with `~$`, such as `~$document.docx`.  
+These files are temporary lock files created by Microsoft Office applications (Word, Excel, PowerPoint) while a document is open.
+
+<img src={require("./img/common-issues/desktop-excluded.png").default} alt="Show the ~$ file is excluded from synchronizing" width="500"/>
+
+They are not actual content files but serve as internal markers to prevent multiple users from editing the same document simultaneously.  
+Once the file is closed, the `~$` file is automatically removed by Office.
+
+For more details, see the [Microsoft support article on temporary Office lock files created by Word/Excel/PowerPoint](https://support.microsoft.com/en-gb/topic/-the-document-is-locked-for-editing-by-another-user-error-message-when-you-try-to-open-a-document-in-word-10b92aeb-2e23-25e0-9110-370af6edb638?).
diff --git a/versioned_docs/version-7.x/user/desktop-client/_category_.json b/versioned_docs/version-7.x/user/desktop-client/_category_.json
new file mode 100644
index 000000000..de8566fa9
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/_category_.json
@@ -0,0 +1,8 @@
+{
+  "label": "OpenCloud Desktop",
+  "position": 6,
+  "link": {
+    "type": "doc",
+    "id": "desktop-client-overview"
+  }
+}
diff --git a/versioned_docs/version-7.x/user/desktop-client/common-functionality/_category_.json b/versioned_docs/version-7.x/user/desktop-client/common-functionality/_category_.json
new file mode 100644
index 000000000..110565308
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/common-functionality/_category_.json
@@ -0,0 +1,9 @@
+{
+  "label": "Common functionality",
+  "position": 4,
+  "link": {
+    "type": "generated-index",
+    "description": "Common functionalities for the OpenCloud Desktop Client.",
+    "slug": "user/desktop/common-functionality/"
+  }
+}
diff --git a/versioned_docs/version-7.x/user/desktop-client/common-functionality/conflict-files.md b/versioned_docs/version-7.x/user/desktop-client/common-functionality/conflict-files.md
new file mode 100644
index 000000000..4383e8f0b
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/common-functionality/conflict-files.md
@@ -0,0 +1,56 @@
+---
+sidebar_position: 4
+id: file-conflicts
+title: Handle file conflicts
+description: How to handle file conflicts
+draft: false
+---
+
+# Handle file conflicts in the OpenCloud Desktop Client
+
+When files are modified both locally and remotely before synchronization, the Desktop Client creates "conflicted copy" files—examples include:
+
+- `conflict.txt` (remote version)
+- `conflict (conflicted copy YYYY-MM-DD HHMMSS).txt` (local version)
+
+  <img src={require(".././img/conflict-files/conflict-file.png").default} alt="Conflict files in explorer" width="1920"/>
+
+This usually happens when:
+
+- Your local copy and the server copy diverge simultaneously,
+- and the app cannot automatically merge changes.
+
+## How You’ll Be Notified
+
+In the Desktop Client overview, a notification will appear when conflicting files are detected.  
+This means that multiple versions of the same file exist—often because changes were made on different devices before synchronization.  
+The notification serves as a prompt for you to review the conflicts and decide how to merge or keep the versions.
+
+<img src={require(".././img/conflict-files/conflict-info.png").default} alt="Notification about file conflicts in the Desktop Client" width="500"/>
+
+## Resolve File Conflicts Manually
+
+To resolve a conflict:
+
+- Open both files (the original and the conflicted copy).
+- Manually compare and merge the differences.
+- Edit the base file (`conflict.txt`) to include both sets of changes if needed.
+- After merging, delete the conflicted copy file.
+- Leave the updated base file—sync will now continue as normal.
+
+## Good Practices to Prevent Conflicts
+
+- Avoid editing the same file simultaneously on multiple devices.
+- Always wait for sync completion before making local changes.
+
+## Why Conflict Files Appear
+
+The Desktop Client determines a conflict when:
+
+- Local and remote versions of a file both change since the last sync.
+- Content is compared using file IDs and checksums—not only timestamps.
+- The client preserves both versions by renaming the local file with `"(conflicted copy ...)"`.
+
+Conflict files are created locally; they do not appear on the server unless explicitly uploaded.
+
+If you're experiencing frequent conflicts—especially on simple edits—it’s likely due to permission issues, read-only files, or syncing the same files via other tools. Check logs and file attributes accordingly.
diff --git a/versioned_docs/version-7.x/user/desktop-client/common-functionality/desktop-client-states.md b/versioned_docs/version-7.x/user/desktop-client/common-functionality/desktop-client-states.md
new file mode 100644
index 000000000..c5dcf9a0d
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/common-functionality/desktop-client-states.md
@@ -0,0 +1,106 @@
+---
+sidebar_position: 5
+id: desktop-client-states
+title: Desktop Client State
+description: Desktop Client State Icons
+draft: false
+---
+
+## Understanding Desktop Client State Icons
+
+The OpenCloud Desktop Client uses tray icons to show the current synchronization and connection state. This helps you quickly see whether everything is working normally or if something needs attention.
+
+## Quick Overview
+
+| Icon                                                                                                                              | State         | Meaning                                                              | Typical action                                         |
+| --------------------------------------------------------------------------------------------------------------------------------- | ------------- | -------------------------------------------------------------------- | ------------------------------------------------------ |
+| <img src={require(".././img/desktop-client-states/ocl-ui_logo-petrol.png").default} alt="Ready state" width="28"/>                | Ready         | The client is connected and all files are up to date.                | No action required.                                    |
+| <img src={require(".././img/desktop-client-states/ocl-ui_sync-petrol-colour.png").default} alt="Synchronizing state" width="28"/> | Synchronizing | Files are currently being uploaded or downloaded.                    | Wait until synchronization is complete.                |
+| <img src={require(".././img/desktop-client-states/ocl-ui_pause-petrol-colour.png").default} alt="Paused state" width="28"/>       | Paused        | Synchronization has been temporarily stopped.                        | Resume synchronization when you are ready.             |
+| <img src={require(".././img/desktop-client-states/ocl-ui_offline-petrol-colour.png").default} alt="Offline state" width="28"/>    | Offline       | The client cannot connect to the OpenCloud server.                   | Check your network connection and server availability. |
+| <img src={require(".././img/desktop-client-states/ocl-ui_info-petrol-colour.png").default} alt="Information state" width="28"/>   | Information   | The client shows a non-critical informational message.               | Review the message for details if needed.              |
+| <img src={require(".././img/desktop-client-states/ocl-ui_error-petrol-colour.png").default} alt="Error state" width="28"/>        | Error         | The client encountered a problem that blocks normal synchronization. | Open the client and resolve the reported issue.        |
+
+## Ready
+
+The Ready icon appears when the Desktop Client is connected to OpenCloud and no synchronization activity is currently taking place.
+
+- Connected to OpenCloud
+- No active file transfers
+- All files are up to date
+
+<img src={require(".././img/desktop-client-states/ocl-ui_logo-petrol.png").default} alt="Ready state" width="100"/>
+
+No action is required. Your files are fully synchronized.
+
+## Synchronizing
+
+The Synchronizing icon indicates that files are currently being uploaded or downloaded.
+
+- Files are being synchronized
+- Changes are actively being processed
+- The client is communicating with the server
+
+<img src={require(".././img/desktop-client-states/ocl-ui_sync-petrol-colour.png").default} alt="Synchronizing state" width="100"/>
+
+Wait until synchronization is complete before shutting down your device.
+
+## Paused
+
+The Paused icon appears when synchronization has been temporarily paused.
+
+- Synchronization is stopped
+- No files are transferred
+- Local and remote changes are not synchronized
+
+<img src={require(".././img/desktop-client-states/ocl-ui_pause-petrol-colour.png").default} alt="Paused state" width="100"/>
+
+Resume synchronization from the Desktop Client menu when you are ready to continue syncing files.
+
+## Offline
+
+The Offline icon indicates that the Desktop Client cannot currently connect to the OpenCloud server.
+
+- No connection to the server
+- Synchronization is unavailable
+- Local files remain accessible
+
+<img src={require(".././img/desktop-client-states/ocl-ui_offline-petrol-colour.png").default} alt="Offline state" width="100"/>
+
+Common causes include:
+
+- No internet connection
+- Server unavailable
+- DNS or network issues
+- Firewall restrictions
+
+Verify your network connection and confirm that the OpenCloud server is reachable.
+
+## Information
+
+The Information icon is used for informational messages that do not require immediate user action.
+
+- General notifications
+- Non-critical events
+- Informational client messages
+
+<img src={require(".././img/desktop-client-states/ocl-ui_info-petrol-colour.png").default} alt="Information state" width="100"/>
+
+Review the message for additional details if needed.
+
+## Error
+
+The Error icon indicates that the Desktop Client encountered an issue that prevents normal synchronization.
+
+- Synchronization failed
+- Authentication issues
+- Configuration problems
+- File access or permission errors
+
+<img src={require(".././img/desktop-client-states/ocl-ui_error-petrol-colour.png").default} alt="Error state" width="100"/>
+
+Open the Desktop Client and review the reported error. Synchronization may not continue until the issue has been resolved.
+
+:::info
+The visual appearance and coloring of the icons in the taskbar (Windows), dock (macOS), or system tray/panel (Linux) may vary depending on the operating system.
+:::
diff --git a/versioned_docs/version-7.x/user/desktop-client/common-functionality/file-names.md b/versioned_docs/version-7.x/user/desktop-client/common-functionality/file-names.md
new file mode 100644
index 000000000..139fdc049
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/common-functionality/file-names.md
@@ -0,0 +1,64 @@
+---
+sidebar_position: 5
+id: file-names
+title: File Naming Rules
+description: File Naming Rules for OpenCloud Desktop
+draft: false
+---
+
+# Filename restrictions on OpenCloud Desktop
+
+When using the OpenCloud Desktop Client, file and folder names must meet certain operating system (OS) requirements to ensure seamless sync across different platforms. These restrictions are not enforced by OpenCloud but originate from system limitations.
+
+## Key Guidelines
+
+- Avoid using prohibited characters or reserved words in filenames on any OS.
+- If syncing from Linux/macOS to a Windows-based share, make sure filenames are compatible with Windows naming restrictions.
+- To change casing (e.g., `File.txt` → `file.txt`) on Linux/macOS when syncing to Windows, rename the file to a completely new name, let it sync, then rename it to the desired casing.
+
+## Common Limitations
+
+### a. Maximum Path Length
+
+Windows limits file paths to 260 characters by default.  
+If your sync root exceeds this, the Desktop Client will warn:  
+"The path 'YOUR.LONG.PATH' is too long. Please enable long paths in the Windows settings or choose a different folder."
+
+On Windows 10 and later, you can remove this limit by enabling Long Paths. See [Microsoft’s documentation](https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#enable-long-paths-in-windows-10-version-1607-and-later).
+
+### b. Forbidden Characters
+
+| OS      | Forbidden Characters                       |
+| ------- | ------------------------------------------ |
+| Windows | `<`, `>`, `:`, `"`, `/`, `\`, `\|`,`?`,`*` |
+
+### c. Non-Printable ASCII Characters
+
+- Linux/macOS: NUL (character code 0)
+- Windows: ASCII 0 – 31  
+  While valid on some systems, such characters often cause issues during syncing.
+
+### d. Reserved Filenames (Windows)
+
+Avoid using any of the following as filenames:  
+`CON`, `PRN`, `AUX`, `NUL`, `COM1`–`COM9`, `LPT1`–`LPT9`
+
+### e. Special Rules
+
+- On Linux/macOS syncing to SMB, filenames that differ only by case may cause conflicts—rename files clearly to avoid sync failures.
+- Windows: Filenames must not end in a space or period (`.`).
+
+## Example
+
+Creating a file named `example.` or `example.LPT1` on macOS may sync to OpenCloud successfully. However, when accessed via a Windows client, these files may be rejected due to reserved naming or format rules, leading to inconsistent sync behavior across devices.
+
+## Summary
+
+| Restriction Type     | Action Item                                      |
+| -------------------- | ------------------------------------------------ |
+| Path Length          | Keep paths under ~260 characters unless extended |
+| Forbidden Characters | Remove disallowed characters from names          |
+| Control Characters   | Avoid non-printable ASCII characters             |
+| Reserved Filenames   | Do not use Windows reserved names                |
+| Case-Only Changes    | Rename to a temporary name before syncing        |
+| Trailing Characters  | Avoid filenames ending in space or period        |
diff --git a/versioned_docs/version-7.x/user/desktop-client/common-functionality/logging.md b/versioned_docs/version-7.x/user/desktop-client/common-functionality/logging.md
new file mode 100644
index 000000000..b3f25cdc4
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/common-functionality/logging.md
@@ -0,0 +1,61 @@
+---
+sidebar_position: 1
+id: logging
+title: Collect Logfiles
+description: Collect logfiles in OpenCloud
+draft: false
+---
+
+# Logging to a Temporary Directory in OpenCloud Desktop
+
+If you need to generate logs for troubleshooting, follow these steps:
+
+## Access Log Settings
+
+- Click on Settings → Advanced → Log Settings
+
+  <img src={require(".././img/logging/logging-access.png").default} alt="Logging access" width="400"/>
+
+## Enable Logging
+
+- In the Log Output window, check the box for Enable logging to temporary folder
+- To help the Support-Team and the developers, it is helpful to enable the Log Http traffic
+
+  <img src={require(".././img/logging/logging-enable.png").default} alt="Enable logging" width="400"/>
+
+## Find the Log Files
+
+- Click Open folder to access the logs.
+
+  <img src={require(".././img/logging/logging-open-folder.png").default} alt="Open logfile folder" width="400"/>
+
+- Select the log files for the time frame when the issue occurred.
+
+  <img src={require(".././img/logging/logging-logfiles.png").default} alt="Logfiles overview" width="400"/>
+
+:::note
+These logs can help diagnose and fix any issues with your OpenCloud Desktop Client.
+:::
+
+### Log Content Description
+
+`25-02-17 09:02:35:174 [ info sync.httplogger ]: REQUEST 3710cc12-7391-4793-8e89-00499dc11983 {"request":{"body":{"length":0},"header":{"accept":"*/*","accept-language":"en_DE","original-request-id":"3710cc12-7391-4793-8e89-00499dc11983","user-agent":"Mozilla/5.0 (Macintosh) mirall/1.0.0-git (OpenCloud, macos-24.3.0 ClientArchitecture: x86_64 OsArchitecture: arm64)","x-request-id":"3710cc12-7391-4793-8e89-00499dc11983"},"info":{"cached":false,"id":"3710cc12-7391-4793-8e89-00499dc11983","method":"GET","url":"https://cloud.opencloud.test/.well-known/openid-configuration"}}}`
+
+| Log Content                          | Description                                       |
+| ------------------------------------ | ------------------------------------------------- |
+| 25-02-17 09:02:35:174                | Timestamp of the request                          |
+| [ info sync.httplogger ]             | Log category label                                |
+| 3710cc12-7391-4793-8e89-00499dc11983 | X-REQUEST-ID (used to match requests & responses) |
+| Header: { }                          | List of HTTP headers                              |
+| Data: []                             | HTTP bodies (JSON, XML)                           |
+| (112ms)                              | Response time (since the request was sent)        |
+
+### Using X-REQUEST-ID for Debugging
+
+- The OpenCloud desktop app sends an X-REQUEST-ID header with every request.
+- This ID helps in finding corresponding requests and responses in logs.
+- You can configure your web server to add the X-REQUEST-ID to its logs for deeper analysis.
+
+:::note
+This feature is useful for debugging sync issues, monitoring network activity, and troubleshooting connectivity problems.
+:::
diff --git a/versioned_docs/version-7.x/user/desktop-client/common-functionality/multiple-accounts.md b/versioned_docs/version-7.x/user/desktop-client/common-functionality/multiple-accounts.md
new file mode 100644
index 000000000..632398794
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/common-functionality/multiple-accounts.md
@@ -0,0 +1,44 @@
+---
+sidebar_position: 2
+id: multiple-accounts
+title: Set up multiple accounts
+description: Using multiple Accounts in OpenCloud Desktop
+draft: false
+---
+
+# Using Multiple Accounts in OpenCloud Desktop
+
+You can synchronize multiple accounts from different OpenCloud servers to your local machine. This allows you to manage files from different instances within the same desktop client.
+
+## How to Add a New Account
+
+- Open OpenCloud Desktop
+- Click on Add Account
+
+  <img src={require(".././img/multiple-accounts/multiple-accounts-add-account.png").default} alt="Add accounts" width="400"/>
+
+- Follow the standard setup process:
+  - Enter the server URL
+  - Log in with your credentials
+  - Authorize access
+
+## Switching Between Accounts
+
+- After adding multiple accounts, they will appear in the account overview in the settings menu
+- You can easily switch between them to manage synchronization settings for each account separately
+
+  <img src={require(".././img/multiple-accounts/multiple-accounts-switch-accounts.png").default} alt="Switch accounts" width="400"/>
+
+## How Files are Stored Locally
+
+- In your File Explorer, each account will have a separate folder
+- By default, the folders are named:
+  - OpenCloud (for the first account)
+  - OpenCloud (2) (for the second account)
+  - OpenCloud (3) (for the third account), and so on
+
+    <img src={require(".././img/multiple-accounts/multiple-accounts-locally.png").default} alt="Multiple accounts in explorer or finder" width="400"/>
+
+:::note
+This setup ensures that files from different accounts remain organized and do not mix.
+:::
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/conflict-files/conflict-file.png b/versioned_docs/version-7.x/user/desktop-client/img/conflict-files/conflict-file.png
new file mode 100644
index 000000000..444ed1d0c
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/conflict-files/conflict-file.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/conflict-files/conflict-info.png b/versioned_docs/version-7.x/user/desktop-client/img/conflict-files/conflict-info.png
new file mode 100644
index 000000000..f2f2de293
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/conflict-files/conflict-info.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_error-petrol-colour.png b/versioned_docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_error-petrol-colour.png
new file mode 100644
index 000000000..d56597ca7
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_error-petrol-colour.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_info-petrol-colour.png b/versioned_docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_info-petrol-colour.png
new file mode 100644
index 000000000..a88ac03e0
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_info-petrol-colour.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_logo-petrol.png b/versioned_docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_logo-petrol.png
new file mode 100644
index 000000000..7e3bb5e64
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_logo-petrol.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_offline-petrol-colour.png b/versioned_docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_offline-petrol-colour.png
new file mode 100644
index 000000000..24f10f8b9
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_offline-petrol-colour.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_pause-petrol-colour.png b/versioned_docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_pause-petrol-colour.png
new file mode 100644
index 000000000..f97c08fe5
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_pause-petrol-colour.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_sync-petrol-colour.png b/versioned_docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_sync-petrol-colour.png
new file mode 100644
index 000000000..90e82d173
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/desktop-client-states/ocl-ui_sync-petrol-colour.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/logging/logging-access.png b/versioned_docs/version-7.x/user/desktop-client/img/logging/logging-access.png
new file mode 100644
index 000000000..a45b44704
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/logging/logging-access.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/logging/logging-enable.png b/versioned_docs/version-7.x/user/desktop-client/img/logging/logging-enable.png
new file mode 100644
index 000000000..f41e2b2ab
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/logging/logging-enable.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/logging/logging-logfiles.png b/versioned_docs/version-7.x/user/desktop-client/img/logging/logging-logfiles.png
new file mode 100644
index 000000000..c1b0cebfb
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/logging/logging-logfiles.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/logging/logging-open-folder.png b/versioned_docs/version-7.x/user/desktop-client/img/logging/logging-open-folder.png
new file mode 100644
index 000000000..0742c5f99
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/logging/logging-open-folder.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/multiple-accounts/multiple-accounts-add-account.png b/versioned_docs/version-7.x/user/desktop-client/img/multiple-accounts/multiple-accounts-add-account.png
new file mode 100644
index 000000000..65eb31f2d
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/multiple-accounts/multiple-accounts-add-account.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/multiple-accounts/multiple-accounts-locally.png b/versioned_docs/version-7.x/user/desktop-client/img/multiple-accounts/multiple-accounts-locally.png
new file mode 100644
index 000000000..9e4ccc9f4
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/multiple-accounts/multiple-accounts-locally.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/multiple-accounts/multiple-accounts-switch-accounts.png b/versioned_docs/version-7.x/user/desktop-client/img/multiple-accounts/multiple-accounts-switch-accounts.png
new file mode 100644
index 000000000..dcaa16fc5
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/multiple-accounts/multiple-accounts-switch-accounts.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/set-up/set-up-accept-access.png b/versioned_docs/version-7.x/user/desktop-client/img/set-up/set-up-accept-access.png
new file mode 100644
index 000000000..b6b51152f
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/set-up/set-up-accept-access.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/set-up/set-up-advanced-configuration.png b/versioned_docs/version-7.x/user/desktop-client/img/set-up/set-up-advanced-configuration.png
new file mode 100644
index 000000000..a8c143c99
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/set-up/set-up-advanced-configuration.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/set-up/set-up-all-set.png b/versioned_docs/version-7.x/user/desktop-client/img/set-up/set-up-all-set.png
new file mode 100644
index 000000000..2588736a6
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/set-up/set-up-all-set.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/set-up/set-up-enter-url.png b/versioned_docs/version-7.x/user/desktop-client/img/set-up/set-up-enter-url.png
new file mode 100644
index 000000000..eafad3ae3
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/set-up/set-up-enter-url.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/set-up/set-up-login.png b/versioned_docs/version-7.x/user/desktop-client/img/set-up/set-up-login.png
new file mode 100644
index 000000000..93b376d87
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/set-up/set-up-login.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/set-up/set-up-user-password.png b/versioned_docs/version-7.x/user/desktop-client/img/set-up/set-up-user-password.png
new file mode 100644
index 000000000..eb083e75c
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/set-up/set-up-user-password.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/set-up/windows/set-up-advanced-configuration.png b/versioned_docs/version-7.x/user/desktop-client/img/set-up/windows/set-up-advanced-configuration.png
new file mode 100644
index 000000000..d8c0558d7
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/set-up/windows/set-up-advanced-configuration.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/set-up/windows/set-up-all-set.png b/versioned_docs/version-7.x/user/desktop-client/img/set-up/windows/set-up-all-set.png
new file mode 100644
index 000000000..771ed3337
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/set-up/windows/set-up-all-set.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/settings/settings-advanced.png b/versioned_docs/version-7.x/user/desktop-client/img/settings/settings-advanced.png
new file mode 100644
index 000000000..abaca05fe
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/settings/settings-advanced.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/settings/settings-bandwidth.png b/versioned_docs/version-7.x/user/desktop-client/img/settings/settings-bandwidth.png
new file mode 100644
index 000000000..1cbf04e74
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/settings/settings-bandwidth.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/settings/settings-general.png b/versioned_docs/version-7.x/user/desktop-client/img/settings/settings-general.png
new file mode 100644
index 000000000..633ee0c3a
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/settings/settings-general.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/settings/settings-network.png b/versioned_docs/version-7.x/user/desktop-client/img/settings/settings-network.png
new file mode 100644
index 000000000..d41a73b50
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/settings/settings-network.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/settings/settings-overview.png b/versioned_docs/version-7.x/user/desktop-client/img/settings/settings-overview.png
new file mode 100644
index 000000000..0962cf7e4
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/settings/settings-overview.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/settings/windows/settings-general.png b/versioned_docs/version-7.x/user/desktop-client/img/settings/windows/settings-general.png
new file mode 100644
index 000000000..ecd1f8b3d
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/settings/windows/settings-general.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/sync-settings/sync-settings-choose-what-to-sync.png b/versioned_docs/version-7.x/user/desktop-client/img/sync-settings/sync-settings-choose-what-to-sync.png
new file mode 100644
index 000000000..9ee467e0e
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/sync-settings/sync-settings-choose-what-to-sync.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/sync-settings/sync-settings-menu.png b/versioned_docs/version-7.x/user/desktop-client/img/sync-settings/sync-settings-menu.png
new file mode 100644
index 000000000..ffeef30f2
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/sync-settings/sync-settings-menu.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/sync-settings/sync-settings-three-dot.png b/versioned_docs/version-7.x/user/desktop-client/img/sync-settings/sync-settings-three-dot.png
new file mode 100644
index 000000000..3770e9fd7
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/sync-settings/sync-settings-three-dot.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/vfs/always-keep-on-this-device.png b/versioned_docs/version-7.x/user/desktop-client/img/vfs/always-keep-on-this-device.png
new file mode 100644
index 000000000..becd2b170
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/vfs/always-keep-on-this-device.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/vfs/free-up-space.png b/versioned_docs/version-7.x/user/desktop-client/img/vfs/free-up-space.png
new file mode 100644
index 000000000..6cf327835
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/vfs/free-up-space.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/vfs/full-pinned.png b/versioned_docs/version-7.x/user/desktop-client/img/vfs/full-pinned.png
new file mode 100644
index 000000000..398b77906
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/vfs/full-pinned.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/vfs/full.png b/versioned_docs/version-7.x/user/desktop-client/img/vfs/full.png
new file mode 100644
index 000000000..2bca9d9ad
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/vfs/full.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/img/vfs/placeholder.png b/versioned_docs/version-7.x/user/desktop-client/img/vfs/placeholder.png
new file mode 100644
index 000000000..c3db85f28
Binary files /dev/null and b/versioned_docs/version-7.x/user/desktop-client/img/vfs/placeholder.png differ
diff --git a/versioned_docs/version-7.x/user/desktop-client/index.md b/versioned_docs/version-7.x/user/desktop-client/index.md
new file mode 100644
index 000000000..a181831d2
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/index.md
@@ -0,0 +1,23 @@
+---
+sidebar_position: 0
+id: desktop-client-overview
+title: OpenCloud Desktop Client
+---
+
+# OpenCloud Desktop Client
+
+The OpenCloud Desktop Client synchronizes files between your computer and OpenCloud. It is available for Windows, macOS, and Linux and provides offline access, automatic synchronization, and a consistent way to work with files locally.
+
+## In this section
+
+- [Windows](./windows/installation.md)  
+  Install, set up, and configure the Desktop Client on Windows.
+
+- [macOS](./macos/installation.md)  
+  Install, set up, and configure the Desktop Client on macOS.
+
+- [Linux](./linux/installation.md)  
+  Install, set up, and configure the Desktop Client on Linux.
+
+- [Common functionality](./common-functionality/multiple-accounts.md)  
+  Learn about shared features such as multiple accounts, file naming rules, conflict handling, and logging.
diff --git a/versioned_docs/version-7.x/user/desktop-client/linux/_category_.json b/versioned_docs/version-7.x/user/desktop-client/linux/_category_.json
new file mode 100644
index 000000000..c87324d0d
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/linux/_category_.json
@@ -0,0 +1,9 @@
+{
+  "label": "Desktop Client for Linux",
+  "position": 3,
+  "link": {
+    "type": "generated-index",
+    "description": "OpenCloud Desktop Client for Linux.",
+    "slug": "user/desktop/linux/"
+  }
+}
diff --git a/versioned_docs/version-7.x/user/desktop-client/linux/installation.md b/versioned_docs/version-7.x/user/desktop-client/linux/installation.md
new file mode 100644
index 000000000..267ab574c
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/linux/installation.md
@@ -0,0 +1,67 @@
+---
+sidebar_position: 1
+id: installation
+title: Installation
+description: Install OpenCloud Desktop Client on Linux
+draft: false
+---
+
+# Installation on Linux (AppImage with AppImageLauncher)
+
+The OpenCloud Desktop Client is available as an AppImage for Linux.  
+Using AppImageLauncher is recommended to ensure proper system integration, menu entries, and simplified updates.
+
+## Install AppImageLauncher
+
+AppImageLauncher integrates AppImages into your system and manages them like regular applications.
+
+Follow the installation instructions here:
+
+[AppImageLauncher Installation Guide](https://github.com/TheAssassin/AppImageLauncher/releases/tag/v3.0.0-beta-3)
+
+## Download the OpenCloud AppImage
+
+Download the latest or desired `.AppImage` version from the official release page:
+
+- [OpenCloud Desktop Releases on GitHub](https://github.com/opencloud-eu/desktop/releases)
+
+Save the file to your preferred download directory.
+
+## Integrate the AppImage
+
+Once AppImageLauncher is installed:
+
+1. Right-click the downloaded `OpenCloud.AppImage`.
+2. Select “Open with AppImageLauncher”.
+3. Confirm integration when prompted.
+
+AppImageLauncher will automatically:
+
+- store the AppImage in the correct location
+- register a menu entry
+- ensure the app behaves like a native application
+
+## Launching OpenCloud Desktop
+
+After integration, you can start the client as usual through your application menu:
+
+- open your Application Launcher
+- search for OpenCloud Desktop
+- start the application
+
+The client will guide you through the initial setup.
+
+## Updating the AppImage
+
+When a new version is available, download the updated AppImage from GitHub.  
+AppImageLauncher will detect it and offer to replace the existing version automatically.
+
+## Uninstallation
+
+To remove the OpenCloud Desktop Client:
+
+1. Open your application menu.
+2. Search for OpenCloud Desktop
+3. Select the option to remove or uninstall the AppImage (menu wording may vary depending on distribution and launcher).
+
+AppImageLauncher will cleanly remove the integrated AppImage.
diff --git a/versioned_docs/version-7.x/user/desktop-client/linux/set-up.md b/versioned_docs/version-7.x/user/desktop-client/linux/set-up.md
new file mode 100644
index 000000000..35fd86524
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/linux/set-up.md
@@ -0,0 +1,55 @@
+---
+sidebar_position: 2
+id: set-up
+title: Set up OpenCloud Desktop
+description: Setting up your OpenCloud Desktop
+draft: false
+---
+
+# Setting Up Your OpenCloud Desktop
+
+Follow these simple steps to install and configure your OpenCloud Desktop and start syncing your files effortlessly.
+
+## Enter the Server URL
+
+- Open your OpenCloud Desktop
+- Enter the URL of your OpenCloud instance
+- Click "Continue"
+
+  <img src={require(".././img/set-up/set-up-enter-url.png").default} alt="Enter URL" width="400"/>
+
+## Log In via Web Browser
+
+- Click "Open web browser" to log in automatically
+- Alternatively, copy the provided URL and paste it into your browser manually
+
+  <img src={require(".././img/set-up/set-up-login.png").default} alt="Open browser to login" width="400"/>
+
+## Enter Your Credentials
+
+- Enter your username and password
+- Click "Login"
+
+  <img src={require(".././img/set-up/set-up-user-password.png").default} alt="Enter credentials" width="400"/>
+
+## Grant Access
+
+- Accept the access request to link your account with OpenCloud Desktop.
+
+  <img src={require(".././img/set-up/set-up-accept-access.png").default} alt="Grand access" width="400"/>
+
+## Finalize Setup
+
+## Optional Advanced Configuration
+
+- Choose whether to sync all files or select specific folders (this can be adjusted later).
+- Change the local download directory where your files will be stored.
+
+  <img src={require(".././img/set-up/set-up-advanced-configuration.png").default} alt="Finalize setup" width="400"/>
+
+Once you're ready, click Done to complete the setup.
+
+<img src={require(".././img/set-up/set-up-all-set.png").default} alt="All set" width="400"/>
+
+OpenCloud Desktop is now successfully set up.  
+You can start syncing your files seamlessly between your device and the OpenCloud server!
diff --git a/versioned_docs/version-7.x/user/desktop-client/linux/settings.md b/versioned_docs/version-7.x/user/desktop-client/linux/settings.md
new file mode 100644
index 000000000..4f96daf34
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/linux/settings.md
@@ -0,0 +1,54 @@
+---
+sidebar_position: 3
+id: settings
+title: Settings in Linux
+description: Settings in OpenCloud Desktop for Linux
+draft: false
+---
+
+# Change Settings in OpenCloud Desktop
+
+You can customize OpenCloud Desktop settings by following these steps:
+
+## Open Settings
+
+- Click on "Settings" in the top-right corner of OpenCloud Desktop
+
+  <img src={require(".././img/settings/settings-overview.png").default} alt="Settings overview" width="400"/>
+
+## Overview of Settings Sections
+
+### General Settings
+
+- Enable or disable auto-start when log in
+- Choose whether to show desktop notifications
+- Set your preferred language
+
+  <img src={require(".././img/settings/settings-general.png").default} alt="Settings-general" width="400"/>
+
+### Advanced Settings
+
+- Choose to sync hidden files
+- Decide whether deleted files should be moved to the local trash bin
+- Edit the ignored files list
+- Enable a debug log file for troubleshooting
+
+  <img src={require(".././img/settings/settings-advanced.png").default} alt="Settings advanced" width="400"/>
+
+### Network Settings
+
+- Select how the client handles proxy settings:
+  - No proxy
+  - Use system proxy (default)
+  - Manually enter a proxy
+
+  <img src={require(".././img/settings/settings-network.png").default} alt="Settings network" width="400"/>
+
+### Download and Upload Bandwidth
+
+- Set bandwidth limits:
+  - No limit (default)
+  - Automatically adjust limit
+  - Set a specific limit manually
+
+  <img src={require(".././img/settings/settings-bandwidth.png").default} alt="Settings bandwidth" width="400"/>
diff --git a/versioned_docs/version-7.x/user/desktop-client/linux/sync-settings.md b/versioned_docs/version-7.x/user/desktop-client/linux/sync-settings.md
new file mode 100644
index 000000000..6c224fcbb
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/linux/sync-settings.md
@@ -0,0 +1,57 @@
+---
+sidebar_position: 3
+id: sync-settings-linux
+title: Synchronization Settings on Linux
+description: Synchronisation Settings on Linux
+draft: false
+---
+
+# Linux: Synchronization Settings
+
+On Linux, files are downloaded to your system. You can configure what to sync and how often through the OpenCloud Desktop Client.
+
+## Access Synchronization Settings
+
+1. Open the OpenCloud Desktop Client.
+2. Go to the Account View.
+3. Click the three-dot menu (...) next to the Space you want to configure.
+
+<img src={require(".././img/sync-settings/sync-settings-three-dot.png").default} alt="Account spaces menu" width="400"/>
+
+## Synchronization Options
+
+<img src={require(".././img/sync-settings/sync-settings-menu.png").default} alt="Choose what to sync" width="400"/>
+
+### Show in Linux file manager
+
+- Opens the Space in your Linux desktop environment file manager.
+
+### Show in Web Browser
+
+- Opens the Space in your web browser.
+- You may need to sign in if not already logged in.
+
+### Force Sync Now
+
+- Manually triggers an immediate synchronization.
+
+### Pause Sync
+
+- Temporarily stops synchronization.
+- Resume anytime via **Resume Sync**.
+
+### Remove Sync Folder Connection
+
+- Stops syncing the Space but does not delete local files.
+- The Space remains on the server.
+
+### Choose What to Sync
+
+- Select specific folders to sync locally.
+- Helps save disk space by keeping only necessary files synced.
+
+<img src={require(".././img/sync-settings/sync-settings-choose-what-to-sync.png").default} alt="Choose what to sync" width="400"/>
+
+:::note
+Files and folders not selected for sync will not be available locally.
+:::
diff --git a/versioned_docs/version-7.x/user/desktop-client/linux/upgrade.md b/versioned_docs/version-7.x/user/desktop-client/linux/upgrade.md
new file mode 100644
index 000000000..3b422eb52
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/linux/upgrade.md
@@ -0,0 +1,72 @@
+---
+sidebar_position: 5
+id: upgrade-linux
+title: Upgrade Desktop Client on Linux
+description: Upgrade Desktop Client on Linux
+draft: false
+---
+
+# Upgrade Desktop Client on Linux
+
+The OpenCloud Desktop Client for Linux is provided as an AppImage.
+
+If you installed OpenCloud Desktop with AppImageLauncher, the client can be upgraded by downloading the updated AppImage and replacing the existing integrated version.
+
+Existing accounts, synchronization settings, preferences, cached data, and credentials are preserved during the upgrade.
+
+## Download the Latest AppImage
+
+Download the latest `.AppImage` file from the official release page:
+
+- [OpenCloud Desktop Releases on GitHub](https://github.com/opencloud-eu/desktop/releases)
+
+Choose the AppImage that matches your system architecture and save it to your Downloads folder or another location where you can easily find it.
+
+## Close OpenCloud Desktop
+
+Before starting the upgrade, close the running Desktop Client:
+
+1. Open the OpenCloud Desktop menu.
+2. Stop active synchronization if necessary.
+3. Select Quit OpenCloud Desktop.
+
+This ensures that all synchronization processes are stopped cleanly before the upgrade.
+
+## Replace the Existing AppImage
+
+To upgrade OpenCloud Desktop with AppImageLauncher:
+
+1. Right-click the downloaded `.AppImage` file.
+2. Select Open with AppImageLauncher.
+3. Confirm that the existing integrated version should be replaced when prompted.
+
+AppImageLauncher replaces the existing AppImage and keeps the application menu entry available.
+
+## Launch the Updated Application
+
+After the upgrade has completed, start OpenCloud Desktop from your application menu:
+
+1. Open your application launcher.
+2. Search for OpenCloud Desktop.
+3. Start the application.
+
+The client should start normally and use your existing configuration.
+
+## Verify the Installed Version
+
+To confirm that the upgrade was successful:
+
+1. Open OpenCloud Desktop.
+2. Open the settings.
+3. Select About.
+4. Check the displayed version number.
+
+The currently installed version number is displayed in the about dialog.
+
+:::note
+Upgrading does not remove synchronized files.
+
+Existing user accounts and sync connections remain configured.
+
+A system restart is usually not required after upgrading.
+:::
diff --git a/versioned_docs/version-7.x/user/desktop-client/macos/_category_.json b/versioned_docs/version-7.x/user/desktop-client/macos/_category_.json
new file mode 100644
index 000000000..a22ed06b4
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/macos/_category_.json
@@ -0,0 +1,9 @@
+{
+  "label": "Desktop Client for MacOS",
+  "position": 2,
+  "link": {
+    "type": "generated-index",
+    "description": "OpenCloud Desktop Client for MacOS.",
+    "slug": "user/desktop/macos/"
+  }
+}
diff --git a/versioned_docs/version-7.x/user/desktop-client/macos/installation.md b/versioned_docs/version-7.x/user/desktop-client/macos/installation.md
new file mode 100644
index 000000000..1f431edac
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/macos/installation.md
@@ -0,0 +1,63 @@
+---
+sidebar_position: 1
+id: installation
+title: Installation
+description: Install OpenCloud Client
+draft: false
+---
+
+# Installation on macOS (.pkg file)
+
+The OpenCloud Desktop Client is provided as a signed `.pkg` installer for macOS.  
+This installation method integrates cleanly into the system and follows the standard macOS installation process.
+
+## Download the Installer
+
+Download the latest or preferred `.pkg` file from the official release page:
+
+- [OpenCloud Desktop Releases on GitHub](https://github.com/opencloud-eu/desktop/releases)
+
+Save the file to your Downloads folder.
+
+## Run the Installer
+
+1. Double-click the downloaded `.pkg` file.
+2. The macOS installer will open automatically.
+3. Follow the on-screen steps to complete the installation.
+
+The installer places OpenCloud Desktop in the system’s Applications directory.
+
+## Launch the Application
+
+After installation, you can start OpenCloud Desktop from:
+
+- the Applications folder
+- Launchpad
+- or by using Spotlight (press `Cmd + Space` and search for “OpenCloud Desktop”)
+
+## First Start
+
+On first launch, the client will guide you through:
+
+- signing in with your OpenCloud account
+- selecting sync settings
+- configuring basic preferences
+
+The application is now ready to use on macOS.
+
+## Uninstallation
+
+To remove the OpenCloud Desktop Client from your system:
+
+1. Open the Applications folder.
+2. Locate OpenCloud Desktop.app.
+3. Drag the application to the Trash or right-click and select Move to Trash.
+4. Empty the Trash to complete the removal.
+
+Optional configuration files may remain in the user directory:
+
+- `~/Library/Application Support/OpenCloud/`
+- `~/Library/Preferences/eu.opencloud.desktop.plist`
+- `~/Library/Logs/OpenCloud/`
+
+These files can be deleted manually if a full cleanup is desired.
diff --git a/versioned_docs/version-7.x/user/desktop-client/macos/set-up.md b/versioned_docs/version-7.x/user/desktop-client/macos/set-up.md
new file mode 100644
index 000000000..35fd86524
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/macos/set-up.md
@@ -0,0 +1,55 @@
+---
+sidebar_position: 2
+id: set-up
+title: Set up OpenCloud Desktop
+description: Setting up your OpenCloud Desktop
+draft: false
+---
+
+# Setting Up Your OpenCloud Desktop
+
+Follow these simple steps to install and configure your OpenCloud Desktop and start syncing your files effortlessly.
+
+## Enter the Server URL
+
+- Open your OpenCloud Desktop
+- Enter the URL of your OpenCloud instance
+- Click "Continue"
+
+  <img src={require(".././img/set-up/set-up-enter-url.png").default} alt="Enter URL" width="400"/>
+
+## Log In via Web Browser
+
+- Click "Open web browser" to log in automatically
+- Alternatively, copy the provided URL and paste it into your browser manually
+
+  <img src={require(".././img/set-up/set-up-login.png").default} alt="Open browser to login" width="400"/>
+
+## Enter Your Credentials
+
+- Enter your username and password
+- Click "Login"
+
+  <img src={require(".././img/set-up/set-up-user-password.png").default} alt="Enter credentials" width="400"/>
+
+## Grant Access
+
+- Accept the access request to link your account with OpenCloud Desktop.
+
+  <img src={require(".././img/set-up/set-up-accept-access.png").default} alt="Grand access" width="400"/>
+
+## Finalize Setup
+
+## Optional Advanced Configuration
+
+- Choose whether to sync all files or select specific folders (this can be adjusted later).
+- Change the local download directory where your files will be stored.
+
+  <img src={require(".././img/set-up/set-up-advanced-configuration.png").default} alt="Finalize setup" width="400"/>
+
+Once you're ready, click Done to complete the setup.
+
+<img src={require(".././img/set-up/set-up-all-set.png").default} alt="All set" width="400"/>
+
+OpenCloud Desktop is now successfully set up.  
+You can start syncing your files seamlessly between your device and the OpenCloud server!
diff --git a/versioned_docs/version-7.x/user/desktop-client/macos/settings.md b/versioned_docs/version-7.x/user/desktop-client/macos/settings.md
new file mode 100644
index 000000000..3df805781
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/macos/settings.md
@@ -0,0 +1,53 @@
+---
+sidebar_position: 3
+id: settings
+title: Settings for macOS
+description: Settings in OpenCloud Desktop for macOS
+draft: false
+---
+
+# Change Settings in OpenCloud Desktop
+
+You can customize OpenCloud Desktop settings by following these steps:
+
+## Open Settings
+
+- Click on "Settings" in the top-right corner of OpenCloud Desktop
+
+  <img src={require(".././img/settings/settings-overview.png").default} alt="Settings overview" width="400"/>
+
+## Overview of Settings Sections
+
+### General Settings
+
+- Enable or disable auto-start when log in
+- Set your preferred language
+
+  <img src={require(".././img/settings/settings-general.png").default} alt="Settings-general" width="400"/>
+
+### Advanced Settings
+
+- Choose to sync hidden files
+- Decide whether deleted files should be moved to the local trash bin
+- Edit the ignored files list
+- Enable a debug log file for troubleshooting
+
+  <img src={require(".././img/settings/settings-advanced.png").default} alt="Settings advanced" width="400"/>
+
+### Network Settings
+
+- Select how the client handles proxy settings:
+  - No proxy
+  - Use system proxy (default)
+  - Manually enter a proxy
+
+  <img src={require(".././img/settings/settings-network.png").default} alt="Settings network" width="400"/>
+
+### Download and Upload Bandwidth
+
+- Set bandwidth limits:
+  - No limit (default)
+  - Automatically adjust limit
+  - Set a specific limit manually
+
+  <img src={require(".././img/settings/settings-bandwidth.png").default} alt="Settings bandwidth" width="400"/>
diff --git a/versioned_docs/version-7.x/user/desktop-client/macos/sync-settings.md b/versioned_docs/version-7.x/user/desktop-client/macos/sync-settings.md
new file mode 100644
index 000000000..f4255bcea
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/macos/sync-settings.md
@@ -0,0 +1,57 @@
+---
+sidebar_position: 3
+id: sync-settings-mac
+title: Synchronization Settings in macOS
+description: Synchronisation Settings in macOS
+draft: false
+---
+
+# macOS: Synchronization Settings
+
+On macOS, files are downloaded to your system. You can configure what to sync and how often through the OpenCloud Desktop Client.
+
+## Access Synchronization Settings
+
+1. Open the OpenCloud Desktop Client.
+2. Go to the Account View.
+3. Click the three-dot menu (...) next to the Space you want to configure.
+
+<img src={require(".././img/sync-settings/sync-settings-three-dot.png").default} alt="Account spaces menu" width="400"/>
+
+## Synchronization Options
+
+<img src={require(".././img/sync-settings/sync-settings-menu.png").default} alt="Choose what to sync" width="400"/>
+
+### Show in Finder
+
+- Opens the Space in Finder.
+
+### Show in Web Browser
+
+- Opens the Space in your web browser.
+- You may need to sign in if not already logged in.
+
+### Force Sync Now
+
+- Manually triggers an immediate synchronization.
+
+### Pause Sync
+
+- Temporarily stops synchronization.
+- Resume anytime via **Resume Sync**.
+
+### Remove Sync Folder Connection
+
+- Stops syncing the Space but does not delete local files.
+- The Space remains on the server.
+
+### Choose What to Sync
+
+- Select specific folders to sync locally.
+- Helps save disk space by keeping only necessary files synced.
+
+<img src={require(".././img/sync-settings/sync-settings-choose-what-to-sync.png").default} alt="Choose what to sync" width="400"/>
+
+:::note
+Files and folders not selected for sync will not be available locally.
+:::
diff --git a/versioned_docs/version-7.x/user/desktop-client/macos/upgrade.md b/versioned_docs/version-7.x/user/desktop-client/macos/upgrade.md
new file mode 100644
index 000000000..ab2b833c0
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/macos/upgrade.md
@@ -0,0 +1,76 @@
+---
+sidebar_position: 4
+id: upgrade-macos
+title: Upgrade Desktop Client on macOS
+description: Upgrade Desktop Client on macOS
+draft: false
+---
+
+# Upgrade Desktop Client on macOS
+
+The OpenCloud Desktop Client for macOS can be upgraded using the official signed `.pkg` installer.
+
+The upgrade replaces the existing application while preserving your account settings, synchronization configuration, preferences, cached data, and credentials.
+
+## Download the Latest Installer
+
+Download the latest `.pkg` installer from the official release page:
+
+- [OpenCloud Desktop Releases on GitHub](https://github.com/opencloud-eu/desktop/releases)
+
+Choose the installer that matches your Mac architecture:
+
+- Apple Silicon Macs (M1, M2, M3): `arm64`
+- Intel Macs: `x86_64`
+
+Save the installer to your Downloads folder or another location where you can easily find it.
+
+## Close OpenCloud Desktop
+
+Before starting the upgrade, close the running Desktop Client:
+
+1. Click the OpenCloud Desktop icon in the macOS menu bar.
+2. Open the menu.
+3. Select Quit OpenCloud Desktop.
+
+This ensures that all synchronization processes are stopped cleanly before the upgrade.
+
+## Run the Installer
+
+To upgrade OpenCloud Desktop:
+
+1. Double-click the downloaded `.pkg` file.
+2. Follow the instructions in the macOS installer.
+3. When prompted, confirm that the existing installation should be replaced.
+
+The installer updates the application in the Applications folder.
+
+Existing accounts, synchronization folders, preferences, cached data, and credentials are preserved automatically.
+
+## Launch the Updated Application
+
+After the installation has completed, launch OpenCloud Desktop from one of the following locations:
+
+- Applications folder
+- Launchpad
+- Spotlight
+
+The client should start normally and use your existing configuration.
+
+## Verify the Installed Version
+
+To confirm that the upgrade was successful:
+
+1. Open OpenCloud Desktop.
+2. Open the settings.
+3. Select About and check the version.
+
+The currently installed version number is displayed in the about dialog.
+
+:::note
+Upgrading does not remove synchronized files.
+
+Existing user accounts and sync connections remain configured.
+
+A system restart is usually not required after upgrading.
+:::
diff --git a/versioned_docs/version-7.x/user/desktop-client/windows/_category_.json b/versioned_docs/version-7.x/user/desktop-client/windows/_category_.json
new file mode 100644
index 000000000..bb743e300
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/windows/_category_.json
@@ -0,0 +1,9 @@
+{
+  "label": "Desktop Client for Windows",
+  "position": 1,
+  "link": {
+    "type": "generated-index",
+    "description": "OpenCloud Desktop Client for Windows.",
+    "slug": "user/desktop/windows/"
+  }
+}
diff --git a/versioned_docs/version-7.x/user/desktop-client/windows/installation.md b/versioned_docs/version-7.x/user/desktop-client/windows/installation.md
new file mode 100644
index 000000000..613206f1e
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/windows/installation.md
@@ -0,0 +1,56 @@
+---
+sidebar_position: 1
+id: installation
+title: Installation
+description: Install OpenCloud Client
+draft: false
+---
+
+# Installation on Windows
+
+The OpenCloud Desktop Clientfor Windows is available through the Microsoft Store. Using the Store ensures a simple installation process, automatic updates, and seamless integration with Windows.
+
+## Open the Microsoft Store
+
+Open the Microsoft Store on your Windows device and search for OpenCloud Desktop,  
+or click the button below to go directly to the app page:
+
+<a href="https://apps.microsoft.com/detail/9pbx43hcmldq?mode=direct">
+  <img alt="Download from Microsoft Store" src="https://get.microsoft.com/images/en-us%20dark.svg" width="200"/>
+</a>
+
+## Click “Install”
+
+On the app page, select Install to download and install the OpenCloud Desktop Client.
+
+The Microsoft Store will handle the installation automatically and place the application in the appropriate location on your system.
+
+## Start the Application
+
+Once the installation is complete, launch the client by opening the Start Menu and searching for OpenCloud Desktop.  
+The application will guide you through the initial setup, including signing in with your account.
+
+## Automatic Updates
+
+The Microsoft Store keeps the OpenCloud Desktop Client up to date.  
+Updates are installed automatically in the background and require no manual steps.
+
+This ensures:
+
+- the latest features are always available
+- security improvements are applied promptly
+- full compatibility with current Windows versions
+
+:::note
+Installing from the Microsoft Store ensures automatic updates, improved system integration, and reduces the need for manual maintenance.
+:::
+
+## Uninstallation (optional)
+
+If you ever need to uninstall the client:
+
+1. Open the Start Menu.
+2. Search for OpenCloud Desktop.
+3. Right-click the application and select Uninstall.
+
+Windows will remove the client and its components cleanly through the Microsoft Store framework.
diff --git a/versioned_docs/version-7.x/user/desktop-client/windows/set-up.md b/versioned_docs/version-7.x/user/desktop-client/windows/set-up.md
new file mode 100644
index 000000000..35a2d64f8
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/windows/set-up.md
@@ -0,0 +1,55 @@
+---
+sidebar_position: 2
+id: set-up
+title: Set up OpenCloud Desktop
+description: Setting up your OpenCloud Desktop
+draft: false
+---
+
+# Setting Up Your OpenCloud Desktop
+
+Follow these simple steps to install and configure your OpenCloud Desktop and start syncing your files effortlessly.
+
+## Enter the Server URL
+
+- Open your OpenCloud Desktop
+- Enter the URL of your OpenCloud instance
+- Click "Continue"
+
+  <img src={require(".././img/set-up/set-up-enter-url.png").default} alt="Enter URL" width="400"/>
+
+## Log In via Web Browser
+
+- Click "Open web browser" to log in automatically
+- Alternatively, copy the provided URL and paste it into your browser manually
+
+  <img src={require(".././img/set-up/set-up-login.png").default} alt="Open browser to login" width="400"/>
+
+## Enter Your Credentials
+
+- Enter your username and password
+- Click "Login"
+
+  <img src={require(".././img/set-up/set-up-user-password.png").default} alt="Enter credentials" width="400"/>
+
+## Grant Access
+
+- Accept the access request to link your account with OpenCloud Desktop.
+
+  <img src={require(".././img/set-up/set-up-accept-access.png").default} alt="Grand access" width="400"/>
+
+## Finalize Setup
+
+## Optional Advanced Configuration
+
+- Choose whether all existing Spaces should be synchronized or should the synchronization be configured manually.
+- Change the local download directory where your files will be stored.
+
+  <img src={require(".././img/set-up/windows/set-up-advanced-configuration.png").default} alt="Finalize setup" width="400"/>
+
+Once you're ready, click Done to complete the setup.
+
+<img src={require(".././img/set-up/windows/set-up-all-set.png").default} alt="All set" width="400"/>
+
+OpenCloud Desktop is now successfully set up.  
+You can start syncing your files seamlessly between your device and the OpenCloud server!
diff --git a/versioned_docs/version-7.x/user/desktop-client/windows/settings.md b/versioned_docs/version-7.x/user/desktop-client/windows/settings.md
new file mode 100644
index 000000000..4350bca20
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/windows/settings.md
@@ -0,0 +1,52 @@
+---
+sidebar_position: 3
+id: settings
+title: Settings in Windows
+description: Settings in OpenCloud Desktop for Windows
+draft: false
+---
+
+# Change Settings in OpenCloud Desktop
+
+You can customize OpenCloud Desktop settings by following these steps:
+
+## Open Settings
+
+- Click on "Settings" in the top-right corner of OpenCloud Desktop
+
+  <img src={require(".././img/settings/settings-overview.png").default} alt="Settings overview" width="400"/>
+
+## Overview of Settings Sections
+
+### General Settings
+
+- Set your preferred language
+
+  <img src={require(".././img/settings/windows/settings-general.png").default} alt="Settings-general" width="400"/>
+
+### Advanced Settings
+
+- Choose to sync hidden files
+- Decide whether deleted files should be moved to the local trash bin
+- Edit the ignored files list
+- Enable a debug log file for troubleshooting
+
+  <img src={require(".././img/settings/settings-advanced.png").default} alt="Settings advanced" width="400"/>
+
+### Network Settings
+
+- Select how the client handles proxy settings:
+  - No proxy
+  - Use system proxy (default)
+  - Manually enter a proxy
+
+  <img src={require(".././img/settings/settings-network.png").default} alt="Settings network" width="400"/>
+
+### Download and Upload Bandwidth
+
+- Set bandwidth limits:
+  - No limit (default)
+  - Automatically adjust limit
+  - Set a specific limit manually
+
+  <img src={require(".././img/settings/settings-bandwidth.png").default} alt="Settings bandwidth" width="400"/>
diff --git a/versioned_docs/version-7.x/user/desktop-client/windows/sync-settings.md b/versioned_docs/version-7.x/user/desktop-client/windows/sync-settings.md
new file mode 100644
index 000000000..28294201a
--- /dev/null
+++ b/versioned_docs/version-7.x/user/desktop-client/windows/sync-settings.md
@@ -0,0 +1,65 @@
+---
+sidebar_position: 4
+id: sync-settings-win
+title: Synchronisation Settings in Windows
+description: Synchronisation Settings in Windows
+draft: false
+---
+
+# Windows: Synchronization Settings
+
+The OpenCloud Desktop Client uses the Windows Virtual File System (VFS) to integrate your cloud data directly into the File Explorer.  
+Files and folders appear in the system without needing to be fully downloaded, saving local disk space.
+
+## File States
+
+Files and folders can appear in different states, depending on whether they are stored locally or only available online.
+
+### Always available on this device (full pinned)
+
+- Stored locally and always accessible offline.
+- Windows will not remove the file automatically.
+
+<img src={require(".././img/vfs/full-pinned.png").default} alt="full pinned file icon" width="400"/>
+
+### Available on this device (full)
+
+- Downloaded and accessible offline.
+- Can be removed by Windows if disk space is needed.
+- Newly created or added files automatically receive this state.
+
+<img src={require(".././img/vfs/full.png").default} alt="full file icon" width="400"/>
+
+### Available when online (placeholder)
+
+- Shown in File Explorer but stored only in the cloud.
+- Downloaded automatically when opened; requires an internet connection.
+
+<img src={require(".././img/vfs/placeholder.png").default} alt="placeholder file icon" width="400"/>
+
+## Making Items Available Offline
+
+To store a file, folder, or Space locally:
+
+1. Right-click the item in File Explorer.
+2. Select “Always keep on this device”.
+
+<img src={require(".././img/vfs/always-keep-on-this-device.png").default} alt="select always keep on this device" width="400"/>
+
+## Freeing Up Disk Space
+
+To remove local copies while keeping them visible in File Explorer:
+
+1. Right-click the item.
+2. Select “Free up space”.
+
+<img src={require(".././img/vfs/free-up-space.png").default} alt="select free up space" width="400"/>
+
+## Accessing Files
+
+- Online-only items are downloaded automatically when opened.
+- Changes are synced back to OpenCloud.
+
+:::note
+An internet connection is required for online-only files.
+:::
diff --git a/versioned_docs/version-7.x/user/files-and-folders/_category_.json b/versioned_docs/version-7.x/user/files-and-folders/_category_.json
new file mode 100644
index 000000000..5437a6616
--- /dev/null
+++ b/versioned_docs/version-7.x/user/files-and-folders/_category_.json
@@ -0,0 +1,8 @@
+{
+  "label": "Manage Files and Folders",
+  "position": 3,
+  "link": {
+    "type": "doc",
+    "id": "files-and-folders-overview"
+  }
+}
diff --git a/versioned_docs/version-7.x/user/files-and-folders/activity.md b/versioned_docs/version-7.x/user/files-and-folders/activity.md
new file mode 100644
index 000000000..bb88133e8
--- /dev/null
+++ b/versioned_docs/version-7.x/user/files-and-folders/activity.md
@@ -0,0 +1,31 @@
+---
+sidebar_position: 8
+id: activities
+title: Activities
+description: Viewing the activities of a file or folder in OpenCloud
+draft: false
+---
+
+# Viewing the activities of a file or folder
+
+To find out who has edited a file or folder and what actions have been carried out, follow these steps:
+
+## Show activities
+
+- Open details
+  - Right-click on the file or folder, or click on the three dots in the corresponding line.
+  - Select "Details" from the context menu.
+
+    <img src={require("./img/activity/details-button.png").default} alt="Context menu details" width="400"/>
+
+- Select Activities
+  - In the right sidebar opens a window, in this select the “Activities” item.
+    <img src={require("./img/activity/activities-button.png").default} alt="Select activities" width="400"/>
+
+- View activities
+  - All activities carried out with this file or folder are now displayed.
+    <img src={require("./img/activity/activities.png").default} alt="View activities" width="400"/>
+
+:::info
+This allows you to track all changes and actions!
+:::
diff --git a/versioned_docs/version-7.x/user/files-and-folders/create-rename-move.md b/versioned_docs/version-7.x/user/files-and-folders/create-rename-move.md
new file mode 100644
index 000000000..3baef034d
--- /dev/null
+++ b/versioned_docs/version-7.x/user/files-and-folders/create-rename-move.md
@@ -0,0 +1,60 @@
+---
+sidebar_position: 1
+id: create-rename-move
+title: Create - Rename - Move
+description: Create - Rename - Move
+draft: false
+---
+
+# Create - Rename - Move
+
+You can easily create new text, table and presentation files in the web interface. You can also rename files and folders or move them to another location.
+
+## Create files and folders
+
+- Open the “+ New” menu in the left sidebar.
+  <img src={require("./img/create-rename-move/new-button.png").default} alt="New button" width="1920"/>
+- Select either “Folder” or the desired "file type" that you want to create.
+  <img src={require("./img/create-rename-move/create-options.png").default} alt="Select file type or folder" width="400"/>
+- Enter a name for the file or folder in the window that appears.
+- Click on “Create”.
+
+  <img src={require("./img/create-rename-move/create-button.png").default} alt="Click create" width="400"/>
+
+Done! The file or folder is created. If it is a file, it is automatically opened in edit mode.
+
+## Rename files or folders
+
+- Open the context menu by either:
+  - right-clicking on the file or folder
+  - or clicking on the three dots on the right in the corresponding line.
+- Select the “Rename” option.
+  <img src={require("./img/create-rename-move/rename-option.png").default} alt="Select rename" width="400"/>
+- Enter the new name for the file or folder in the window that appears.
+  Confirm by clicking on “Rename”.
+
+  <img src={require("./img/create-rename-move/rename-popup.png").default} alt="Enter new name" width="400"/>
+
+Done! - the new name is applied!
+
+## Move files or folders
+
+- Make a selection:
+  - Select the file(s) or folder(s) you want to move.
+    <img src={require("./img/create-rename-move/mark-folder.png").default} alt="Mark folder or files" width="1920"/>
+  - Open the context menu:
+    - Right-click on the file or folder
+    - or click on the three dots in the corresponding line
+
+  - Select the “Cut” option from the menu.
+    <img src={require("./img/create-rename-move/right-click-cut-option.png").default} alt="Right click on cut option" width="400"/>
+    (Alternatively, you can use the “Cut” function in the action bar at the top).
+    <img src={require("./img/create-rename-move/actionbar-cut-option.png").default} alt="Cut option in action bar" width="1920"/>
+
+- Select destination:
+  - Navigate to the folder or location where the file or folder should be moved to.
+  - Click on “Paste here” in the action bar.
+    <img src={require("./img/create-rename-move/paste-here-button.png").default} alt="Paste here button" width="1920"/>
+    <img src={require("./img/create-rename-move/pasted-file.png").default} alt="Paste file" width="1920"/>
+
+The file or folder is now moved to the new location and no longer exists in the original location.
diff --git a/versioned_docs/version-7.x/user/files-and-folders/delete-restore.md b/versioned_docs/version-7.x/user/files-and-folders/delete-restore.md
new file mode 100644
index 000000000..35aa8ee04
--- /dev/null
+++ b/versioned_docs/version-7.x/user/files-and-folders/delete-restore.md
@@ -0,0 +1,51 @@
+---
+sidebar_position: 3
+id: delete-restore
+title: Delete - Restore
+description: Delete - Restore
+draft: false
+---
+
+# Delete - Restore
+
+## Delete files or folders
+
+- Select the file(s) or folder(s) you wish to delete.
+
+  <img src={require("./img/delete-restore/mark-folder.png").default} alt="Mark folder or file" width="1920"/>
+
+- Open the context menu and select "Delete".
+
+  <img src={require("./img/delete-restore/delete-options.png").default} alt="Click delete" width="1920"/>
+
+:::info
+Alternatively, you can also click on “Delete” in the action bar.
+:::
+
+- The files or folders are moved to the “Deleted files” area. They can be restored from there if necessary.
+
+  <img src={require("./img/delete-restore/folder-in-deleted-files.png").default} alt="Removed files and folders in deleted files" width="1920"/>
+
+## Restore files or folders
+
+- Click “Deleted files” in the left sidebar.
+- Files from your personal space can be found under “Personal”.
+- Files from other spaces, such as “Platform Team”, can be found in their respective spaces.
+
+  <img src={require("./img/delete-restore/structure-in-deleted-files.png").default} alt="Structure in deleted files" width="1920"/>
+
+- Click on the file(s) or folder(s) you want to restore.
+
+  <img src={require("./img/delete-restore/mark-folder-in-deleted-files.png").default} alt="Mark what should be restored" width="1920"/>
+
+- Right-click the selection or click the three dots next to it, then choose "Restore".
+
+  <img src={require("./img/delete-restore/three-dot-menu-in-deleted-files.png").default} alt="Three dot menu" width="1920"/>
+
+:::info
+Alternatively, you can also click on “Restore” in the action bar.
+:::
+
+:::note
+The files or folders are restored to their original location.
+:::
diff --git a/versioned_docs/version-7.x/user/files-and-folders/favorites.md b/versioned_docs/version-7.x/user/files-and-folders/favorites.md
new file mode 100644
index 000000000..58f7e0bae
--- /dev/null
+++ b/versioned_docs/version-7.x/user/files-and-folders/favorites.md
@@ -0,0 +1,41 @@
+---
+sidebar_position: 7
+id: favorites
+title: Favorites
+description: Mark frequently used files for quick access
+draft: false
+---
+
+# Favorites
+
+Introduced in OpenCloud 6.0.0, Favorites lets you mark frequently used files and folders for quicker access in the Web Client.
+
+Favorite items are stored server-side, shown in a dedicated Favorites page and are also visible in search results and file lists. The feature works across personal and project spaces, including subfolders.
+
+## Mark an item as a favorite
+
+- Open the context menu for a file or folder.
+  <img src={require("./img/favorites/add-to-favorites-menu.png").default} alt="Context menu with favorites action" width="1920"/>
+
+- Choose "Add to favorites" in the context menu or in the batch actions.
+
+- The item is added to your favorites immediately.
+
+## Open your favorites
+
+- Open Favorites from the left sidebar in the Web Client.
+  <img src={require("./img/favorites/favorites-personal.png").default} alt="Favorites page with multiple personal files" width="1920"/>
+
+- The favorites page shows items from the personal space together.
+
+## Remove a favorite
+
+- Open the context menu again.
+  <img src={require("./img/favorites/remove-from-favorites-menu.png").default} alt="Context menu with remove from favorites action" width="1920"/>
+
+- Choose "Remove from favorites" in the context menu or in the batch actions.
+- The item is removed from your favorites.
+
+:::note
+Spaces themselves cannot yet be marked as favorites.
+:::
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/activity/activities-button.png b/versioned_docs/version-7.x/user/files-and-folders/img/activity/activities-button.png
new file mode 100644
index 000000000..21fff2b04
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/activity/activities-button.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/activity/activities.png b/versioned_docs/version-7.x/user/files-and-folders/img/activity/activities.png
new file mode 100644
index 000000000..3a01f53c0
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/activity/activities.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/activity/details-button.png b/versioned_docs/version-7.x/user/files-and-folders/img/activity/details-button.png
new file mode 100644
index 000000000..38de7703e
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/activity/details-button.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/actionbar-cut-option.png b/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/actionbar-cut-option.png
new file mode 100644
index 000000000..35b12b10c
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/actionbar-cut-option.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/create-button.png b/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/create-button.png
new file mode 100644
index 000000000..80dd7f6f0
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/create-button.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/create-options.png b/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/create-options.png
new file mode 100644
index 000000000..6a48acf30
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/create-options.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/mark-folder.png b/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/mark-folder.png
new file mode 100644
index 000000000..130872e50
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/mark-folder.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/new-button.png b/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/new-button.png
new file mode 100644
index 000000000..59a324dc0
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/new-button.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/paste-here-button.png b/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/paste-here-button.png
new file mode 100644
index 000000000..e5b67717c
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/paste-here-button.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/pasted-file.png b/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/pasted-file.png
new file mode 100644
index 000000000..f9131f5eb
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/pasted-file.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/rename-option.png b/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/rename-option.png
new file mode 100644
index 000000000..ae0cd48d2
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/rename-option.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/rename-popup.png b/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/rename-popup.png
new file mode 100644
index 000000000..063f1dd7d
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/rename-popup.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/right-click-cut-option.png b/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/right-click-cut-option.png
new file mode 100644
index 000000000..05c6db3ae
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/create-rename-move/right-click-cut-option.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/delete-options.png b/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/delete-options.png
new file mode 100644
index 000000000..46d046dfb
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/delete-options.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/folder-in-deleted-files.png b/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/folder-in-deleted-files.png
new file mode 100644
index 000000000..fbf715939
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/folder-in-deleted-files.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/mark-folder-in-deleted-files.png b/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/mark-folder-in-deleted-files.png
new file mode 100644
index 000000000..a79b9affb
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/mark-folder-in-deleted-files.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/mark-folder.png b/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/mark-folder.png
new file mode 100644
index 000000000..42fb0b8a1
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/mark-folder.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/restore-options.png b/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/restore-options.png
new file mode 100644
index 000000000..00b91afd6
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/restore-options.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/structure-in-deleted-files.png b/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/structure-in-deleted-files.png
new file mode 100644
index 000000000..4344877e4
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/structure-in-deleted-files.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/three-dot-menu-in-deleted-files.png b/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/three-dot-menu-in-deleted-files.png
new file mode 100644
index 000000000..69a239b5a
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/three-dot-menu-in-deleted-files.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/three-dot-menu.png b/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/three-dot-menu.png
new file mode 100644
index 000000000..598e35d58
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/delete-restore/three-dot-menu.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/favorites/add-to-favorites-menu.png b/versioned_docs/version-7.x/user/files-and-folders/img/favorites/add-to-favorites-menu.png
new file mode 100644
index 000000000..63bffe174
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/favorites/add-to-favorites-menu.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/favorites/favorites-personal.png b/versioned_docs/version-7.x/user/files-and-folders/img/favorites/favorites-personal.png
new file mode 100644
index 000000000..711096d42
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/favorites/favorites-personal.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/favorites/remove-from-favorites-menu.png b/versioned_docs/version-7.x/user/files-and-folders/img/favorites/remove-from-favorites-menu.png
new file mode 100644
index 000000000..95b8ee0d8
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/favorites/remove-from-favorites-menu.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/link/create-button.png b/versioned_docs/version-7.x/user/files-and-folders/img/link/create-button.png
new file mode 100644
index 000000000..bf8b9eb7f
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/link/create-button.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/link/pop-up-window.png b/versioned_docs/version-7.x/user/files-and-folders/img/link/pop-up-window.png
new file mode 100644
index 000000000..43fd1a08f
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/link/pop-up-window.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/link/shortcut-button.png b/versioned_docs/version-7.x/user/files-and-folders/img/link/shortcut-button.png
new file mode 100644
index 000000000..a7d5d7a48
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/link/shortcut-button.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/link/shortcut-right-click.png b/versioned_docs/version-7.x/user/files-and-folders/img/link/shortcut-right-click.png
new file mode 100644
index 000000000..2f0438df8
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/link/shortcut-right-click.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/link/url-and-title.png b/versioned_docs/version-7.x/user/files-and-folders/img/link/url-and-title.png
new file mode 100644
index 000000000..49a14f872
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/link/url-and-title.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/markdown-editor/editor-open.png b/versioned_docs/version-7.x/user/files-and-folders/img/markdown-editor/editor-open.png
new file mode 100644
index 000000000..829e599e0
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/markdown-editor/editor-open.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/markdown-editor/slash-menu.png b/versioned_docs/version-7.x/user/files-and-folders/img/markdown-editor/slash-menu.png
new file mode 100644
index 000000000..cb799f6e7
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/markdown-editor/slash-menu.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/photos-and-videos/photo-roll-screenshot.png b/versioned_docs/version-7.x/user/files-and-folders/img/photos-and-videos/photo-roll-screenshot.png
new file mode 100644
index 000000000..c4e8e8695
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/photos-and-videos/photo-roll-screenshot.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/photos-and-videos/video-screenshot.png b/versioned_docs/version-7.x/user/files-and-folders/img/photos-and-videos/video-screenshot.png
new file mode 100644
index 000000000..34b60afd2
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/photos-and-videos/video-screenshot.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/readme-files/readme-list-view.png b/versioned_docs/version-7.x/user/files-and-folders/img/readme-files/readme-list-view.png
new file mode 100644
index 000000000..84ae727ce
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/readme-files/readme-list-view.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/readme-files/readme-removed.png b/versioned_docs/version-7.x/user/files-and-folders/img/readme-files/readme-removed.png
new file mode 100644
index 000000000..58efbc23b
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/readme-files/readme-removed.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/search/drop-down-menu-searchbar.png b/versioned_docs/version-7.x/user/files-and-folders/img/search/drop-down-menu-searchbar.png
new file mode 100644
index 000000000..984eaa893
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/search/drop-down-menu-searchbar.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/search/search-example.png b/versioned_docs/version-7.x/user/files-and-folders/img/search/search-example.png
new file mode 100644
index 000000000..63f1bc2fc
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/search/search-example.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/search/searchbar.png b/versioned_docs/version-7.x/user/files-and-folders/img/search/searchbar.png
new file mode 100644
index 000000000..4de2f5e78
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/search/searchbar.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/tags/delete-a-tag.png b/versioned_docs/version-7.x/user/files-and-folders/img/tags/delete-a-tag.png
new file mode 100644
index 000000000..bfd73a108
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/tags/delete-a-tag.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/tags/details-button.png b/versioned_docs/version-7.x/user/files-and-folders/img/tags/details-button.png
new file mode 100644
index 000000000..362e509fd
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/tags/details-button.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/tags/tags-line.png b/versioned_docs/version-7.x/user/files-and-folders/img/tags/tags-line.png
new file mode 100644
index 000000000..9f5d3bbe5
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/tags/tags-line.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/tags/type-or-choose-a-tag.png b/versioned_docs/version-7.x/user/files-and-folders/img/tags/type-or-choose-a-tag.png
new file mode 100644
index 000000000..6a1b0b675
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/tags/type-or-choose-a-tag.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/upload-download-unzip/choose-download-files.png b/versioned_docs/version-7.x/user/files-and-folders/img/upload-download-unzip/choose-download-files.png
new file mode 100644
index 000000000..b7016436c
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/upload-download-unzip/choose-download-files.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/upload-download-unzip/download-options.png b/versioned_docs/version-7.x/user/files-and-folders/img/upload-download-unzip/download-options.png
new file mode 100644
index 000000000..d4431acec
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/upload-download-unzip/download-options.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/upload-download-unzip/unzip-options-fullpage.png b/versioned_docs/version-7.x/user/files-and-folders/img/upload-download-unzip/unzip-options-fullpage.png
new file mode 100644
index 000000000..2f5941c92
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/upload-download-unzip/unzip-options-fullpage.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/upload-download-unzip/upload-button.png b/versioned_docs/version-7.x/user/files-and-folders/img/upload-download-unzip/upload-button.png
new file mode 100644
index 000000000..536a62b11
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/upload-download-unzip/upload-button.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/upload-download-unzip/upload-options.png b/versioned_docs/version-7.x/user/files-and-folders/img/upload-download-unzip/upload-options.png
new file mode 100644
index 000000000..093c4fccc
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/upload-download-unzip/upload-options.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/upload-download-unzip/upload-window.png b/versioned_docs/version-7.x/user/files-and-folders/img/upload-download-unzip/upload-window.png
new file mode 100644
index 000000000..0cb9717d1
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/upload-download-unzip/upload-window.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/upload-download-unzip/zip-file.png b/versioned_docs/version-7.x/user/files-and-folders/img/upload-download-unzip/zip-file.png
new file mode 100644
index 000000000..43c5ad4ef
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/upload-download-unzip/zip-file.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/versions/details-button.png b/versioned_docs/version-7.x/user/files-and-folders/img/versions/details-button.png
new file mode 100644
index 000000000..db03436a6
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/versions/details-button.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/versions/versions-button.png b/versioned_docs/version-7.x/user/files-and-folders/img/versions/versions-button.png
new file mode 100644
index 000000000..2c6ceb3ac
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/versions/versions-button.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/img/versions/versions.png b/versioned_docs/version-7.x/user/files-and-folders/img/versions/versions.png
new file mode 100644
index 000000000..087847e7f
Binary files /dev/null and b/versioned_docs/version-7.x/user/files-and-folders/img/versions/versions.png differ
diff --git a/versioned_docs/version-7.x/user/files-and-folders/index.md b/versioned_docs/version-7.x/user/files-and-folders/index.md
new file mode 100644
index 000000000..ec12f202e
--- /dev/null
+++ b/versioned_docs/version-7.x/user/files-and-folders/index.md
@@ -0,0 +1,53 @@
+---
+sidebar_position: 0
+id: files-and-folders-overview
+title: Manage Files and Folders
+---
+
+# Manage Files and Folders
+
+Learn how to organize, manage, and review files and folders in OpenCloud.  
+This section covers common day-to-day tasks such as creating and moving content, uploading files, restoring deleted items, and reviewing file history.
+
+## In this section
+
+### Organize and manage content
+
+- [Create, rename, and move files and folders](./create-rename-move.md)  
+  Create new content, reorganize existing files and folders, and move items to a different location.
+
+- [Upload, download, and unzip content](./upload-download-unzip.md)  
+  Upload files to OpenCloud, download them to your device, or extract ZIP archives.
+
+- [Delete and restore items from the trash](./delete-restore.md)  
+  Remove files and folders and restore them later if needed.
+
+- [Editing Markdown files](./markdown-editor.md)  
+  Edit `README.md` and other Markdown files directly in OpenCloud with formatting suggestions.
+- [README files in folders](./readme-files.md)  
+  Add a `README.md` file to a folder so OpenCloud renders it above the file list.
+
+### Find and classify content
+
+- [Photos and videos](./photos-and-videos.md)  
+  Preview photos, browse them in a photo roll, and play videos directly in the web interface.
+
+- [Search for files and content](./search.md)  
+  Find files by name or search within their content.
+
+- [Favorites](./favorites.md)  
+  Mark frequently used files for quick access and collect them on a dedicated Favorites page.
+
+- [Add and remove tags](./tags.md)  
+  Use tags to organize files and folders and make them easier to find.
+
+- [Create shortcuts to files or web links](./shortcut.md)  
+  Add shortcuts to frequently used files or external websites for quicker access.
+
+### Review file history and activity
+
+- [View file versions and activity history](./versions.md)  
+  Review earlier file versions and track how a file has changed over time.
+
+- [Inspect file activity](./activity.md)  
+  See which actions were performed on a file or folder and who made the changes.
diff --git a/versioned_docs/version-7.x/user/files-and-folders/markdown-editor.md b/versioned_docs/version-7.x/user/files-and-folders/markdown-editor.md
new file mode 100644
index 000000000..31a4ac78e
--- /dev/null
+++ b/versioned_docs/version-7.x/user/files-and-folders/markdown-editor.md
@@ -0,0 +1,61 @@
+---
+id: markdown-editor
+sidebar_position: 3.6
+title: Editing Markdown Files
+description: Learn how to edit Markdown files with the OpenCloud Tiptap editor.
+---
+
+# Editing Markdown Files
+
+OpenCloud uses a Tiptap-based Markdown editor for files such as `README.md` and other `.md` files. The editor helps you write and format content even if you do not know Markdown syntax well.
+
+## How the Editor Works
+
+When you open a Markdown file, OpenCloud shows it in the editor so you can write and update the file directly in the browser.
+
+<img src={require("./img/markdown-editor/editor-open.png").default} alt="Markdown editor open on a README file" width="1920"/>
+
+You can add headings, lists, links, quotes, code, and other common formatting without leaving the file view.
+
+As you edit, OpenCloud shows the Markdown content rendered right away so you can immediately see how the file will look.
+
+The editor also supports inserting images and creating tables, which makes it easier to build richer Markdown files directly in OpenCloud.
+
+## Use the Slash Shortcut
+
+Type `/` in a new line to open the formatting menu.
+
+The menu gives you a quick overview of the available formatting options and lets you insert them without memorizing every shortcut.
+
+<img src={require("./img/markdown-editor/slash-menu.png").default} alt="Slash menu in the Markdown editor" width="1920"/>
+
+This is especially helpful when you want to insert formatting quickly while keeping your hands on the keyboard.
+
+## Use the Formatting Toolbar
+
+Use the formatting toolbar above the editor to insert common Markdown elements.
+
+Click the `Heading` button to choose a heading level or use the other buttons for bold, italic, lists, code, images, and tables.
+
+This is especially helpful if you want to format content quickly without memorizing every Markdown shortcut.
+
+## Supported Formatting
+
+The Markdown editor supports common formatting options for all Markdown files. You can use the toolbar or the slash menu to insert:
+
+- headings
+- bold and italic text
+- bullet and numbered lists
+- quotes
+- inline code and code blocks
+- links
+- images
+- tables
+
+## Good To Know
+
+- The editor works for Markdown files such as `README.md`.
+- You can use the formatting menu to build structured content step by step.
+- The file stays a normal Markdown file, so it can still be used outside OpenCloud.
+
+When the file is saved, the Markdown content is stored in the same `.md` file and can be rendered wherever Markdown is supported.
diff --git a/versioned_docs/version-7.x/user/files-and-folders/photos-and-videos.md b/versioned_docs/version-7.x/user/files-and-folders/photos-and-videos.md
new file mode 100644
index 000000000..5c51035ad
--- /dev/null
+++ b/versioned_docs/version-7.x/user/files-and-folders/photos-and-videos.md
@@ -0,0 +1,32 @@
+---
+sidebar_position: 3.6
+title: Photos and Videos
+description: Learn how OpenCloud previews photos and plays videos in the web interface.
+---
+
+# Photos and Videos
+
+OpenCloud can preview photos and play videos directly in the web interface.
+This makes it easier to review media without downloading files first.
+
+## Photo preview
+
+Open a photo in the preview view to browse through the photo roll.
+
+<img src={require("./img/photos-and-videos/photo-roll-screenshot.png").default} alt="Photo roll view in OpenCloud" width="1920"/>
+
+The photo viewer supports photo roll style navigation, so you can move through a series of images without leaving the preview.
+
+## Video playback
+
+Videos open in the same preview area and can be played directly in the browser.
+
+<img src={require("./img/photos-and-videos/video-screenshot.png").default} alt="Video preview in OpenCloud" width="1920"/>
+
+Video playback works directly in OpenCloud, so you can review clips without downloading them first.
+
+## Notes
+
+- The experience depends on the file type and browser capabilities.
+- Very large media files may still take a moment to load.
+- This feature is meant for quick viewing, not for advanced media editing.
diff --git a/versioned_docs/version-7.x/user/files-and-folders/readme-files.md b/versioned_docs/version-7.x/user/files-and-folders/readme-files.md
new file mode 100644
index 000000000..2962d06fd
--- /dev/null
+++ b/versioned_docs/version-7.x/user/files-and-folders/readme-files.md
@@ -0,0 +1,52 @@
+---
+sidebar_position: 3.5
+title: README Files in Folders
+description: Learn how README.md files are rendered in folders in OpenCloud.
+---
+
+# README Files in Folders
+
+If a folder contains a file named `README.md`, OpenCloud renders its Markdown content above the file list.
+
+<img src={require("./img/readme-files/readme-list-view.png").default} alt="README rendered in list view with the file still visible" width="1920"/>
+
+## Create a README File
+
+1. Open the folder where you want to add the README.
+2. Create or upload a file named `README.md`.
+3. Add your Markdown content and save the file.
+
+OpenCloud renders the content when the folder is opened or refreshed.
+
+## Supported File Name
+
+The file name must be exactly:
+
+```text
+README.md
+```
+
+## Example
+
+A `README.md` file can contain Markdown like this:
+
+```markdown
+# Photos
+
+This folder contains visual samples for preview and documentation screenshots.
+
+The images are used to show list view, thumbnail view, and image preview behavior in OpenCloud.
+
+## Files
+
+- moon-surface-public-domain.jpg
+- rotated-chessboard-photo.jpg
+- vintage-computer-terminal.jpg
+- Space-Nebula.jpg
+```
+
+## Remove the README Section
+
+Delete or rename `README.md` to remove the rendered section.
+
+<img src={require("./img/readme-files/readme-removed.png").default} alt="Folder without the rendered README section" width="1920"/>
diff --git a/versioned_docs/version-7.x/user/files-and-folders/search.md b/versioned_docs/version-7.x/user/files-and-folders/search.md
new file mode 100644
index 000000000..e8ca22f67
--- /dev/null
+++ b/versioned_docs/version-7.x/user/files-and-folders/search.md
@@ -0,0 +1,25 @@
+---
+sidebar_position: 4
+id: search
+title: Search
+description: Using the search in OpenCloud
+draft: false
+---
+
+# Using the search in OpenCloud
+
+You can use the search bar in the top bar to find files and content quickly.
+
+## This is how the search works
+
+- The search bar is located at the top of the top bar in the web interface.
+  <img src={require("./img/search/searchbar.png").default} alt="Search bar" width="1920"/>
+- Shortcut: press `/` or type `s` to focus the search bar.
+
+- Click on the drop-down menu next to the search bar.
+- Select whether you want to search in all files or only in the current folder.
+  <img src={require("./img/search/drop-down-menu-searchbar.png").default} alt="Select where to search" width="500"/>
+- The Search function searches through file names as well as the content of the files to display relevant results.
+  <img src={require("./img/search/search-example.png").default} alt="Example search" width="500"/>
+
+Use these steps to find your files or folders quickly and efficiently!
diff --git a/versioned_docs/version-7.x/user/files-and-folders/shortcut.md b/versioned_docs/version-7.x/user/files-and-folders/shortcut.md
new file mode 100644
index 000000000..ffccc6ac7
--- /dev/null
+++ b/versioned_docs/version-7.x/user/files-and-folders/shortcut.md
@@ -0,0 +1,35 @@
+---
+sidebar_position: 5
+id: shortcut
+title: Shortcut
+description: Create shortcuts in OpenCloud
+draft: false
+---
+
+# Shortcut
+
+With OpenCloud you can create shortcuts to websites or files
+
+## Create shortcut
+
+- Open the “+ New” menu and select “Shortcut”.
+
+  <img src={require("./img/link/shortcut-button.png").default} alt="Select Shortcut" width="1920"/>
+
+- Enter a URL or file name.
+  - You can also pick a file from the list after typing a few letters.
+
+  <img src={require("./img/link/pop-up-window.png").default} alt="Enter link or file in popup window" width="500"/>
+
+- Enter a name for the shortcut.
+
+  <img src={require("./img/link/url-and-title.png").default} alt="Enter a name for the shortcut" width="500"/>
+
+- Create the shortcut by clicking on "Create"
+
+  <img src={require("./img/link/create-button.png").default} alt="Click on create" width="500"/>
+
+## Use shortcut
+
+- Open the context menü, click on "Open with" and choose “Open shortcut”.
+  <img src={require("./img/link/shortcut-right-click.png").default} alt="Right click on shortcut" width="1920"/>
diff --git a/versioned_docs/version-7.x/user/files-and-folders/tags.md b/versioned_docs/version-7.x/user/files-and-folders/tags.md
new file mode 100644
index 000000000..2a584f4b1
--- /dev/null
+++ b/versioned_docs/version-7.x/user/files-and-folders/tags.md
@@ -0,0 +1,35 @@
+---
+sidebar_position: 6
+id: tags
+title: Tags
+description: Add and manage tags with OpenCloud
+draft: false
+---
+
+# Add and manage tags with OpenCloud
+
+With OpenCloud you can add tags to files and folders to make them easier to search or group.
+
+## Add tag
+
+- Open the context menu for the file or folder.
+- Select the “Details” option.
+  <img src={require("./img/tags/details-button.png").default} alt="Select details in context menu" width="1920"/>
+
+## Add a tag
+
+- Click in the input field next to “Tags”.
+  <img src={require("./img/tags/tags-line.png").default} alt="Input line next to tags" width="400"/>
+- Select an existing tag, or enter a new term to create a new tag.
+  <img src={require("./img/tags/type-or-choose-a-tag.png").default} alt="Enter tag name" width="400"/>
+
+  The tag is added and is now linked to the file or folder.
+
+## Remove tag
+
+- Open the “Details” of the file or folder again.
+- Find the tag you want to remove.
+- Click on the “x” next to the tag to delete it.
+  <img src={require("./img/tags/delete-a-tag.png").default} alt="Click on x next to the tag" width="400"/>
+
+  The file or folder is now no longer associated with this tag.
diff --git a/versioned_docs/version-7.x/user/files-and-folders/upload-download-unzip.md b/versioned_docs/version-7.x/user/files-and-folders/upload-download-unzip.md
new file mode 100644
index 000000000..76d681b01
--- /dev/null
+++ b/versioned_docs/version-7.x/user/files-and-folders/upload-download-unzip.md
@@ -0,0 +1,59 @@
+---
+sidebar_position: 2
+id: upload-download-unzip
+title: Upload - Download - Unzip
+description: Upload - Download - Unzip
+draft: false
+---
+
+# Upload - Download - Unzip
+
+## Upload files or folders
+
+- Open the “+ New” menu in the left sidebar.
+
+  <img src={require("./img/upload-download-unzip/upload-button.png").default} alt="Upload button" width="1920"/>
+
+- Select whether you want to upload files or folders.
+
+  <img src={require("./img/upload-download-unzip/upload-options.png").default} alt="Select file or folder" width="400" style={{ display: "block", marginTop: "1rem", marginBottom: "1rem" }}/>
+
+- Select files/folders:
+  - In the window that opens, select the desired files or folders.
+  - Several files or folders can be selected at the same time.
+- Confirm upload:
+  - Click on “Open” to start the upload.
+
+    <img src={require("./img/upload-download-unzip/upload-window.png").default} alt="Confirm upload" width="500"/>
+
+  - Once completed, a message will appear in the bottom right-hand corner.
+
+- Alternatively:
+  - Drag and drop the files or folders directly from your Explorer window into the browser to upload them.
+
+## Download files or folders
+
+- Choose the file(s) you want to download
+
+  <img src={require("./img/upload-download-unzip/choose-download-files.png").default} alt="Admin spaces" width="1920"/>
+
+- Open the context menu - By right-clicking - or by clicking on the three dots next to the file.
+
+  <img src={require("./img/upload-download-unzip/download-options.png").default} alt="Download options" width="1920"/>
+
+- Select “Download” from the menu or in the top bar.
+
+- If you download several files or folders, these are saved as a ZIP file.
+- Unzip the ZIP file on your device after downloading.
+
+## Unzip
+
+If activated, you can unzip packed files in the cloud.
+
+- Select the ZIP file in the file list and open the context menu by right-clicking the file or clicking the three dots next to it.
+- Choose “Extract here”.
+
+  <img src={require("./img/upload-download-unzip/unzip-options-fullpage.png").default} alt="Extract zip file options full screen" width="1920"/>
+
+- The contents are extracted directly in the cloud and appear in the current folder.
+- Once the process is complete, a notification appears.
diff --git a/versioned_docs/version-7.x/user/files-and-folders/versions.md b/versioned_docs/version-7.x/user/files-and-folders/versions.md
new file mode 100644
index 000000000..e79fad455
--- /dev/null
+++ b/versioned_docs/version-7.x/user/files-and-folders/versions.md
@@ -0,0 +1,31 @@
+---
+sidebar_position: 7
+id: versions
+title: Versions
+description: Managing Versions of files in OpenCloud
+draft: false
+---
+
+# Managing versions of files in OpenCloud
+
+OpenCloud saves different versions of files. This allows you to restore or download previous versions:
+
+## View and restore versions
+
+- Open details
+  - Right-click on the file
+  - or click on the three dots in the corresponding file line.
+  - Select “Details” from the context menu.
+    <img src={require("./img/versions/details-button.png").default} alt="Select details" width="1920"/>
+
+- Select versions
+  - In the right sidebar that opens select the “Versions” item.
+    <img src={require("./img/versions/versions-button.png").default} alt="Select versions" width="400" style={{ display: "block", marginTop: "1rem", marginBottom: "1rem" }}/>
+
+- Show versions
+  - All versions of the file are displayed.
+  - You can now restore or download the desired version.
+
+    <img src={require("./img/versions/versions.png").default} alt="Show all versions" width="400" style={{ display: "block", marginTop: "1rem", marginBottom: "1rem" }}/>
+
+These steps give you access to older versions of your files at any time!
diff --git a/versioned_docs/version-7.x/user/general/_category_.json b/versioned_docs/version-7.x/user/general/_category_.json
new file mode 100644
index 000000000..23b82718d
--- /dev/null
+++ b/versioned_docs/version-7.x/user/general/_category_.json
@@ -0,0 +1,5 @@
+{
+  "label": "User Interface and Navigation",
+  "position": 2
+}
+
diff --git a/versioned_docs/version-7.x/user/general/account-settings.md b/versioned_docs/version-7.x/user/general/account-settings.md
new file mode 100644
index 000000000..5433d127a
--- /dev/null
+++ b/versioned_docs/version-7.x/user/general/account-settings.md
@@ -0,0 +1,83 @@
+---
+sidebar_position: 2
+id: settings
+title: Account Settings
+description: User account settings in OpenCloud
+draft: false
+---
+
+# User account settings in OpenCloud
+
+In OpenCloud you have the option of making various settings for your user account to customize it according to your needs
+
+## Access the settings
+
+- Click on your avatar in the top right corner
+- Select "Preferences"
+  <img src={require("./img/account-settings/access.png").default} alt="Access settings" width="400" style={{ display: "block", marginTop: "1rem", marginBottom: "1rem" }}/>
+
+## Account information
+
+In the settings you can choose between different sections:
+
+### Profile
+
+- Profile picture
+- Username / Login name
+- First and last name
+- E-mail address
+- Personal storage space
+- Group memberships
+
+<img src={require("./img/account-settings/account-information.png").default} alt="Account Information" width="1920"/>
+
+### Avatar
+
+In profile picture you can change your Avatar image:
+
+- Click on "Upload" under your Avatar icon
+  <img src={require("./img/account-settings/avatar-menu.png").default} alt="Avatar menu" width="400" style={{ display: "block", marginTop: "1rem", marginBottom: "1rem" }}/>
+- Choose your Avatar image and click on "Upload"
+  <img src={require("./img/account-settings/avatar-upload.png").default} alt="Avatar upload" width="500"/>
+- now it opens a window you can anjusted your image and then click on the "Set" button
+  <img src={require("./img/account-settings/avatar-settings.png").default} alt="Avatar settings" width="400" style={{ display: "block", marginTop: "1rem", marginBottom: "1rem" }}/>
+- after this your Avatar will be set up to your account
+  <img src={require("./img/account-settings/visible-avatar.png").default} alt="Visible Avatar" width="1920"/>
+
+## Preferences
+
+Depending on the basic configuration, you can change the following options:
+
+- Language:  
+  Select the desired language for your user interface.
+- Password:  
+  Change your password for access to your user account.
+- Theme:  
+  Customize the Theme of the user interface according to your preferences.
+- Email notifications:  
+  Determine which email notifications you would like to receive from OpenCloud.
+- View options:  
+  Set the WebDAV settings to allow external access to files and folders.
+  <img src={require("./img/account-settings/preferences.png").default} alt="Preferences" width="1920"/>
+
+## Extensions
+
+Under Extensions you can configure installed extensions, such as the Progressbar, if available.
+<img src={require("./img/account-settings/extensions.png").default} alt="Extensions" width="1920"/>
+
+## Calendar
+
+Under Calendar you can access your personal calendar for integration with third-party apps like Thunderbird, Apple Calendar, and others, when configured.
+
+<img src={require("./img/account-settings/calendar.png").default} alt="Calendar" width="1920"/>
+
+## GDPR
+
+Under GDPR you can request a data export of your personal data if you wish.
+<img src={require("./img/account-settings/gdpr.png").default} alt="GDPR" width="1920"/>
+
+## App Tokens
+
+App Tokens allow you to connect external apps and services (such as WebDAV clients) securely without using your main password.
+
+<img src={require("./img/account-settings/app-tokens.png").default} alt="App Tokens" width="1920"/>
diff --git a/versioned_docs/version-7.x/user/general/file-list-adjustments.md b/versioned_docs/version-7.x/user/general/file-list-adjustments.md
new file mode 100644
index 000000000..87cf54484
--- /dev/null
+++ b/versioned_docs/version-7.x/user/general/file-list-adjustments.md
@@ -0,0 +1,31 @@
+---
+sidebar_position: 3
+id: customization-file-list
+title: Customization of the file list
+description: Files-List customizations in OpenCloud
+draft: false
+---
+
+# Files-List customizations in OpenCloud
+
+Clicking on the settings icon on the right side of the user interface takes you to the options for customizing the view. Here you can customize the display
+
+## Available options
+
+<img src={require("./img/files-list-adjustment/settings-icon.png").default} alt="Settings icon" width="400"/>
+
+- Show hidden files
+  - Activate or deactivate the display of hidden files.
+  - Hidden files are often system or configuration files.
+
+- Show file extensions
+  - Specify whether the file extensions (e.g. `.docx`, `.jpg`) should be displayed after the file names. This makes it easier to identify file types.
+
+- Items per page
+  - Specify how many files should be displayed per page in a folder.
+  - Useful for navigating in folders with many files.
+
+- Tile size
+  - Customize the size of the icons and buttons:
+  - Small tiles for a more compact view.
+  - Large tiles for a clearer view.
diff --git a/versioned_docs/version-7.x/user/general/img/account-settings/access.png b/versioned_docs/version-7.x/user/general/img/account-settings/access.png
new file mode 100644
index 000000000..6bc31d65e
Binary files /dev/null and b/versioned_docs/version-7.x/user/general/img/account-settings/access.png differ
diff --git a/versioned_docs/version-7.x/user/general/img/account-settings/account-information.png b/versioned_docs/version-7.x/user/general/img/account-settings/account-information.png
new file mode 100644
index 000000000..f3b3181b4
Binary files /dev/null and b/versioned_docs/version-7.x/user/general/img/account-settings/account-information.png differ
diff --git a/versioned_docs/version-7.x/user/general/img/account-settings/app-tokens.png b/versioned_docs/version-7.x/user/general/img/account-settings/app-tokens.png
new file mode 100644
index 000000000..1751e0211
Binary files /dev/null and b/versioned_docs/version-7.x/user/general/img/account-settings/app-tokens.png differ
diff --git a/versioned_docs/version-7.x/user/general/img/account-settings/avatar-menu.png b/versioned_docs/version-7.x/user/general/img/account-settings/avatar-menu.png
new file mode 100644
index 000000000..d8e9ef7bf
Binary files /dev/null and b/versioned_docs/version-7.x/user/general/img/account-settings/avatar-menu.png differ
diff --git a/versioned_docs/version-7.x/user/general/img/account-settings/avatar-settings.png b/versioned_docs/version-7.x/user/general/img/account-settings/avatar-settings.png
new file mode 100644
index 000000000..c6b86d763
Binary files /dev/null and b/versioned_docs/version-7.x/user/general/img/account-settings/avatar-settings.png differ
diff --git a/versioned_docs/version-7.x/user/general/img/account-settings/avatar-upload.png b/versioned_docs/version-7.x/user/general/img/account-settings/avatar-upload.png
new file mode 100644
index 000000000..1fc7e40cd
Binary files /dev/null and b/versioned_docs/version-7.x/user/general/img/account-settings/avatar-upload.png differ
diff --git a/versioned_docs/version-7.x/user/general/img/account-settings/calendar.png b/versioned_docs/version-7.x/user/general/img/account-settings/calendar.png
new file mode 100644
index 000000000..3acc0fc46
Binary files /dev/null and b/versioned_docs/version-7.x/user/general/img/account-settings/calendar.png differ
diff --git a/versioned_docs/version-7.x/user/general/img/account-settings/extensions.png b/versioned_docs/version-7.x/user/general/img/account-settings/extensions.png
new file mode 100644
index 000000000..f877784f8
Binary files /dev/null and b/versioned_docs/version-7.x/user/general/img/account-settings/extensions.png differ
diff --git a/versioned_docs/version-7.x/user/general/img/account-settings/gdpr.png b/versioned_docs/version-7.x/user/general/img/account-settings/gdpr.png
new file mode 100644
index 000000000..1d27b8770
Binary files /dev/null and b/versioned_docs/version-7.x/user/general/img/account-settings/gdpr.png differ
diff --git a/versioned_docs/version-7.x/user/general/img/account-settings/preferences.png b/versioned_docs/version-7.x/user/general/img/account-settings/preferences.png
new file mode 100644
index 000000000..c3d609664
Binary files /dev/null and b/versioned_docs/version-7.x/user/general/img/account-settings/preferences.png differ
diff --git a/versioned_docs/version-7.x/user/general/img/account-settings/visible-avatar.png b/versioned_docs/version-7.x/user/general/img/account-settings/visible-avatar.png
new file mode 100644
index 000000000..db5e81c73
Binary files /dev/null and b/versioned_docs/version-7.x/user/general/img/account-settings/visible-avatar.png differ
diff --git a/versioned_docs/version-7.x/user/general/img/files-list-adjustment/settings-icon.png b/versioned_docs/version-7.x/user/general/img/files-list-adjustment/settings-icon.png
new file mode 100644
index 000000000..3857d6956
Binary files /dev/null and b/versioned_docs/version-7.x/user/general/img/files-list-adjustment/settings-icon.png differ
diff --git a/versioned_docs/version-7.x/user/general/img/overview/marker.svg b/versioned_docs/version-7.x/user/general/img/overview/marker.svg
new file mode 100644
index 000000000..c0d261367
--- /dev/null
+++ b/versioned_docs/version-7.x/user/general/img/overview/marker.svg
@@ -0,0 +1,60 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1180 900" width="1180" height="900" role="img" aria-label="OpenCloud overview markers">
+<defs><filter id="markerShadow" x="-20%" y="-20%" width="140%" height="140%"><feDropShadow dx="0" dy="1" stdDeviation="1.2" flood-opacity="0.18"/></filter></defs>
+<g fill="#f5401d" filter="url(#markerShadow)">
+<polygon points="69,353 111,360 69,367"/>
+<circle cx="48" cy="360" r="23"/>
+<polygon points="1096,79 1103,37 1110,79"/>
+<circle cx="1103" cy="100" r="23"/>
+<polygon points="226,23 268,30 226,37"/>
+<circle cx="205" cy="30" r="23"/>
+<polygon points="681,21 723,28 681,35"/>
+<circle cx="660" cy="28" r="23"/>
+<polygon points="328,619 335,577 342,619"/>
+<circle cx="335" cy="640" r="23"/>
+<polygon points="324,67 282,74 324,81"/>
+<circle cx="345" cy="74" r="23"/>
+<polygon points="448,146 455,176 462,146"/>
+<circle cx="455" cy="125" r="23"/>
+<polygon points="696,81 738,88 696,95"/>
+<circle cx="675" cy="88" r="23"/>
+<polygon points="807,81 765,88 807,95"/>
+<circle cx="828" cy="88" r="23"/>
+<polygon points="1135,79 1142,37 1149,79"/>
+<circle cx="1142" cy="100" r="23"/>
+<polygon points="1104,338 1146,345 1104,352"/>
+<circle cx="1083" cy="345" r="23"/>
+<polygon points="809,153 767,160 809,167"/>
+<circle cx="830" cy="160" r="23"/>
+<polygon points="824,507 782,514 824,521"/>
+<circle cx="845" cy="514" r="23"/>
+<polygon points="1101,570 1143,577 1101,584"/>
+<circle cx="1080" cy="577" r="23"/>
+<polygon points="1101,618 1143,625 1101,632"/>
+<circle cx="1080" cy="625" r="23"/>
+<polygon points="1101,666 1143,673 1101,680"/>
+<circle cx="1080" cy="673" r="23"/>
+<polygon points="1101,713 1143,720 1101,727"/>
+<circle cx="1080" cy="720" r="23"/>
+<polygon points="553,719 560,677 567,719"/>
+<circle cx="560" cy="740" r="23"/>
+</g>
+<g fill="#ffffff" font-family="Arial, Helvetica, sans-serif" font-weight="700" font-size="21" text-anchor="middle" dominant-baseline="central">
+<text x="48" y="360">1</text>
+<text x="1103" y="100">2</text>
+<text x="205" y="30">3</text>
+<text x="660" y="28">4</text>
+<text x="335" y="640">5</text>
+<text x="345" y="74">6</text>
+<text x="455" y="125">7</text>
+<text x="675" y="88">8</text>
+<text x="828" y="88">9</text>
+<text x="1142" y="100">10</text>
+<text x="1083" y="345">11</text>
+<text x="830" y="160">12</text>
+<text x="845" y="514">13</text>
+<text x="1080" y="577">14</text>
+<text x="1080" y="625">15</text>
+<text x="1080" y="673">16</text>
+<text x="1080" y="720">17</text>
+<text x="560" y="740">18</text>
+</g></svg>
\ No newline at end of file
diff --git a/versioned_docs/version-7.x/user/general/img/overview/overview.png b/versioned_docs/version-7.x/user/general/img/overview/overview.png
new file mode 100644
index 000000000..b283124a5
Binary files /dev/null and b/versioned_docs/version-7.x/user/general/img/overview/overview.png differ
diff --git a/versioned_docs/version-7.x/user/general/img/view-modes/condensed.png b/versioned_docs/version-7.x/user/general/img/view-modes/condensed.png
new file mode 100644
index 000000000..509b5f611
Binary files /dev/null and b/versioned_docs/version-7.x/user/general/img/view-modes/condensed.png differ
diff --git a/versioned_docs/version-7.x/user/general/img/view-modes/default.png b/versioned_docs/version-7.x/user/general/img/view-modes/default.png
new file mode 100644
index 000000000..7aad86046
Binary files /dev/null and b/versioned_docs/version-7.x/user/general/img/view-modes/default.png differ
diff --git a/versioned_docs/version-7.x/user/general/img/view-modes/tiles.png b/versioned_docs/version-7.x/user/general/img/view-modes/tiles.png
new file mode 100644
index 000000000..a02a3370d
Binary files /dev/null and b/versioned_docs/version-7.x/user/general/img/view-modes/tiles.png differ
diff --git a/versioned_docs/version-7.x/user/general/index.md b/versioned_docs/version-7.x/user/general/index.md
new file mode 100644
index 000000000..7ef0c0760
--- /dev/null
+++ b/versioned_docs/version-7.x/user/general/index.md
@@ -0,0 +1,23 @@
+---
+title: Web User Interface and Navigation
+---
+
+# Web User Interface and Navigation
+
+The Web Client is the main interface of OpenCloud and provides full access through the browser without requiring any additional software.
+
+This section explains the main areas of the interface and shows how to navigate the Web Client, adjust the file list, and personalize your account settings.
+
+## In this section
+
+- [Overview](./overview.md)  
+  Get familiar with the main areas of the Web Client, including the sidebar, top bar, file list, and action areas.
+
+- [Account Settings](./account-settings.md)  
+  Manage your profile, preferences, avatar, calendar access, GDPR export, and app tokens.
+
+- [Customize the file list](./file-list-adjustments.md)  
+  Adjust how files are displayed, including hidden files, file extensions, pagination, and tile size.
+
+- [View modes](./view-modes.md)  
+  Switch between table, condensed, and tile views to change how the file list is displayed.
diff --git a/versioned_docs/version-7.x/user/general/overview.md b/versioned_docs/version-7.x/user/general/overview.md
new file mode 100644
index 000000000..01eee8576
--- /dev/null
+++ b/versioned_docs/version-7.x/user/general/overview.md
@@ -0,0 +1,109 @@
+---
+sidebar_position: 1
+id: overview
+title: Overview
+description: Overview of the web user interface
+draft: false
+---
+
+import OverviewMarker from "./img/overview/marker.svg";
+
+# OpenCloud - Overview of the web user interface
+
+The OpenCloud web interface consists of several areas that help you to work efficiently with files and settings
+
+<div style={{ position: "relative", display: "inline-block", width: "100%", maxWidth: "1920px" }}>
+  <img
+    src={require("./img/overview/overview.png").default}
+    alt="Overview"
+    width="1920"
+    style={{ display: 'block', width: '100%', height: 'auto' }}
+  />
+  <OverviewMarker
+    aria-hidden="true"
+    style={{
+      position: 'absolute',
+      inset: 0,
+      width: '100%',
+      height: '100%',
+      pointerEvents: 'none',
+      zIndex: 1,
+    }}
+  />
+</div>
+
+## 1. Left Sidebar
+
+The sidebar contains the navigation elements such as Spaces, Files, Shares and Settings.
+
+## 2. App Switcher
+
+The menu in the top right corner allows you to switch between different Apps and modules.
+
+## 3. Top Bar
+
+The top bar contains important functions such as the search bar, user actions and global settings.
+
+## 4. Search Bar
+
+Allows you to quickly find files, folders or spaces.
+
+## 5. Files List
+
+Displays all files and folders in a selected view.
+
+## 6. Breadcrumb Menu
+
+Shows the current path of your navigation and allows you to quickly jump back to previous directories.
+
+## 7. Batch Actions
+
+Allows you to edit, move or delete several selected files at the same time.
+
+## 8. View Modes
+
+Provides various display options for the file list:
+
+- List view
+- Tile view
+- Condensed view
+
+## 9. View Settings
+
+Here you can customize additional display options such as sorting or column selection.
+
+## 10. User Menu
+
+    Click on your profile picture in the top right corner to access Settings, Logout and Account Options.
+
+## 11. Right Sidebar
+
+    Shows additional information and panels for shares, activities or file details.
+
+## 12. Actions
+
+    Here you will find Actions such as Download, Share, Delete or Edit for selected files.
+
+## 13. Three-Dot Menu
+
+    Provides further options for files, folders or spaces.
+
+## 14. Actions Panel
+
+    Shows possible actions for the selected file, e.g. rename or move.
+
+## 15. Shares Panel
+
+    Here you can share files and folders internally or externally and manage permissions.
+
+## 16. Versions
+
+    Shows an overview of the versions of a selected file or folder.
+
+## 17. Activity Panel
+
+    Shows an overview of changes and activities within a space or file.
+
+## 18. Context Menu
+
+    Right-clicking on a file or folder opens the context menu with specific options.
diff --git a/versioned_docs/version-7.x/user/general/view-modes.md b/versioned_docs/version-7.x/user/general/view-modes.md
new file mode 100644
index 000000000..5bc73169c
--- /dev/null
+++ b/versioned_docs/version-7.x/user/general/view-modes.md
@@ -0,0 +1,31 @@
+---
+sidebar_position: 4
+id: view-modes
+title: View modes
+description: View modes for the file list in OpenCloud
+draft: false
+---
+
+# File list view modes in OpenCloud
+
+In OpenCloud, you can choose between different view modes for files and folders to customize the display to your preferences.
+
+## Available view modes
+
+### Tiles view
+
+This is the default view. Files and folders are displayed as tiles, which works well for visual browsing.
+
+<img src={require("./img/view-modes/default.png").default} alt="Tiles view of the file list" width="1920"/>
+
+### Condensed table view
+
+A more compact table view that groups information more tightly to save space.
+
+<img src={require("./img/view-modes/condensed.png").default} alt="Condensed table view of the file list" width="1920"/>
+
+### Default table view
+
+The classic list view, where files and folders are displayed in a detailed table.
+
+<img src={require("./img/view-modes/tiles.png").default} alt="Default table view of the file list" width="1920"/>
diff --git a/versioned_docs/version-7.x/user/img/common-issues/desktop-excluded.png b/versioned_docs/version-7.x/user/img/common-issues/desktop-excluded.png
new file mode 100644
index 000000000..a9463fc8a
Binary files /dev/null and b/versioned_docs/version-7.x/user/img/common-issues/desktop-excluded.png differ
diff --git a/versioned_docs/version-7.x/user/index.md b/versioned_docs/version-7.x/user/index.md
new file mode 100644
index 000000000..f7fb8d81f
--- /dev/null
+++ b/versioned_docs/version-7.x/user/index.md
@@ -0,0 +1,95 @@
+---
+sidebar_position: 1
+title: Welcome
+description: Welcome
+draft: false
+---
+
+<!-- markdownlint-disable MD041 -->
+
+import OcLogoPetrol from '/static/img/oc-logo-petrol.svg';
+import OcLogoLilac from '/static/img/oc-logo-lilac.svg';
+
+<!-- markdownlint-enable MD041 -->
+
+# Welcome
+
+<OcLogoPetrol width="250" height="55" className="light-mode-image"/>
+<OcLogoLilac width="250" height="55" className="dark-mode-image"/>
+
+## Welcome to the OpenCloud knowledge base
+
+This documentation helps you get started with OpenCloud, understand its main features, and find guidance for everyday tasks, administration, and troubleshooting.
+
+## What is OpenCloud?
+
+OpenCloud is a file sharing and collaboration platform developed by the [Heinlein Group](https://www.heinlein.group/). It helps teams store, organize, share, and collaborate on files across different devices and use cases.
+
+You can access OpenCloud in different ways, depending on your workflow:
+
+- The [Web Client](./general/) provides full access to OpenCloud features directly in the browser, including file management, collaboration features, and administration options based on your permissions.
+- The [Desktop Client](./desktop-client/) synchronizes files between OpenCloud and your local computer for offline work and automatic updates.
+- The [iOS App](./ios-app/) provides convenient access to files and essential actions on iPhone and iPad.
+- The [Android App](./android-app/) provides convenient access to files and essential actions on Android devices.
+- [Collabora in OpenCloud](./collabora) provides browser-based document editing and real-time collaboration for supported office files stored in OpenCloud.
+
+Each client and integration is designed for a specific use case: the Web Client for full-featured browser access, the Desktop Client for local synchronization, the mobile apps for mobile access and everyday tasks, and Collabora Online for browser-based document editing and collaboration.
+
+## Administration and deployment
+
+If you want to install, set up, or manage your own OpenCloud environment, see the [Admin documentation](../admin/) and the [Getting Started](../admin/getting-started/) section.
+
+## Documentation versions
+
+This documentation is versioned so you can find the information that matches your OpenCloud version.
+
+- **Rolling version**  
+  Reflects the current development state. Changes are added continuously, but some features may not yet be fully documented.
+
+- **Stable release versions**  
+  Provide documentation for officially released versions. These versions are reviewed and remain unchanged after publication.
+
+You can switch between the Rolling version and specific release versions using the version menu in the top-right corner.
+
+## Explore the documentation
+
+### Apps
+
+- [OpenCloud Desktop Client](./desktop-client/)  
+  Learn how to install, set up, and use the Desktop Client.
+
+- [OpenCloud iOS App](./ios-app/)  
+  Find guidance for using OpenCloud on iPhone and iPad.
+
+- [OpenCloud Android App](./android-app/)  
+  Find guidance for using OpenCloud on Android devices.
+
+### Web and editing
+
+- [User Interface and Navigation](./general/)  
+  Learn how to navigate the Web Client, adjust account settings, and customize the interface.
+
+- [Collabora Online](./collabora)  
+  Get an overview of the document editing and collaboration features available through Collabora Online in OpenCloud.
+
+- [Manage Files and Folders](./files-and-folders/)  
+  Find guidance for creating, organizing, moving, deleting, and restoring files and folders.
+
+- [Share Files and Folders](./sharing/)  
+  Learn how to share content internally, create public links, and use File Drop.
+
+- [Working in Teams with Spaces](./spaces/)  
+  Understand how to use Spaces to organize shared work and collaborate with teams.
+
+### Administration
+
+- [Roles](./roles/)  
+  Learn about user roles, Space roles, and share permissions in OpenCloud.
+
+- [Administration of OpenCloud](./admin/)  
+  Explore administration features such as settings, app tokens, and WebDAV access.
+
+### Help
+
+- [Common Issues and Help](./common-issues)  
+  Find solutions for common problems and answers to frequently asked questions.
diff --git a/versioned_docs/version-7.x/user/ios-app/_category_.json b/versioned_docs/version-7.x/user/ios-app/_category_.json
new file mode 100644
index 000000000..39441f177
--- /dev/null
+++ b/versioned_docs/version-7.x/user/ios-app/_category_.json
@@ -0,0 +1,8 @@
+{
+  "label": "OpenCloud iOS App",
+  "position": 7,
+  "link": {
+    "type": "doc",
+    "id": "ios-app-overview"
+  }
+}
diff --git a/versioned_docs/version-7.x/user/ios-app/files-and-folders/_category_.json b/versioned_docs/version-7.x/user/ios-app/files-and-folders/_category_.json
new file mode 100644
index 000000000..9dd2cdc23
--- /dev/null
+++ b/versioned_docs/version-7.x/user/ios-app/files-and-folders/_category_.json
@@ -0,0 +1,10 @@
+{
+  "label": "Files and Folders",
+  "position": 2,
+  "key": "ios-files-folders",
+  "link": {
+    "type": "generated-index",
+    "description": "Tutorials for managing your files and folders in the OpenCloud iOS App.",
+    "slug": "user/ios-app/files-and-folders/"
+  }
+}
diff --git a/versioned_docs/version-7.x/user/ios-app/files-and-folders/create-rename-move.md b/versioned_docs/version-7.x/user/ios-app/files-and-folders/create-rename-move.md
new file mode 100644
index 000000000..e715bb3f2
--- /dev/null
+++ b/versioned_docs/version-7.x/user/ios-app/files-and-folders/create-rename-move.md
@@ -0,0 +1,116 @@
+---
+sidebar_position: 1
+id: create-rename-move
+title: Create - Rename - Move
+description: Create - Rename - Move
+draft: false
+---
+
+# Create, Rename, and Move Files and Folders
+
+The OpenCloud iOS App makes it easy to manage your content. You can create new folders and files, rename items, and move them to different locations — all directly from your iPhone or iPad.
+
+## Creating Files and Folders
+
+- Tap the “+” button in the top right corner.
+
+  <img src={require("../img/files-and-folders/create-rename-move/create-new.png").default} alt="Create new" height="400"/>
+
+Choose what you want to create from the menu:
+
+### Create a Folder
+
+- Tap "Create folder"
+- Enter a name for your folder
+- Tap "Done"
+
+  <img src={require("../img/files-and-folders/create-rename-move/create-folder.png").default} alt="Create folder" height="400"/>
+
+### Create a Document (Requires Collabora)
+
+If Collabora Online is enabled in your OpenCloud instance:
+
+- Tap "New document"
+- Choose the document type (text, spreadsheet, presentation)
+- Enter a filename and confirm
+
+  <img src={require("../img/files-and-folders/create-rename-move/choose-file-type.png").default} alt="Choose file type" height="400"/>
+
+The document will open in a built-in web view using Collabora for editing.
+<img src={require("../img/files-and-folders/create-rename-move/open-collabora.png").default} alt="Open Collabora" height="400"/>
+<img src={require("../img/files-and-folders/create-rename-move/edit-collabora.png").default} alt="Edit Collabora" height="400"/>
+
+### Take Photo or Video
+
+- Select "Take photo or video" from the menu
+
+  <img src={require("../img/files-and-folders/create-rename-move/select-take-photo.png").default} alt="select take photo or video" height="400"/>
+
+- Your device camera will open
+- Capture a photo or video
+
+  <img src={require("../img/files-and-folders/create-rename-move/take-photo.png").default} alt="Take Photo" height="400"/>
+
+- The media will be saved directly to your OpenCloud account
+
+  <img src={require("../img/files-and-folders/create-rename-move/photo-saved.png").default} alt="Photo saved" height="400"/>
+
+### Scan Document
+
+Use your iOS device to scan paper documents:
+
+- Select "Scan document"
+- Point the camera at your document
+- OpenCloud will auto-detect the edges and scan it
+
+You can then:
+
+- Crop or rotate the scan
+- Switch color modes (color, grayscale, black & white)
+- Choose a file format (PDF, JPEG, PNG)
+- Save as a single-page or multi-page file
+
+The scanned document will be saved in your OpenCloud account.
+
+## Rename Files or Folders
+
+To rename a file or folder in the OpenCloud iOS App:
+
+- Tap the three dots (⋯) next to the item you want to rename
+
+  <img src={require("../img/files-and-folders/create-rename-move/three-dots.png").default} alt="Click on the three dots menu" height="400"/>
+
+- Select "Rename" from the menu
+
+  <img src={require("../img/files-and-folders/create-rename-move/select-rename.png").default} alt="Select rename" height="400"/>
+
+- Enter the new name for the file or folder
+
+  <img src={require("../img/files-and-folders/create-rename-move/enter-rename.png").default} alt="Enter the new name" height="400"/>
+
+- Tap "Done" to apply the changes
+
+  <img src={require("../img/files-and-folders/create-rename-move/tap-done.png").default} alt="Tap done" height="400"/>
+  <img src={require("../img/files-and-folders/create-rename-move/new-name-applied.png").default} alt="New applied name" height="400"/>
+
+The new name will be saved immediately.
+
+## Move Files or Folders
+
+To move a file or folder in the OpenCloud iOS App:
+
+- Tap the three dots (⋯) next to the file or folder you want to move
+
+  <img src={require("../img/files-and-folders/create-rename-move/three-dots-move.png").default} alt="Select the three dot menu" height="400"/>
+
+- Select "Cut" or "Copy" from the menu
+
+  <img src={require("../img/files-and-folders/create-rename-move/select-cut-or-copy.png").default} alt="Select cut or copy" height="400"/>
+
+- Navigate to the destination folder
+- Tap the three dots (⋯) in the destination location and select "Paste"
+
+  <img src={require("../img/files-and-folders/create-rename-move/select-paste.png").default} alt="Select paste" height="400"/>
+  <img src={require("../img/files-and-folders/create-rename-move/file-moved.png").default} alt="File is moved" height="400"/>
+
+The file or folder will now appear in the new location.
diff --git a/versioned_docs/version-7.x/user/ios-app/files-and-folders/upload-make-available-offline.md b/versioned_docs/version-7.x/user/ios-app/files-and-folders/upload-make-available-offline.md
new file mode 100644
index 000000000..709e88814
--- /dev/null
+++ b/versioned_docs/version-7.x/user/ios-app/files-and-folders/upload-make-available-offline.md
@@ -0,0 +1,60 @@
+---
+sidebar_position: 2
+id: upload-make-available-offline
+title: Upload - Make available offline
+description: Upload files in iOS
+draft: false
+---
+
+# Upload Files in iOS
+
+With the OpenCloud iOS App, you can easily upload files and make them available for offline use.
+
+## Open the Desired Folder
+
+Navigate to the folder where you want to upload a file.
+
+## The "+" Icon
+
+Tap the “+” icon in the top right corner
+
+<img src={require("../img/files-and-folders/upoload-make-available-offline/upload-plus-button.png").default} alt="Plus Button" height="400"/>
+
+## Upload options
+
+From the menu, you can choose an Upload option:
+
+- "Upload file" – upload a file from your device's Files app
+- "Upload from your photo library" – upload an existing photo or video from your media library
+
+  <img src={require("../img/files-and-folders/upoload-make-available-offline/upload-options.png").default} alt="Upload Options" height="400"/>
+
+## Confirm the Selection
+
+Choose the file or media you want to upload. The upload will start automatically.
+
+## Make Files Available Offline
+
+You can also make files available offline so they are accessible without an internet connection.
+
+- Tap the three dots (⋯) next to the file
+
+  <img src={require("../img/files-and-folders/upoload-make-available-offline/three-dots.png").default} alt="Make available offline" height="400"/>
+
+- Select “Make available offline”
+
+  <img src={require("../img/files-and-folders/upoload-make-available-offline/make-available-offline.png").default} alt="Make available offline" height="400"/>
+  The file will be downloaded and stored locally on your device.
+
+- Offline files are marked with a cloud icon with a checkmark.
+
+  <img src={require("../img/files-and-folders/upoload-make-available-offline/marked-offline.png").default} alt="Make available offline" height="400"/>
+
+## Remove Offline Availability
+
+To free up space:
+
+- Tap the three dots (⋯) again on an offline file
+- Select “Remove offline access”
+
+These features ensure you’re always prepared — even when you’re offline!
diff --git a/versioned_docs/version-7.x/user/ios-app/general/_category_.json b/versioned_docs/version-7.x/user/ios-app/general/_category_.json
new file mode 100644
index 000000000..ea225d082
--- /dev/null
+++ b/versioned_docs/version-7.x/user/ios-app/general/_category_.json
@@ -0,0 +1,10 @@
+{
+  "label": "General",
+  "position": 1,
+  "key": "ios-general",
+  "link": {
+    "type": "generated-index",
+    "description": "Tutorials about installing, setup and overview of the OpenCloud iOS App.",
+    "slug": "user/ios-app/general/"
+  }
+}
diff --git a/versioned_docs/version-7.x/user/ios-app/general/installation.md b/versioned_docs/version-7.x/user/ios-app/general/installation.md
new file mode 100644
index 000000000..d2a9304dc
--- /dev/null
+++ b/versioned_docs/version-7.x/user/ios-app/general/installation.md
@@ -0,0 +1,37 @@
+---
+sidebar_position: 1
+id: installation
+title: Install the iOS App
+description: Install the iOS App
+draft: false
+---
+
+# 📱 Installing the iOS App
+
+A short Tutorial how to install the OpenCloud iOS App.
+
+## App Store
+
+Open the App Store on your iPhone or iPad.
+
+## OpenCloud
+
+Search for "OpenCloud" or click the following link to go directly to the app:
+
+[OpenCloud on the App Store](https://apps.apple.com/de/app/opencloud-your-data-anywhere/id6743121005)
+
+<img src={require(".././img/installation/ios-installation.jpg").default} alt="iOS Installation" height="400"/>
+
+## Install
+
+Tap "Get" to install the app.
+
+## App Icon
+
+After installation, you will find the OpenCloud app on your home screen.
+
+<img src={require(".././img/installation/icon-on-screen.png").default} alt="Icon" height="400"/>
+
+## Set it up
+
+Open the app and follow the on-screen instructions to set it up.
diff --git a/versioned_docs/version-7.x/user/ios-app/general/overview/_category_.json b/versioned_docs/version-7.x/user/ios-app/general/overview/_category_.json
new file mode 100644
index 000000000..3bb03a21e
--- /dev/null
+++ b/versioned_docs/version-7.x/user/ios-app/general/overview/_category_.json
@@ -0,0 +1,10 @@
+{
+  "label": "Overview",
+  "position": 3,
+  "key": "ios-overview",
+  "link": {
+    "type": "generated-index",
+    "description": "Overview of the user interface of the OpenCloud iOS App.",
+    "slug": "user/ios-app/general/overview/"
+  }
+}
diff --git a/versioned_docs/version-7.x/user/ios-app/general/overview/account-fileslist.md b/versioned_docs/version-7.x/user/ios-app/general/overview/account-fileslist.md
new file mode 100644
index 000000000..d0580526c
--- /dev/null
+++ b/versioned_docs/version-7.x/user/ios-app/general/overview/account-fileslist.md
@@ -0,0 +1,53 @@
+---
+sidebar_position: 2
+id: account-fileslist
+title: Fileslist Menu
+description: Fileslist Menu
+draft: false
+---
+
+# Interface Overview
+
+This section explains the core interface elements of the OpenCloud iOS app and their functionality.
+
+<img src={require("../../img/overview/fileslist.png").default} alt="Fileslist-Overview" style={{ width: '400px', marginRight: '60px' }} />
+
+## 1. Account Menu
+
+Provides access to account settings.
+
+## 2. Navigation History
+
+Allows you to go back and forward through previously visited views or folders.
+
+## 3. Search
+
+Lets the user search for files, folders, or shared items within the app.
+
+## 4. Add Button
+
+Opens options to upload files, create folders, or add new content.
+
+## 5. Three Dot Menu
+
+Displays additional actions or settings related to the current view or item.
+
+## 6. Sorting
+
+Lets the user sort files by name, date, size, or other criteria.
+
+## 7. View Mode
+
+Allows switching between different view modes.
+
+## 8. Selection Toggle
+
+Enables multi-select mode to select multiple files or folders at once.
+
+## 9. Files List
+
+Shows the contents of the current folder as a list of files and folders.
+
+## 10. Breadcrumbs Menu
+
+Displays the current folder path and allows quick navigation to parent folders.
diff --git a/versioned_docs/version-7.x/user/ios-app/general/overview/account-overview.md b/versioned_docs/version-7.x/user/ios-app/general/overview/account-overview.md
new file mode 100644
index 000000000..061ce67db
--- /dev/null
+++ b/versioned_docs/version-7.x/user/ios-app/general/overview/account-overview.md
@@ -0,0 +1,57 @@
+---
+sidebar_position: 1
+id: account-overview
+title: Account Menu
+description: Account Menu
+draft: false
+---
+
+# Account Menu
+
+In the iOS app, the account menu provides access to various personal and sharing-related features.
+
+<img src={require("../../img/overview/account.png").default} alt="Fileslist-Overview" style={{ width: '400px', marginRight: '60px' }} />
+
+## 1. Account Menu Item
+
+Opens the main account options and settings.
+
+## 2. Active Account
+
+Shows which user account is currently active.
+
+## 3. Personal Space Menu Item
+
+Gives access to the user's personal files and folders.
+
+## 4. Shares Menu Item
+
+Displays files and folders that have been shared with others or received.
+
+## 5. Spaces Menu Item
+
+Opens a list of collaborative spaces or team folders.
+
+## 6. Search Menu Item
+
+Allows the user to search through files, folders, and content.
+
+## 7. Recents Menu Item
+
+Shows a list of recently accessed or modified files.
+
+## 8. Available Offline Menu Item
+
+Displays files that are marked for offline access.
+
+## 9. Status Menu Item
+
+Indicates the current sync or connection status.
+
+## 10. Add Account Menu Item
+
+Lets the user add a new account to the application.
+
+## 11. Settings Menu Item
+
+Opens the general settings and configuration options.
diff --git a/versioned_docs/version-7.x/user/ios-app/general/set-up.md b/versioned_docs/version-7.x/user/ios-app/general/set-up.md
new file mode 100644
index 000000000..0802df93f
--- /dev/null
+++ b/versioned_docs/version-7.x/user/ios-app/general/set-up.md
@@ -0,0 +1,54 @@
+---
+sidebar_position: 2
+id: set-up
+title: Set up OpenCloud iOS App
+description: Setting up your OpenCloud Account
+draft: false
+---
+
+# 🔐 Setting Up Your OpenCloud Account
+
+After installing the app, you can now set up your OpenCloud account.
+
+## Start the Setup
+
+- Tap on "Start Setup" to begin.
+- If you've already set up an account and want to add another one, tap the "+" icon located at the bottom left corner of the screen.
+
+  <img src={require(".././img/set-up/start-setup.png").default} alt="Start setup" height="400"/>
+  <img src={require(".././img/set-up/add-additional-account.png").default} alt="Add additional account" height="400"/>
+
+## Enter Your Server URL
+
+- Enter your OpenCloud Server URL (e.g., `https://cloud.example.com`)
+- Tap "Proceed" to continue.
+
+  <img src={require(".././img/set-up/enter-server-url.png").default} alt="Enter server URL" height="400"/>
+
+## Open the Login Page
+
+- Tap "Open Login Page"
+- Then tap "Continue" to launch the login page in your browser
+
+  <img src={require(".././img/set-up/open-login-page.png").default} alt="Open Login Page" height="400"/>
+  <img src={require(".././img/set-up/continue-sign-in.png").default} alt="Continue sign in" height="400"/>
+
+## Log In and Authorize Access
+
+- Log in with your OpenCloud credentials
+- Grant the app permission to access your user information and maintain continuous access
+
+  <img src={require(".././img/set-up/enter-credentials.png").default} alt="Enter Opencloud credentials" height="400"/>
+  <img src={require(".././img/set-up/grant-access.png").default} alt="Grant access" height="400"/>
+
+## Finalize Setup
+
+- Once login is complete, your account will be added to the app
+- Optionally, assign a custom display name to your account  
+  (By default, it will appear as `USERNAME@YOUR.DOMAIN`)
+
+  <img src={require(".././img/set-up/custom-name.png").default} alt="Enter custom name" height="400"/>
+
+- Your OpenCloud account is now fully set up and ready to use!
+
+  <img src={require(".././img/set-up/account-set-up.png").default} alt="Account is set up" height="400"/>
diff --git a/versioned_docs/version-7.x/user/ios-app/general/settings.md b/versioned_docs/version-7.x/user/ios-app/general/settings.md
new file mode 100644
index 000000000..041c7e526
--- /dev/null
+++ b/versioned_docs/version-7.x/user/ios-app/general/settings.md
@@ -0,0 +1,103 @@
+---
+sidebar_position: 4
+id: settings
+title: Settings
+description: Setting in OpenCloud iOS app
+draft: false
+---
+
+# Settings
+
+In the iOS app settings changes can be made, such as
+
+    - User interface
+    - Data usage
+    - Advanced settings
+    - Media files
+    and more
+
+<img src={require(".././img/settings/settings.png").default} alt="Settings" width="1920"/>
+
+## Userinterface
+
+### 1. Theme
+
+Here you can choose whether you want to run the app in "light mode" or "dark mode".
+
+### 2. Search settings
+
+Here you can specify where the search function should operate:
+
+- Folder
+- Tree
+- Space
+- Account
+- Server
+
+### 3. Logging
+
+Here you can activate and deactivate the logging function and specify the storage location of the log file.
+
+## Data Usage
+
+### 4. Cellular data usage
+
+Here you can set whether the app can be used with cellular data or not.
+
+### 5. Delete unused local copies
+
+Here you can specify when unused local copies should be deleted.
+
+## Advanced Settings
+
+### 6. Show hidden files and folders
+
+Here you can enable or disable the display of hidden files and folders.
+
+### 7. Show folders on top
+
+Here you can set whether the folders should be displayed before the files in the list view.
+
+### 8. Disable gestures
+
+Here you can disable gesture control to prevent multiple selection and dragging of files and folders.
+
+### 9. Enable diagnostics
+
+Here you can select whether the app is allowed to run diagnostics in the background.
+
+## Media Files
+
+### 10. Download instead of streaming
+
+Here you can set whether a file should be downloaded directly or streamed.
+
+### 11. Media Upload
+
+Here you can set whether certain files should be converted when uploading, such as HEIC to JPEG.
+
+## More
+
+### 12. Help & contact
+
+Here you will find links to our documentation page and help links.
+
+### 13. Recommend to a friend
+
+Here you can forward a link to download the iOS app.
+
+### 14. Privacy Policy
+
+A full entry on our privacy policy can be found here.
+
+### 15. Terms of Use
+
+You can find a full entry on our terms of use here.
+
+### 16. Acknowledgements
+
+Parts of the app may use copyrighted material, which is acknowledged here.
+
+### 17. App version
+
+Here you can see which app version is being used.
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/choose-file-type.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/choose-file-type.png
new file mode 100644
index 000000000..0e014e283
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/choose-file-type.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/create-folder.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/create-folder.png
new file mode 100644
index 000000000..ba69d2a97
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/create-folder.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/create-new.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/create-new.png
new file mode 100644
index 000000000..c925a437a
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/create-new.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/edit-collabora.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/edit-collabora.png
new file mode 100644
index 000000000..79a870c1d
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/edit-collabora.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/enter-rename.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/enter-rename.png
new file mode 100644
index 000000000..6023a359d
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/enter-rename.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/file-moved.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/file-moved.png
new file mode 100644
index 000000000..df5c8fe32
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/file-moved.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/new-name-applied.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/new-name-applied.png
new file mode 100644
index 000000000..3c9a42233
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/new-name-applied.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/open-collabora.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/open-collabora.png
new file mode 100644
index 000000000..890e17a71
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/open-collabora.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/photo-saved.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/photo-saved.png
new file mode 100644
index 000000000..651c303f0
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/photo-saved.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-cut-or-copy.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-cut-or-copy.png
new file mode 100644
index 000000000..36e6376b6
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-cut-or-copy.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-paste.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-paste.png
new file mode 100644
index 000000000..55ea34e2d
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-paste.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-rename.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-rename.png
new file mode 100644
index 000000000..3555bd608
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-rename.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-take-photo.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-take-photo.png
new file mode 100644
index 000000000..776241fc7
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/select-take-photo.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/take-photo.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/take-photo.png
new file mode 100644
index 000000000..9c82a0645
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/take-photo.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/tap-done.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/tap-done.png
new file mode 100644
index 000000000..cc09b6957
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/tap-done.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/three-dots-move.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/three-dots-move.png
new file mode 100644
index 000000000..5005f980f
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/three-dots-move.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/three-dots.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/three-dots.png
new file mode 100644
index 000000000..f26842895
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/create-rename-move/three-dots.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/make-available-offline.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/make-available-offline.png
new file mode 100644
index 000000000..c7f66a588
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/make-available-offline.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/marked-offline.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/marked-offline.png
new file mode 100644
index 000000000..6a414eaae
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/marked-offline.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/three-dots.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/three-dots.png
new file mode 100644
index 000000000..200f2d4f1
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/three-dots.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/upload-options.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/upload-options.png
new file mode 100644
index 000000000..ee3c63a76
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/upload-options.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/upload-plus-button.png b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/upload-plus-button.png
new file mode 100644
index 000000000..f2a7ceeff
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/files-and-folders/upoload-make-available-offline/upload-plus-button.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/installation/icon-on-screen.png b/versioned_docs/version-7.x/user/ios-app/img/installation/icon-on-screen.png
new file mode 100644
index 000000000..fdbece62f
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/installation/icon-on-screen.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/installation/ios-installation.jpg b/versioned_docs/version-7.x/user/ios-app/img/installation/ios-installation.jpg
new file mode 100644
index 000000000..70eaa1864
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/installation/ios-installation.jpg differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/overview/account.png b/versioned_docs/version-7.x/user/ios-app/img/overview/account.png
new file mode 100644
index 000000000..ffd976234
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/overview/account.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/overview/fileslist.png b/versioned_docs/version-7.x/user/ios-app/img/overview/fileslist.png
new file mode 100644
index 000000000..cf8773d83
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/overview/fileslist.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/search/date.png b/versioned_docs/version-7.x/user/ios-app/img/search/date.png
new file mode 100644
index 000000000..c4a31e2bc
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/search/date.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/search/save-search.png b/versioned_docs/version-7.x/user/ios-app/img/search/save-search.png
new file mode 100644
index 000000000..63f439b26
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/search/save-search.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/search/search-location.png b/versioned_docs/version-7.x/user/ios-app/img/search/search-location.png
new file mode 100644
index 000000000..b2084313e
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/search/search-location.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/search/search-result.png b/versioned_docs/version-7.x/user/ios-app/img/search/search-result.png
new file mode 100644
index 000000000..551f4f7b2
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/search/search-result.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/search/search-symbol.png b/versioned_docs/version-7.x/user/ios-app/img/search/search-symbol.png
new file mode 100644
index 000000000..3ecbd4991
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/search/search-symbol.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/search/searchbar.png b/versioned_docs/version-7.x/user/ios-app/img/search/searchbar.png
new file mode 100644
index 000000000..755fa9050
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/search/searchbar.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/search/type.png b/versioned_docs/version-7.x/user/ios-app/img/search/type.png
new file mode 100644
index 000000000..72d249a63
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/search/type.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/set-up/account-set-up.png b/versioned_docs/version-7.x/user/ios-app/img/set-up/account-set-up.png
new file mode 100644
index 000000000..aa142aff0
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/set-up/account-set-up.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/set-up/add-additional-account.png b/versioned_docs/version-7.x/user/ios-app/img/set-up/add-additional-account.png
new file mode 100644
index 000000000..e3ecc6c06
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/set-up/add-additional-account.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/set-up/continue-sign-in.png b/versioned_docs/version-7.x/user/ios-app/img/set-up/continue-sign-in.png
new file mode 100644
index 000000000..a27e83842
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/set-up/continue-sign-in.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/set-up/custom-name.png b/versioned_docs/version-7.x/user/ios-app/img/set-up/custom-name.png
new file mode 100644
index 000000000..056a6225f
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/set-up/custom-name.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/set-up/enter-credentials.png b/versioned_docs/version-7.x/user/ios-app/img/set-up/enter-credentials.png
new file mode 100644
index 000000000..582b805f8
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/set-up/enter-credentials.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/set-up/enter-server-url.png b/versioned_docs/version-7.x/user/ios-app/img/set-up/enter-server-url.png
new file mode 100644
index 000000000..90af12a67
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/set-up/enter-server-url.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/set-up/grant-access.png b/versioned_docs/version-7.x/user/ios-app/img/set-up/grant-access.png
new file mode 100644
index 000000000..409d56dc2
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/set-up/grant-access.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/set-up/open-login-page.png b/versioned_docs/version-7.x/user/ios-app/img/set-up/open-login-page.png
new file mode 100644
index 000000000..195e33502
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/set-up/open-login-page.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/set-up/start-setup.png b/versioned_docs/version-7.x/user/ios-app/img/set-up/start-setup.png
new file mode 100644
index 000000000..69ab090f6
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/set-up/start-setup.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/settings/settings.png b/versioned_docs/version-7.x/user/ios-app/img/settings/settings.png
new file mode 100644
index 000000000..93fc10aba
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/settings/settings.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shares/invite/choose-invites.png b/versioned_docs/version-7.x/user/ios-app/img/shares/invite/choose-invites.png
new file mode 100644
index 000000000..0a632fc7d
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shares/invite/choose-invites.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shares/invite/invite-button.png b/versioned_docs/version-7.x/user/ios-app/img/shares/invite/invite-button.png
new file mode 100644
index 000000000..a4ae9d18f
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shares/invite/invite-button.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shares/invite/invite-menue.png b/versioned_docs/version-7.x/user/ios-app/img/shares/invite/invite-menue.png
new file mode 100644
index 000000000..13c5854a7
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shares/invite/invite-menue.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shares/invite/invite-option.png b/versioned_docs/version-7.x/user/ios-app/img/shares/invite/invite-option.png
new file mode 100644
index 000000000..d5f398baf
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shares/invite/invite-option.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shares/invite/permissions.png b/versioned_docs/version-7.x/user/ios-app/img/shares/invite/permissions.png
new file mode 100644
index 000000000..3848f49ae
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shares/invite/permissions.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shares/invite/searchbar.png b/versioned_docs/version-7.x/user/ios-app/img/shares/invite/searchbar.png
new file mode 100644
index 000000000..f7aa1ecf0
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shares/invite/searchbar.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shares/invite/shared-with.png b/versioned_docs/version-7.x/user/ios-app/img/shares/invite/shared-with.png
new file mode 100644
index 000000000..80566d860
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shares/invite/shared-with.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shares/invite/sharing-button.png b/versioned_docs/version-7.x/user/ios-app/img/shares/invite/sharing-button.png
new file mode 100644
index 000000000..cb96657d0
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shares/invite/sharing-button.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shares/invite/three-dot-menue.png b/versioned_docs/version-7.x/user/ios-app/img/shares/invite/three-dot-menue.png
new file mode 100644
index 000000000..fb1ec63ec
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shares/invite/three-dot-menue.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shares/links/create-link-button.png b/versioned_docs/version-7.x/user/ios-app/img/shares/links/create-link-button.png
new file mode 100644
index 000000000..9b38d54ae
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shares/links/create-link-button.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shares/links/create-link-options.png b/versioned_docs/version-7.x/user/ios-app/img/shares/links/create-link-options.png
new file mode 100644
index 000000000..e126b5de6
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shares/links/create-link-options.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shares/links/created-link.png b/versioned_docs/version-7.x/user/ios-app/img/shares/links/created-link.png
new file mode 100644
index 000000000..233aa0124
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shares/links/created-link.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shares/links/expiration-date.png b/versioned_docs/version-7.x/user/ios-app/img/shares/links/expiration-date.png
new file mode 100644
index 000000000..33eda696c
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shares/links/expiration-date.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shares/links/link-name.png b/versioned_docs/version-7.x/user/ios-app/img/shares/links/link-name.png
new file mode 100644
index 000000000..3f70f6c0b
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shares/links/link-name.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shares/links/password.png b/versioned_docs/version-7.x/user/ios-app/img/shares/links/password.png
new file mode 100644
index 000000000..b6814c107
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shares/links/password.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shares/links/share-button.png b/versioned_docs/version-7.x/user/ios-app/img/shares/links/share-button.png
new file mode 100644
index 000000000..ac909edf7
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shares/links/share-button.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shares/links/sharing-button.png b/versioned_docs/version-7.x/user/ios-app/img/shares/links/sharing-button.png
new file mode 100644
index 000000000..cb96657d0
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shares/links/sharing-button.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shares/links/sharing-options.png b/versioned_docs/version-7.x/user/ios-app/img/shares/links/sharing-options.png
new file mode 100644
index 000000000..05f86cd45
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shares/links/sharing-options.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shares/links/three-dot-menue.png b/versioned_docs/version-7.x/user/ios-app/img/shares/links/three-dot-menue.png
new file mode 100644
index 000000000..fb1ec63ec
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shares/links/three-dot-menue.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shortcuts/choose-file-or-folder.png b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/choose-file-or-folder.png
new file mode 100644
index 000000000..ff7c3266a
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/choose-file-or-folder.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shortcuts/create-shortcut-button.png b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/create-shortcut-button.png
new file mode 100644
index 000000000..de479b955
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/create-shortcut-button.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shortcuts/create-shortcut.png b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/create-shortcut.png
new file mode 100644
index 000000000..a55ff6ed3
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/create-shortcut.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shortcuts/created-shortcut.png b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/created-shortcut.png
new file mode 100644
index 000000000..ccf7a2b88
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/created-shortcut.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shortcuts/pick-file-or-folder.png b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/pick-file-or-folder.png
new file mode 100644
index 000000000..3f2a0899f
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/pick-file-or-folder.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shortcuts/plus-button.png b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/plus-button.png
new file mode 100644
index 000000000..d66a0b336
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/plus-button.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shortcuts/plus-menue.png b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/plus-menue.png
new file mode 100644
index 000000000..9247ed80c
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/plus-menue.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shortcuts/select-button.png b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/select-button.png
new file mode 100644
index 000000000..18ab749bf
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/select-button.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shortcuts/shortcut-menue.png b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/shortcut-menue.png
new file mode 100644
index 000000000..f65abb1d0
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/shortcut-menue.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shortcuts/shortcut-name.png b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/shortcut-name.png
new file mode 100644
index 000000000..7673f7fa5
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/shortcut-name.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/shortcuts/url.png b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/url.png
new file mode 100644
index 000000000..2e455795e
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/shortcuts/url.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/spaces/Search-menue.png b/versioned_docs/version-7.x/user/ios-app/img/spaces/Search-menue.png
new file mode 100644
index 000000000..3aff88663
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/spaces/Search-menue.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/spaces/plus-symbol.png b/versioned_docs/version-7.x/user/ios-app/img/spaces/plus-symbol.png
new file mode 100644
index 000000000..a8bb6ed5f
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/spaces/plus-symbol.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/spaces/search-button.png b/versioned_docs/version-7.x/user/ios-app/img/spaces/search-button.png
new file mode 100644
index 000000000..5893e8bae
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/spaces/search-button.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/spaces/spaces-button.png b/versioned_docs/version-7.x/user/ios-app/img/spaces/spaces-button.png
new file mode 100644
index 000000000..8f44b7e19
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/spaces/spaces-button.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/spaces/spaces-functions.png b/versioned_docs/version-7.x/user/ios-app/img/spaces/spaces-functions.png
new file mode 100644
index 000000000..60db08662
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/spaces/spaces-functions.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/spaces/spaces-overview.png b/versioned_docs/version-7.x/user/ios-app/img/spaces/spaces-overview.png
new file mode 100644
index 000000000..0973862ff
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/spaces/spaces-overview.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/img/spaces/three-point-menue.png b/versioned_docs/version-7.x/user/ios-app/img/spaces/three-point-menue.png
new file mode 100644
index 000000000..e6e214bdc
Binary files /dev/null and b/versioned_docs/version-7.x/user/ios-app/img/spaces/three-point-menue.png differ
diff --git a/versioned_docs/version-7.x/user/ios-app/index.md b/versioned_docs/version-7.x/user/ios-app/index.md
new file mode 100644
index 000000000..ea003f13e
--- /dev/null
+++ b/versioned_docs/version-7.x/user/ios-app/index.md
@@ -0,0 +1,29 @@
+---
+sidebar_position: 0
+id: ios-app-overview
+title: OpenCloud iOS App
+---
+
+# OpenCloud iOS App
+
+The OpenCloud iOS app provides mobile access to your files, Spaces, and shares on iPhone and iPad. It is designed for everyday tasks such as setup, searching, sharing, and making files available offline.
+
+## In this section
+
+- [General](./general/)  
+  Install the app, complete the initial setup, and learn the main interface and settings.
+
+- [Files and folders](./files-and-folders/)  
+  Create and edit content, upload files, and make items available offline.
+
+- [Spaces](./spaces.md)  
+  Work with Spaces and use the available Space actions in the iOS app.
+
+- [Search](./search.md)  
+  Find files and folders from within the iOS app.
+
+- [Shortcuts](./shortcuts.md)  
+  Create shortcuts to files or web links.
+
+- [Shares](./shares/)  
+  Invite people and create share links from the iOS app.
diff --git a/versioned_docs/version-7.x/user/ios-app/search.md b/versioned_docs/version-7.x/user/ios-app/search.md
new file mode 100644
index 000000000..e5efab204
--- /dev/null
+++ b/versioned_docs/version-7.x/user/ios-app/search.md
@@ -0,0 +1,72 @@
+---
+sidebar_position: 4
+id: search
+title: Search
+description: Search
+draft: false
+---
+
+# Search function
+
+Here we explain how to use the search function in the OpenCloud iOS app
+
+## Search Icon
+
+- Click on the search icon to open the search function
+
+  <img src={require("./img/search/search-symbol.png").default} alt="Magnifying glass icon" height="400"/>
+
+## Search function
+
+- The search function offers various options that can be used to narrow down your search
+
+## Search bar
+
+- You can search for file or folder names in the search bar.
+
+  <img src={require("./img/search/searchbar.png").default} alt="Search bar" height="400"/>
+
+## Search Location
+
+By clicking the option to the left of the search bar, you can specify where the search function should operate.
+
+- Folder:  
+  Searches only in the current folder.
+- Tree:  
+  Searches in the current folder and all subfolders within it.
+- Space:  
+  Searches the current space, including all folders and subfolders within it.
+- Account:  
+  Searches the entire logged-in account, including all spaces, folders, and subfolders.
+- Server:  
+  Searches the entire server.
+
+  <img src={require("./img/search/search-location.png").default} alt="Search location" height="400"/>
+
+## Type
+
+- By clicking on the option "Type", you can set which file type should be searched for
+
+  <img src={require("./img/search/type.png").default} alt="File type" height="400"/>
+
+## Date
+
+- By clicking on the option "date", you can set the period in which you want to search
+
+  <img src={require("./img/search/date.png").default} alt="Date" height="400"/>
+
+## Size
+
+- By clicking on the "Size" option, you can set the file size to search for
+
+## Save search
+
+- By clicking on the "circle symbol" with the three dots in it, you can save the current search
+
+  <img src={require("./img/search/save-search.png").default} alt="Save search" height="400"/>
+
+## Search result
+
+- This area displays the search results
+
+  <img src={require("./img/search/search-result.png").default} alt="Search results" height="400"/>
diff --git a/versioned_docs/version-7.x/user/ios-app/shares/_category_.json b/versioned_docs/version-7.x/user/ios-app/shares/_category_.json
new file mode 100644
index 000000000..f07b051a1
--- /dev/null
+++ b/versioned_docs/version-7.x/user/ios-app/shares/_category_.json
@@ -0,0 +1,10 @@
+{
+    "label": "Shares",
+    "position": 3,
+    "key": "ios-shares",
+    "link": {
+      "type": "generated-index",
+      "description": "Tutorials about creating shares the OpenCloud iOS App.",
+      "slug": "user/ios-app/shares/"
+    }
+  }
\ No newline at end of file
diff --git a/versioned_docs/version-7.x/user/ios-app/shares/invite.md b/versioned_docs/version-7.x/user/ios-app/shares/invite.md
new file mode 100644
index 000000000..93acbed15
--- /dev/null
+++ b/versioned_docs/version-7.x/user/ios-app/shares/invite.md
@@ -0,0 +1,61 @@
+---
+sidebar_position: 1
+id: invite
+title: Invite to share
+description: Invite to share
+draft: false
+---
+
+# Share files and folders with people and groups via invitation
+
+Here we explain how to share files and folders via invitation with other people and groups within your OpenCloud in the OpenCloud iOS app
+
+## Three-dot-menu
+
+- Click the "three-dot menu" next to the file or folder
+
+  <img src={require("../img/shares/invite/three-dot-menue.png").default} alt="Three-dot menu" height="400"/>
+
+## Share
+
+- Now select the menu item "Share"
+
+  <img src={require("../img/shares/invite/sharing-button.png").default} alt="share" height="400"/>
+
+## Share with
+
+- In the following selection, click on "Share with"
+
+  <img src={require("../img/shares/invite/invite-option.png").default} alt="Share with" height="400"/>
+
+## Share menu
+
+- The Share menu opens, where you can use the search bar to search for people or groups you want to invite
+
+  <img src={require("../img/shares/invite/invite-menue.png").default} alt="Share with menu" height="400"/>
+  <img src={require("../img/shares/invite/searchbar.png").default} alt="Search bar" height="400"/>
+  <img src={require("../img/shares/invite/choose-invites.png").default} alt="Selection of people and/or groups" height="400"/>
+
+## Permissions
+
+- Here you can select which permissions people and groups should have:
+
+  <img src={require("../img/shares/invite/permissions.png").default} alt="permissions" height="400"/>
+  - Can View:  
+    People can only view and download content, but not edit, create, or upload it.
+  - Can Edit:  
+    People can view, download, upload, edit, and create files.
+  - Custom:  
+    Permissions can be individually selected here.
+
+## Invite
+
+- To create the link you must click on "Invite"
+
+  <img src={require("../img/shares/invite/invite-button.png").default} alt="Invite" height="400"/>
+
+## Created
+
+- Once the invitation is created, you will see it in the file or folder overview
+
+  <img src={require("../img/shares/invite/shared-with.png").default} alt="Shared with" height="400"/>
diff --git a/versioned_docs/version-7.x/user/ios-app/shares/links.md b/versioned_docs/version-7.x/user/ios-app/shares/links.md
new file mode 100644
index 000000000..c6538cfe9
--- /dev/null
+++ b/versioned_docs/version-7.x/user/ios-app/shares/links.md
@@ -0,0 +1,81 @@
+---
+sidebar_position: 2
+id: links
+title: Share via link
+description: Share via link
+draft: false
+---
+
+# Share files and folders via link
+
+Here we explain how to share files and folders with others via link in the OpenCloud iOS app
+
+## Three-dot-menu
+
+- Click the three-dot menu next to the file or folder
+
+  <img src={require("../img/shares/links/three-dot-menue.png").default} alt="Three-dot menu" height="400"/>
+
+## Share
+
+- Now select the menu item “Share”
+
+  <img src={require("../img/shares/links/sharing-button.png").default} alt="Share" height="400"/>
+
+## Create link
+
+- In the following selection, click on "Create link"
+
+  <img src={require("../img/shares/links/create-link-button.png").default} alt="Create link" height="400"/>
+
+## Options
+
+- Here you can select and specify several options for the link to be created
+
+  <img src={require("../img/shares/links/create-link-options.png").default} alt="Overview link menu" height="400"/>
+
+## Link name
+
+- Enter a name for your link here
+
+  <img src={require("../img/shares/links/link-name.png").default} alt="Linkname" height="400"/>
+
+## Link functions
+
+- Here you can select which function your link should have:
+
+  <img src={require("../img/shares/links/sharing-options.png").default} alt="Share options" height="400"/>
+  - Invite people:
+    Only invited people have access to the link and its content.
+  - Can View:
+    People can only view and download the content of the link, but not edit, create, or upload.
+  - Can Upload:
+    People can only view the content of the link and upload files, but not edit or create them.
+  - Can Manage:
+    People can only view, download, and upload files, but not edit or create them.
+  - Can Edit:
+    People can view, download, upload, edit, and create the content of the link.
+
+## Password
+
+- You must enter a password here. You can choose your own or have one generated for you
+
+  <img src={require("../img/shares/links/password.png").default} alt="Password" height="400"/>
+
+## Period of available
+
+- Here you can specify a period of time for which the link should be available
+
+  <img src={require("../img/shares/links/expiration-date.png").default} alt="Link expiration date" height="400"/>
+
+## Create
+
+- To create the link you must now click on "Share"
+
+  <img src={require("../img/shares/links/share-button.png").default} alt="Share" height="400"/>
+
+## Created link
+
+- Once the link is created, you will see it with the assigned name in the file or folder overview
+
+  <img src={require("../img/shares/links/created-link.png").default} alt="Created link" height="400"/>
diff --git a/versioned_docs/version-7.x/user/ios-app/shortcuts.md b/versioned_docs/version-7.x/user/ios-app/shortcuts.md
new file mode 100644
index 000000000..c2fa5bbbe
--- /dev/null
+++ b/versioned_docs/version-7.x/user/ios-app/shortcuts.md
@@ -0,0 +1,67 @@
+---
+sidebar_position: 5
+id: shortcuts
+title: Shortcut in the OpenCloud iOS app
+description: Shortcuts in OpenCloud iOS app
+draft: false
+---
+
+# Shortcut in the OpenCloud iOS app
+
+Here we show you how to create shortcuts in the iOS app
+
+## "+" Icon
+
+- Click on the "+" Icon
+
+  <img src={require("./img/shortcuts/plus-button.png").default} alt="Plus symbol" height="400"/>
+
+## Drop-Down menu
+
+- A drop-down menu opens
+
+  <img src={require("./img/shortcuts/plus-menue.png").default} alt="Drop-down menu" height="400"/>
+
+## Create shortcut
+
+- Select "Create shortcut"
+
+  <img src={require("./img/shortcuts/create-shortcut.png").default} alt="Select create shortcut" height="400"/>
+
+## Shortcut options
+
+-A menu opens with options for shortcuts
+
+<img src={require("./img/shortcuts/shortcut-menue.png").default} alt="Shortcut menu" height="400"/>
+
+## URL
+
+- To create a shortcut to a website, enter the address of the website under "URL"
+
+  <img src={require("./img/shortcuts/url.png").default} alt="URL" height="400"/>
+
+## Select files and folder
+
+- To create a shortcut to a file or folder in OpenCloud, click the "Select file or folder" option
+
+  <img src={require("./img/shortcuts/pick-file-or-folder.png").default} alt="Select file or folder option" height="400"/>
+  <img src={require("./img/shortcuts/choose-file-or-folder.png").default} alt="Select file or folder" height="400"/>
+  <img src={require("./img/shortcuts/select-button.png").default} alt="Select" height="400"/>
+
+## Shortcut name
+
+- Here you enter a name for the shortcut with which it will be displayed
+
+  <img src={require("./img/shortcuts/shortcut-name.png").default} alt="Name of the shortcut" height="400"/>
+
+## Create button
+
+- To create the shortcut, click on "Create shortcut"
+
+  <img src={require("./img/shortcuts/create-shortcut-button.png").default} alt="Create shortcut" height="400"/>
+
+## Created shortcut
+
+- Your created shortcut is now displayed and can be used
+
+  <img src={require("./img/shortcuts/created-shortcut.png").default} alt="Shortcut" height="400"/>
diff --git a/versioned_docs/version-7.x/user/ios-app/spaces.md b/versioned_docs/version-7.x/user/ios-app/spaces.md
new file mode 100644
index 000000000..2d6cd9eae
--- /dev/null
+++ b/versioned_docs/version-7.x/user/ios-app/spaces.md
@@ -0,0 +1,75 @@
+---
+sidebar_position: 6
+id: spaces
+title: Spaces
+description: Spaces in OpenCloud iOS app
+draft: false
+---
+
+# The "Spaces" Section in the OpenCloud iOS app
+
+The "Spaces" section provides a central place for collaboration in groups or teams. In a Space, multiple users can access files and folders together, organize content, and track changes
+
+## Spaces Overview
+
+To open the Spaces Overview, tap the "Spaces button" in the account menu.
+
+<img src={require("./img/spaces/spaces-button.png").default} alt="Spaces Button" style={{ width: '300px', marginRight: '60px' }} />
+
+Afterwards, the Spaces Overview appears, listing all Spaces you are a member of or have created yourself.
+
+<img src={require("./img/spaces/spaces-overview.png").default} alt="Spaces Overview" style={{ width: '300px', marginRight: '60px' }} />
+
+## Search Function
+
+By tapping the search icon, the search menue for Spaces will open.
+
+<img src={require("./img/spaces/search-button.png").default} alt="Search Function" style={{ width: '300px', marginRight: '60px' }} />
+
+<img src={require("./img/spaces/Search-menue.png").default} alt="Search Menu" style={{ width: '300px', marginRight: '60px' }} />
+
+## Functions within a Space
+
+By tapping the plus icon, the available functions within a Space appear.
+
+<img src={require("./img/spaces/plus-symbol.png").default} alt="Plus Icon" style={{ width: '300px', marginRight: '60px' }} />
+
+<img src={require("./img/spaces/spaces-functions.png").default} alt="Functions in Spaces" style={{ width: '400px', marginRight: '60px' }} />
+
+## Add Menu
+
+The add menu in the iOS app allows users to create and upload content directly into a Space.
+
+### 1. Create Folder
+
+Create new folders to organize and structure content clearly.
+
+### 2. New Document
+
+Create a new document directly within the Space without using a separate app.
+
+### 3. Upload Files
+
+Select files from your device and upload them to the Space.
+
+### 4. Upload from Library
+
+Access your iOS photo library and upload images or videos directly to the Space.
+
+### 5. Take Photo or Video
+
+Use your iOS camera to take pictures or videos and upload them directly to the Space.
+
+### 6. Create Shortcut
+
+Create a shortcut to a file or folder within the Space for quick access.
+
+### 7. Scan Document
+
+Use your device camera to scan physical documents and save them directly as PDFs in the Space.
+
+## "Three-Dot Menue"
+
+By tapping the three-dot menu, a pop-up menu opens where you can choose to make the Space available offline.
+
+<img src={require("./img/spaces/three-point-menue.png").default} alt="Three-Dot Menu" style={{ width: '300px', marginRight: '60px' }} />
diff --git a/versioned_docs/version-7.x/user/roles/_category_.json b/versioned_docs/version-7.x/user/roles/_category_.json
new file mode 100644
index 000000000..3f2dbc1b8
--- /dev/null
+++ b/versioned_docs/version-7.x/user/roles/_category_.json
@@ -0,0 +1,8 @@
+{
+  "label": "Roles",
+  "position": 8,
+  "link": {
+    "type": "doc",
+    "id": "roles-overview"
+  }
+}
diff --git a/versioned_docs/version-7.x/user/roles/index.md b/versioned_docs/version-7.x/user/roles/index.md
new file mode 100644
index 000000000..3a5defd92
--- /dev/null
+++ b/versioned_docs/version-7.x/user/roles/index.md
@@ -0,0 +1,20 @@
+---
+sidebar_position: 0
+id: roles-overview
+title: Roles
+---
+
+# Roles
+
+This section explains the role models used in OpenCloud. It covers general user roles, the permissions available within Spaces, and the access levels that can be assigned when sharing files and folders.
+
+## In this section
+
+- [User roles](./user-roles.md)  
+  Learn about the available user roles in OpenCloud, including Admin, Space Admin, User, and User Light.
+
+- [Space roles](./space-roles.md)  
+  Understand the permissions available within a Space, including Can View, Can Edit, and Can Manage.
+
+- [Share roles](./share-roles.md)  
+  Review the access levels available when sharing files and folders.
diff --git a/versioned_docs/version-7.x/user/roles/share-roles.md b/versioned_docs/version-7.x/user/roles/share-roles.md
new file mode 100644
index 000000000..a5d5dc456
--- /dev/null
+++ b/versioned_docs/version-7.x/user/roles/share-roles.md
@@ -0,0 +1,42 @@
+---
+sidebar_position: 3
+id: share-roles
+title: Share roles in OpenCloud
+description: Share roles in OpenCloud
+draft: false
+---
+
+# Sharing Roles in OpenCloud
+
+| Role              | view | download | upload | edit | add | delete | only view doc, img, pdf with watermark |
+| :---------------- | :--: | :------: | :----: | :--: | :-: | :----: | :------------------------------------: |
+| can view (secure) |  -   |    -     |   -    |  -   |  -  |   -    |                   x                    |
+| can view          |  x   |    x     |   -    |  -   |  -  |   -    |                   -                    |
+| can upload        |  x   |    x     |   x    |  -   |  -  |   -    |                   -                    |
+| can edit          |  x   |    x     |   x    |  x   |  x  |   x    |                   -                    |
+
+## Space Member Roles and Permissions
+
+In a Space, members can have different roles that determine what they can do with shared files and folders.
+
+### Can View (Secure)
+
+- You can only view documents, pictures, and PDFs.
+- A watermark is added to the files.
+- Downloading is not allowed.
+
+### Can View
+
+- You can view and download files and folders.
+- No restrictions on downloading.
+
+### Can Upload
+
+- You can view, download, and upload files and folders.
+
+### Can Edit
+
+- You can edit, add, and delete files and folders.
+- Full access to modify shared content.
+
+Each role gives a different level of access, ensuring the right permissions for each user!
diff --git a/versioned_docs/version-7.x/user/roles/space-roles.md b/versioned_docs/version-7.x/user/roles/space-roles.md
new file mode 100644
index 000000000..308cf4b28
--- /dev/null
+++ b/versioned_docs/version-7.x/user/roles/space-roles.md
@@ -0,0 +1,44 @@
+---
+sidebar_position: 2
+id: space-roles
+title: Space roles in OpenCloud
+description: Space roles in OpenCloud
+draft: false
+---
+
+# Space Roles in OpenCloud
+
+| Role       | view | download | upload | edit | add | delete | manage members | disable / enable Space | edit quota | delete Space |
+| :--------- | :--: | :------: | :----: | :--: | :-: | :----: | :------------: | :--------------------: | :--------: | :----------: |
+| can view   |  x   |    x     |   -    |  -   |  -  |   -    |       -        |           -            |     -      |      -       |
+| can edit   |  x   |    x     |   x    |  x   |  x  |   x    |       -        |           -            |     -      |      -       |
+| can manage |  x   |    x     |   x    |  x   |  x  |   x    |       x        |           x            |     x      |      x       |
+
+## Space Roles and Permissions
+
+In a Space, members can have different roles that give them different levels of access.
+
+### Can View
+
+This role allows the member to view and download files in the Space, but they cannot make any changes, upload or create new files and folders.
+
+### Can Edit
+
+With this role, the member can do everything a "Can View" member can do, plus:
+
+- Upload files to the Space
+- Create new files and folders
+- Delete files and folders, including their history
+- Restore deleted files
+
+### Can Manage
+
+This role gives the member all the abilities of "Can Edit," plus:
+
+- Add or remove members from the Space
+- Change the roles of other members in the Space
+- Enable and disable the Space
+- Edit the quota of the Space
+- Delete the Space
+
+Each role determines what a member can do within the Space!
diff --git a/versioned_docs/version-7.x/user/roles/user-roles.md b/versioned_docs/version-7.x/user/roles/user-roles.md
new file mode 100644
index 000000000..478d67672
--- /dev/null
+++ b/versioned_docs/version-7.x/user/roles/user-roles.md
@@ -0,0 +1,75 @@
+---
+sidebar_position: 1
+id: user-roles
+title: User roles in OpenCloud
+description: User roles in OpenCloud
+draft: false
+---
+
+# User Roles in OpenCloud
+
+| Role        | Personal Space | create Spaces | can be Space Manager | manage Users and Groups |
+| :---------- | :------------: | :-----------: | :------------------: | :---------------------: |
+| Admin       |       x        |       x       |          x           |            x            |
+| Space Admin |       x        |       x       |          x           |            -            |
+| User        |       x        |       -       |          x           |            -            |
+| User Light  |       -        |       -       |          x           |            -            |
+
+## Admin
+
+The Administrator role in OpenCloud has the same abilities as a Space Admin but in addition it has special permissions to manage users, groups, and system settings.
+However, administrators do not have direct access to Space data or the ability to add users to Spaces where they don't have the "can manage" role. Below are the key actions an administrator can perform:
+
+- Create and Delete local Users & Groups
+
+Administrators can add new local users and remove existing local users from the system.
+They can also create and delete local groups to organize users efficiently.
+
+- Edit Users & Groups
+
+User details such as names, emails, and roles can be modified.
+Groups can be updated by adding or removing members as needed.
+
+- Prevent Login
+
+If necessary, administrators can disable user accounts, preventing them from logging in.
+This is useful for security reasons or when an account is no longer needed.
+
+- Manage Spaces (without Access to Space Data)
+
+Administrators can manage Spaces like enable, disable or delete them and rename it or adjust the quota, even if they don't have the "can manage" role.
+However, they cannot access the files inside a Space or add members to it.
+
+- Change the Logo
+
+The system logo can be updated to reflect the company branding.
+This can be done in the Admin Settings under the "General" section.
+
+## Space Admin
+
+A Space Admin has the highest level of control over Spaces. They can:
+
+- Create and manage Spaces
+- Be assigned the "Can Edit" role in Spaces they didn’t create
+- Have a personal Space where they can create files, folders, and upload data
+
+## User
+
+A regular User has access to their own Space and can be part of other Spaces. They can:
+
+- Create files and folders in their personal Space
+- Upload and manage their own data
+- Be added as a member to a Space
+- Can have the "Can Edit" role in a Space
+
+## User Light
+
+A User Light has limited access and does not have their own personal Space. They can:
+
+- Be added as a member to a Space
+- Can have the "Can Edit" role in a Space
+- They do not have a personal Space
+
+:::note
+If a user previously had the role User or higher and is later changed back to User Light, they will still keep their personal Space.
+:::
diff --git a/versioned_docs/version-7.x/user/sharing/_category_.json b/versioned_docs/version-7.x/user/sharing/_category_.json
new file mode 100644
index 000000000..ca042f2f1
--- /dev/null
+++ b/versioned_docs/version-7.x/user/sharing/_category_.json
@@ -0,0 +1,8 @@
+{
+  "label": "Share files and folders",
+  "position": 4,
+  "link": {
+    "type": "doc",
+    "id": "sharing-overview"
+  }
+}
diff --git a/versioned_docs/version-7.x/user/sharing/external.md b/versioned_docs/version-7.x/user/sharing/external.md
new file mode 100644
index 000000000..526938e7a
--- /dev/null
+++ b/versioned_docs/version-7.x/user/sharing/external.md
@@ -0,0 +1,51 @@
+---
+sidebar_position: 2
+id: external
+title: External
+description: External sharing of files and folders in OpenCloud
+draft: false
+---
+
+# Public links - external sharing of files and folders in OpenCloud
+
+Public links let you share files and folders with people outside your organization.
+
+## Steps to create a public link
+
+- Right-click the file or folder, or click the three-dot menu next to its name, to open the context menu.
+- Select “Share” from the context menu.
+
+  <img src={require("./img/extern/share-drop-down-menu.png").default} alt="Select share" width="1920"/>
+
+- A sidebar window will open on the right-hand side of the screen.
+  <img src={require("./img/extern/sidebar-window.png").default} alt="Sidebar window" width="400"/>
+
+- Click “Add link” to open the link configuration window.
+
+  <img src={require("./img/extern/public-link-option-pop-up.png").default} alt="Pop up window" width="1920"/>
+
+- Click “Options” to configure the link.
+- Select the desired access rights for recipients:
+  - “Can view":  
+    Recipients can view and download the file, but cannot edit it or upload files.
+  - “Can edit":  
+    Recipients can view, download, edit and delete the file, and upload files to the folder.
+  - “File Drop (secret)":  
+    Recipients can only upload files. They cannot view or edit the content.
+
+    <img src={require("./img/extern/access-rights.png").default} alt="Access rights" width="1920"/>
+
+- Enter a password in the field under “Password”. A password is required, unless an administrator has changed the setting.
+- Optionally, set an expiry date.
+- After you have configured the link options, click “Copy link” to create and copy the public link.
+  To include the password, open the menu next to “Copy link” and select “Copy link and password”.
+  <img src={require("./img/extern/password-section.png").default} alt="Password section" width="1920"/>
+
+- The link is now created and can be shared with recipients.
+  <img src={require("./img/extern/copy-link-button.png").default} alt="Copy link" width="1920"/>
+
+- You can edit the link later by clicking the three-dot menu to the right of the link.
+  From there, you can rename the link, change the expiry date, update the password, remove the password, or delete the link.
+  <img src={require("./img/extern/link-actions-menu.png").default} alt="Link actions menu" width="1920"/>
+
+Now you know how to share files and folders securely with external users.
diff --git a/versioned_docs/version-7.x/user/sharing/file-drop.md b/versioned_docs/version-7.x/user/sharing/file-drop.md
new file mode 100644
index 000000000..260ac78a5
--- /dev/null
+++ b/versioned_docs/version-7.x/user/sharing/file-drop.md
@@ -0,0 +1,46 @@
+---
+sidebar_position: 3
+id: file-drop
+title: File Drop
+description: File Drop (secret)
+draft: false
+---
+
+# File Drop (secret) - How it works
+
+File Drop lets people who receive a specific link, the so-called link recipients, upload files to a shared folder.
+Link recipients cannot see the files that are already in the folder.
+
+## Create a File Drop
+
+- Right-click the file or folder, or click the three-dot menu next to its name, to open the context menu.
+- Select “Share” from the context menu.
+  <img src={require("./img/file-drop/share-drop-down-menu.png").default} alt="Drop down menu" width="1920" />
+- A sidebar window will open on the right-hand side of the screen.
+  <img src={require("./img/file-drop/sidebar-window.png").default} alt="Sidebar window" width="400"/>
+- In the sidebar window, find the “Public links” section and click “Add link”.
+  <img src={require("./img/file-drop/add-link-button.png").default} alt="Add link button" width="400"/>
+- Click "Options" to open the link settings.
+- Open the access rights dropdown menu and select "Secret File Drop".
+  <img src={require("./img/file-drop/file-drop-button.png").default} alt="Select file drop" width="1920"/>
+
+- Enter a password and click “Copy link” to confirm.
+- You can also set an “Expiry date” if you want the link to expire.
+  <img src={require("./img/file-drop/password-and-copy-link-button.png").default} alt="Enter password and copy link" width="1920"/>
+- Share the link and password with the recipient.
+
+## What the recipient does
+
+- The recipient opens the received link in a browserand enters the password and clicks “Continue”.
+  <img src={require("./img/file-drop/password-and-continue.png").default} alt="Enter password and continue" width="1920"/>
+- Upload files:
+  - The File Drop folder opens. The recipient can upload files without seeing the existing contents of the folder.
+    <img src={require("./img/file-drop/file-drop-area.png").default} alt="File drop area" width="1920"/>
+  - A pop-up window appears in the lower right corner to confirm that the upload was successful.
+    <img src={require("./img/file-drop/upload-confirmation.png").default} alt="Upload confirmation" width="1920"/>
+
+:::important
+Recipients do not have access to existing files. They can only add new files.
+:::
+
+Now you know how to share a File Drop link.
diff --git a/versioned_docs/version-7.x/user/sharing/img/extern/access-rights.png b/versioned_docs/version-7.x/user/sharing/img/extern/access-rights.png
new file mode 100644
index 000000000..f081859da
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/extern/access-rights.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/img/extern/copy-link-button.png b/versioned_docs/version-7.x/user/sharing/img/extern/copy-link-button.png
new file mode 100644
index 000000000..4a69f9fab
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/extern/copy-link-button.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/img/extern/link-actions-menu.png b/versioned_docs/version-7.x/user/sharing/img/extern/link-actions-menu.png
new file mode 100644
index 000000000..5c7ae2a0e
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/extern/link-actions-menu.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/img/extern/password-section.png b/versioned_docs/version-7.x/user/sharing/img/extern/password-section.png
new file mode 100644
index 000000000..4346b82bc
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/extern/password-section.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/img/extern/public-link-option-pop-up.png b/versioned_docs/version-7.x/user/sharing/img/extern/public-link-option-pop-up.png
new file mode 100644
index 000000000..12ab872bd
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/extern/public-link-option-pop-up.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/img/extern/share-drop-down-menu.png b/versioned_docs/version-7.x/user/sharing/img/extern/share-drop-down-menu.png
new file mode 100644
index 000000000..272679ad6
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/extern/share-drop-down-menu.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/img/extern/sidebar-window.png b/versioned_docs/version-7.x/user/sharing/img/extern/sidebar-window.png
new file mode 100644
index 000000000..99dcc200b
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/extern/sidebar-window.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/img/file-drop/add-link-button.png b/versioned_docs/version-7.x/user/sharing/img/file-drop/add-link-button.png
new file mode 100644
index 000000000..68420224f
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/file-drop/add-link-button.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/img/file-drop/file-drop-area.png b/versioned_docs/version-7.x/user/sharing/img/file-drop/file-drop-area.png
new file mode 100644
index 000000000..495f4d67f
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/file-drop/file-drop-area.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/img/file-drop/file-drop-button.png b/versioned_docs/version-7.x/user/sharing/img/file-drop/file-drop-button.png
new file mode 100644
index 000000000..7a3dc1020
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/file-drop/file-drop-button.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/img/file-drop/password-and-continue.png b/versioned_docs/version-7.x/user/sharing/img/file-drop/password-and-continue.png
new file mode 100644
index 000000000..ab8ea3edd
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/file-drop/password-and-continue.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/img/file-drop/password-and-copy-link-button.png b/versioned_docs/version-7.x/user/sharing/img/file-drop/password-and-copy-link-button.png
new file mode 100644
index 000000000..8163c4e34
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/file-drop/password-and-copy-link-button.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/img/file-drop/share-drop-down-menu.png b/versioned_docs/version-7.x/user/sharing/img/file-drop/share-drop-down-menu.png
new file mode 100644
index 000000000..272679ad6
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/file-drop/share-drop-down-menu.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/img/file-drop/sidebar-window.png b/versioned_docs/version-7.x/user/sharing/img/file-drop/sidebar-window.png
new file mode 100644
index 000000000..68420224f
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/file-drop/sidebar-window.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/img/file-drop/upload-confirmation.png b/versioned_docs/version-7.x/user/sharing/img/file-drop/upload-confirmation.png
new file mode 100644
index 000000000..ea911bfc3
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/file-drop/upload-confirmation.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/img/intern/remove-share.png b/versioned_docs/version-7.x/user/sharing/img/intern/remove-share.png
new file mode 100644
index 000000000..613009b4a
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/intern/remove-share.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/img/intern/rights-options.png b/versioned_docs/version-7.x/user/sharing/img/intern/rights-options.png
new file mode 100644
index 000000000..afeda6b16
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/intern/rights-options.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/img/intern/searchbar.png b/versioned_docs/version-7.x/user/sharing/img/intern/searchbar.png
new file mode 100644
index 000000000..6caa02ba2
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/intern/searchbar.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/img/intern/share-drop-down-menu.png b/versioned_docs/version-7.x/user/sharing/img/intern/share-drop-down-menu.png
new file mode 100644
index 000000000..cd2a599ca
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/intern/share-drop-down-menu.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/img/intern/share-with-people-section.png b/versioned_docs/version-7.x/user/sharing/img/intern/share-with-people-section.png
new file mode 100644
index 000000000..b68d23e2a
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/intern/share-with-people-section.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/img/intern/shared-with-alan.png b/versioned_docs/version-7.x/user/sharing/img/intern/shared-with-alan.png
new file mode 100644
index 000000000..9a0f03a5a
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/intern/shared-with-alan.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/img/intern/sidebar-window.png b/versioned_docs/version-7.x/user/sharing/img/intern/sidebar-window.png
new file mode 100644
index 000000000..e69150dab
Binary files /dev/null and b/versioned_docs/version-7.x/user/sharing/img/intern/sidebar-window.png differ
diff --git a/versioned_docs/version-7.x/user/sharing/index.md b/versioned_docs/version-7.x/user/sharing/index.md
new file mode 100644
index 000000000..539998d39
--- /dev/null
+++ b/versioned_docs/version-7.x/user/sharing/index.md
@@ -0,0 +1,20 @@
+---
+sidebar_position: 0
+id: sharing-overview
+title: Share files and folders
+---
+
+# Share files and folders
+
+This section explains how sharing works in OpenCloud. It covers internal sharing with members and groups, public links for external access, and File Drop links for receiving uploads.
+
+## In this section
+
+- [Internal sharing](./internal.md)  
+  Share files and folders with members or groups within your organization.
+
+- [External sharing](./external.md)  
+  Create public links and manage options such as permissions, passwords, and expiry dates.
+
+- [File Drop](./file-drop.md)  
+  Allow external users to upload files without giving them access to existing content.
diff --git a/versioned_docs/version-7.x/user/sharing/internal.md b/versioned_docs/version-7.x/user/sharing/internal.md
new file mode 100644
index 000000000..c5532034e
--- /dev/null
+++ b/versioned_docs/version-7.x/user/sharing/internal.md
@@ -0,0 +1,58 @@
+---
+sidebar_position: 1
+id: internal
+title: Internal
+description: Organization internal sharing of files and folders in OpenCloud
+draft: false
+---
+
+# Organization internal sharing of files and folders in OpenCloud
+
+Files and folders can be shared within the organization with individual members or groups. Different access rights can be assigned.
+
+## Create an internal share
+
+- Open the three-dot menu next to the file or folder you want to share.
+
+- Select “Share” from the context menu.
+
+  <img src={require("./img/intern/share-drop-down-menu.png").default} alt="Drop down menu" width="1920"/>
+
+- The sidebar opens on the right-hand side of the screen.
+  <img src={require("./img/intern/sidebar-window.png").default} alt="Sharing sidebar" width="1920"/>
+
+- At the top of the sidebar, select the “Internal sharing” section.
+  <img src={require("./img/intern/share-with-people-section.png").default} alt="Share with people" width="400"/>
+
+- Enter at least three characters in the search field to look up members or groups.
+
+  <img src={require("./img/intern/searchbar.png").default} alt="Enter name or group" width="400"/>
+
+- Select the desired person or group from the suggestion list.
+
+- Set the access rights for the selected members or groups:
+  - “Can view”:
+    Members can view and download the file or folder. They cannot edit content or upload to shared folders.
+  - “Can upload”:
+    Members can view and download the content. For folders, they can also upload their own files.
+  - “Can edit”:
+    Members can view, download, upload, create, edit, and delete content.
+    <img src={require("./img/intern/rights-options.png").default} alt="Right options" width="400"/>
+
+- Click on “Share” to create the internal share.
+
+The shared members or groups are then shown under “Shared with”.
+
+<img src={require("./img/intern/shared-with-alan.png").default} alt="Show the shared overview" width="400"/>
+
+## Remove an internal share
+
+An existing internal share can be removed at any time.
+
+- Open the three-dot menu next to the person or group in the “Shared with” section.
+
+- Select the “Remove share” option.
+
+<img src={require("./img/intern/remove-share.png").default} alt="Remove share" width="400"/>
+
+The access is removed immediately. After that, the person or group can no longer access the file or folder through this share.
diff --git a/versioned_docs/version-7.x/user/spaces/_category_.json b/versioned_docs/version-7.x/user/spaces/_category_.json
new file mode 100644
index 000000000..f2ae4ad82
--- /dev/null
+++ b/versioned_docs/version-7.x/user/spaces/_category_.json
@@ -0,0 +1,8 @@
+{
+  "label": "Working in teams with Spaces",
+  "position": 5,
+  "link": {
+    "type": "doc",
+    "id": "spaces-overview"
+  }
+}
diff --git a/versioned_docs/version-7.x/user/spaces/add-user.md b/versioned_docs/version-7.x/user/spaces/add-user.md
new file mode 100644
index 000000000..e4f47f0f5
--- /dev/null
+++ b/versioned_docs/version-7.x/user/spaces/add-user.md
@@ -0,0 +1,46 @@
+---
+sidebar_position: 3
+id: add-members
+title: Add members
+description: Add new members to your Space in OpenCloud
+draft: false
+---
+
+# Add a new member to your Space in OpenCloud
+
+You can easily invite new members to collaborate within your Space by following the steps below.
+
+- Go to your Space and open the members' menu.
+  <img src={require("./img/add-user/member-menu.png").default} alt="Member menu" width="1920"/>
+
+- In the members menu, you can search for the user from your organization that you want to add.
+
+  <img src={require("./img/add-user/search-user.png").default} alt="search user" width="1920"/>
+
+- Select the desired rights for the member, e.g. whether the person may only read or also edit.
+
+  <img src={require("./img/add-user/choose-rights.png").default} alt="Choose rights" width="1920"/>
+
+- Click on “Add” to invite the member to the Space.
+
+  <img src={require("./img/add-user/member-added.png").default} alt="Member added" width="1920"/>
+
+- To change the rights of a member, open the members menu, click on the corresponding user and select the desired new rights.
+
+  <img src={require("./img/add-user/change-rights.png").default} alt="Change rights" width="1920"/>
+
+- Open the members menu, click on the three-dot menu next to the member and use “Access details”, “Set expiration date”, or “Remove member” as needed.
+
+  <img src={require("./img/add-user/remove-user.png").default} alt="Remove user" width="1920"/>
+
+:::note
+The removed member immediately loses access to the space.
+:::
+
+:::important
+
+- The added member has immediate access to the Space.
+- Attention: Every user with the “can manage” right has the authorization to deactivate and delete the Space.
+- A deleted Space cannot be restored, so be careful who you grant these rights to.
+
+:::
diff --git a/versioned_docs/version-7.x/user/spaces/create.md b/versioned_docs/version-7.x/user/spaces/create.md
new file mode 100644
index 000000000..4d906079b
--- /dev/null
+++ b/versioned_docs/version-7.x/user/spaces/create.md
@@ -0,0 +1,39 @@
+---
+sidebar_position: 2
+id: create
+title: Create a Space
+description: Create Spaces and share data in OpenCloud
+draft: false
+---
+
+# Create Spaces and share data in OpenCloud
+
+With Spaces you can share data with specific people within your organization. All members of a Space have the defined access to the data, and you can customize the editing rights for each member.
+
+## Create a new Space
+
+- Go to the menu item "Spaces” in the left sidebar
+
+  <img src={require("./img/create/new-space.png").default} alt="Space in left Sidebar" width="1920"/>
+
+- Click on "+ New Space”
+
+  <img src={require("./img/create/new-space-popup.png").default} alt="New-Space" width="1920"/>
+
+- Enter the desired name for the Space.
+
+  <img src={require("./img/create/enter-name.png").default} alt="Enter Spacename" width="1920"/>
+
+- Click on "Create”.
+
+## Your new Space
+
+Your new Space now appears under "Spaces" and is ready to be used.
+
+<img src={require("./img/create/created-space.png").default} alt="Created Space" width="1920"/>
+
+Now you know how to quickly and easily create a Space and can start sharing data!
+
+:::important
+Spaces can only be permanently shared within your own organization.
+:::
diff --git a/versioned_docs/version-7.x/user/spaces/customize.md b/versioned_docs/version-7.x/user/spaces/customize.md
new file mode 100644
index 000000000..fc727473e
--- /dev/null
+++ b/versioned_docs/version-7.x/user/spaces/customize.md
@@ -0,0 +1,45 @@
+---
+sidebar_position: 8
+id: customize
+title: Customize Spaces
+description: Customize a Space in OpenCloud
+draft: false
+---
+
+# Customize a Space in OpenCloud
+
+You can customize a Space either in the Space overview or inside the Space itself.
+
+## Edit description
+
+Click "Edit description". Enter your description in the text editor that opens, then save and close it.
+
+<img src={require("./img/customize/description-edit.png").default} alt="Edit description" width="1920"/>
+<img src={require("./img/customize/description-change.png").default} alt="Change the description" width="1920"/>
+
+The description can also be edited directly in the Space by clicking the pencil next to it.
+
+## Edit subtitle
+
+Click "Edit subtitle". Enter the desired subtitle in the text editor and save it.
+
+<img src={require("./img/customize/subtitle-edit.png").default} alt="Edit subtitle" width="1920"/>
+<img src={require("./img/customize/subtitle-change.png").default} alt="Change subtitle" width="1920"/>
+
+## Set image
+
+Click "Edit image" and then choose "Set image". In the window that opens, select the desired image for your Space and confirm. Then select the desired crop area and confirm.
+
+<img src={require("./img/customize/image-edit.png").default} alt="Select space image" width="1920"/>
+<img src={require("./img/customize/image-size.png").default} alt="Crop space image" width="1920"/>
+<img src={require("./img/customize/image-set.png").default} alt="Space image" width="1920"/>
+
+## Set icon
+
+Click "Edit image" and then choose "Set icon". In the window that opens, select the desired icon for your Space.
+
+<img src={require("./img/customize/icon-set.png").default} alt="Click on set icon" width="1920"/>
+<img src={require("./img/customize/icon-select.png").default} alt="Select the icon" width="500"/>
+<img src={require("./img/customize/icon-spaceimage.png").default} alt="Icon as space image" width="1920"/>
+
+Now you know how to customize a Space.
diff --git a/versioned_docs/version-7.x/user/spaces/delete.md b/versioned_docs/version-7.x/user/spaces/delete.md
new file mode 100644
index 000000000..7980bab25
--- /dev/null
+++ b/versioned_docs/version-7.x/user/spaces/delete.md
@@ -0,0 +1,35 @@
+---
+sidebar_position: 6
+id: delete
+title: Delete a Space
+description: Delete a Space in OpenCloud
+draft: false
+---
+
+# Delete a Space in OpenCloud
+
+Before you delete a Space, it must first be disabled.
+
+## Disable the Space first
+
+- Follow the instructions in [Disable and Enable a Space](./enable-disable.md) to disable the Space before deleting it.
+
+- If the Space is no longer visible after deactivation, make sure the Include disabled filter is enabled so the Space is shown again.
+
+  <img src={require("./img/delete/deactivate-filter.png").default} alt="Deactivate Filter" width="1920"/>
+
+## Delete the Space
+
+- Select the Space you want to delete, or open the context menu and click Delete.
+
+  <img src={require("./img/delete/delete-top-bar.png").default} alt="Delete Top-Bar and Context Menu" width="1920"/>
+
+- Confirm that you want to delete the Space.
+
+  <img src={require("./img/delete/confirm.png").default} alt="Confirm" width="500"/>
+
+:::caution
+A deleted Space cannot be restored. Make sure that no important data will be lost before you delete it.
+:::
+
+Now you know how to delete a Space.
diff --git a/versioned_docs/version-7.x/user/spaces/enable-disable.md b/versioned_docs/version-7.x/user/spaces/enable-disable.md
new file mode 100644
index 000000000..17eaf84a0
--- /dev/null
+++ b/versioned_docs/version-7.x/user/spaces/enable-disable.md
@@ -0,0 +1,56 @@
+---
+sidebar_position: 5
+id: disable-enable
+title: Disable and Enable a Space
+description: Disable and enable a Space in OpenCloud
+draft: false
+---
+
+# Disable and Enable a Space in OpenCloud
+
+You can disable and re-enable a Space in a few different ways. Only a Space Admin or the Administrator can do this.
+
+## Disable Space
+
+- Select the desired Space.
+- Click Disable in the top action bar or open the context menu.
+
+  <img src={require("./img/enable-disable/disable-space-overview.png").default} alt="Overview disabled spaces" width="1920"/>
+
+- Confirm the deactivation.
+
+  <img src={require("./img/enable-disable/disable-confirm.png").default} alt="Confirm disable" width="1920"/>
+
+- The Space is now disabled.
+
+<img src={require("./img/enable-disable/disabled-space.png").default} alt="Confirm disable" width="1920"/>
+:::note
+No data will be deleted. Only the Space Admin or the Administrator can enable the Space again.
+:::
+
+## Enable Space
+
+- After the Space has been disabled, the Enable option replaces Disable.
+
+  <img src={require("./img/enable-disable/enable.png").default} alt="Enable option" width="1920"/>
+
+- Click it to enable the Space again.
+
+- If the Space is not visible, the Show disabled Spaces filter may be enabled.
+
+  <img src={require("./img/enable-disable/include-disabled.png").default} alt="Include disabled spaces" width="1920"/>
+
+- Enable the filter and the Space will appear so it can be enabled.
+
+  <img src={require("./img/enable-disable/disable-included.png").default} alt="Included disabled spaces" width="1920"/>
+
+## Enable by Administrator
+
+An Administrator can also enable or disable a Space from [Admin Settings](../admin/settings.md#spaces).
+
+- Open the Spaces section in Admin Settings.
+- Find the Space that should be enabled or disabled.
+- Open the three-dot menu and select Enable or Disable.
+- Confirm the action.
+
+The Space will then appear in the corresponding state in the Space overview.
diff --git a/versioned_docs/version-7.x/user/spaces/img/add-user/change-rights.png b/versioned_docs/version-7.x/user/spaces/img/add-user/change-rights.png
new file mode 100644
index 000000000..e712a8b9c
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/add-user/change-rights.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/add-user/choose-rights.png b/versioned_docs/version-7.x/user/spaces/img/add-user/choose-rights.png
new file mode 100644
index 000000000..9096cae73
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/add-user/choose-rights.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/add-user/member-added.png b/versioned_docs/version-7.x/user/spaces/img/add-user/member-added.png
new file mode 100644
index 000000000..eb254aec1
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/add-user/member-added.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/add-user/member-menu.png b/versioned_docs/version-7.x/user/spaces/img/add-user/member-menu.png
new file mode 100644
index 000000000..4d265e59e
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/add-user/member-menu.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/add-user/remove-user.png b/versioned_docs/version-7.x/user/spaces/img/add-user/remove-user.png
new file mode 100644
index 000000000..1def4e0bf
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/add-user/remove-user.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/add-user/search-user.png b/versioned_docs/version-7.x/user/spaces/img/add-user/search-user.png
new file mode 100644
index 000000000..4bcfbaabf
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/add-user/search-user.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/create/created-space.png b/versioned_docs/version-7.x/user/spaces/img/create/created-space.png
new file mode 100644
index 000000000..5b04d6cc5
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/create/created-space.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/create/enter-name.png b/versioned_docs/version-7.x/user/spaces/img/create/enter-name.png
new file mode 100644
index 000000000..5345c03d9
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/create/enter-name.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/create/new-space-popup.png b/versioned_docs/version-7.x/user/spaces/img/create/new-space-popup.png
new file mode 100644
index 000000000..34c48ed8e
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/create/new-space-popup.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/create/new-space.png b/versioned_docs/version-7.x/user/spaces/img/create/new-space.png
new file mode 100644
index 000000000..4bf616924
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/create/new-space.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/customize/description-change.png b/versioned_docs/version-7.x/user/spaces/img/customize/description-change.png
new file mode 100644
index 000000000..a0630b035
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/customize/description-change.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/customize/description-edit.png b/versioned_docs/version-7.x/user/spaces/img/customize/description-edit.png
new file mode 100644
index 000000000..bd772cd3b
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/customize/description-edit.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/customize/icon-select.png b/versioned_docs/version-7.x/user/spaces/img/customize/icon-select.png
new file mode 100644
index 000000000..b421456f3
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/customize/icon-select.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/customize/icon-set.png b/versioned_docs/version-7.x/user/spaces/img/customize/icon-set.png
new file mode 100644
index 000000000..252a68ed9
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/customize/icon-set.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/customize/icon-spaceimage.png b/versioned_docs/version-7.x/user/spaces/img/customize/icon-spaceimage.png
new file mode 100644
index 000000000..aeae29937
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/customize/icon-spaceimage.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/customize/image-edit.png b/versioned_docs/version-7.x/user/spaces/img/customize/image-edit.png
new file mode 100644
index 000000000..3641fc9c2
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/customize/image-edit.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/customize/image-set.png b/versioned_docs/version-7.x/user/spaces/img/customize/image-set.png
new file mode 100644
index 000000000..ba79e9cfe
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/customize/image-set.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/customize/image-size.png b/versioned_docs/version-7.x/user/spaces/img/customize/image-size.png
new file mode 100644
index 000000000..d6c9f95e6
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/customize/image-size.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/customize/subtitle-change.png b/versioned_docs/version-7.x/user/spaces/img/customize/subtitle-change.png
new file mode 100644
index 000000000..8d42aa0db
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/customize/subtitle-change.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/customize/subtitle-edit.png b/versioned_docs/version-7.x/user/spaces/img/customize/subtitle-edit.png
new file mode 100644
index 000000000..d6f4dd4bb
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/customize/subtitle-edit.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/delete/confirm.png b/versioned_docs/version-7.x/user/spaces/img/delete/confirm.png
new file mode 100644
index 000000000..e8b07106b
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/delete/confirm.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/delete/deactivate-filter.png b/versioned_docs/version-7.x/user/spaces/img/delete/deactivate-filter.png
new file mode 100644
index 000000000..b6062b706
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/delete/deactivate-filter.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/delete/delete-top-bar.png b/versioned_docs/version-7.x/user/spaces/img/delete/delete-top-bar.png
new file mode 100644
index 000000000..a1785a374
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/delete/delete-top-bar.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/enable-disable/disable-confirm.png b/versioned_docs/version-7.x/user/spaces/img/enable-disable/disable-confirm.png
new file mode 100644
index 000000000..c6e558511
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/enable-disable/disable-confirm.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/enable-disable/disable-included.png b/versioned_docs/version-7.x/user/spaces/img/enable-disable/disable-included.png
new file mode 100644
index 000000000..809eec4c9
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/enable-disable/disable-included.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/enable-disable/disable-space-overview.png b/versioned_docs/version-7.x/user/spaces/img/enable-disable/disable-space-overview.png
new file mode 100644
index 000000000..b4214584c
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/enable-disable/disable-space-overview.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/enable-disable/disabled-space.png b/versioned_docs/version-7.x/user/spaces/img/enable-disable/disabled-space.png
new file mode 100644
index 000000000..e48dfbf62
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/enable-disable/disabled-space.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/enable-disable/enable.png b/versioned_docs/version-7.x/user/spaces/img/enable-disable/enable.png
new file mode 100644
index 000000000..901378317
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/enable-disable/enable.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/enable-disable/include-disabled.png b/versioned_docs/version-7.x/user/spaces/img/enable-disable/include-disabled.png
new file mode 100644
index 000000000..1f235e60c
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/enable-disable/include-disabled.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/quota/context-menu.png b/versioned_docs/version-7.x/user/spaces/img/quota/context-menu.png
new file mode 100644
index 000000000..5d2442360
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/quota/context-menu.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/quota/enter.png b/versioned_docs/version-7.x/user/spaces/img/quota/enter.png
new file mode 100644
index 000000000..05ee3e451
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/quota/enter.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/quota/select.png b/versioned_docs/version-7.x/user/spaces/img/quota/select.png
new file mode 100644
index 000000000..68c860819
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/quota/select.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/rename/confirm.png b/versioned_docs/version-7.x/user/spaces/img/rename/confirm.png
new file mode 100644
index 000000000..9e47ae713
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/rename/confirm.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/rename/rename.png b/versioned_docs/version-7.x/user/spaces/img/rename/rename.png
new file mode 100644
index 000000000..00d6470d7
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/rename/rename.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/rename/renamed-space.png b/versioned_docs/version-7.x/user/spaces/img/rename/renamed-space.png
new file mode 100644
index 000000000..fca55f140
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/rename/renamed-space.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/why-spaces/alan-left.png b/versioned_docs/version-7.x/user/spaces/img/why-spaces/alan-left.png
new file mode 100644
index 000000000..01e2c4179
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/why-spaces/alan-left.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/why-spaces/spaces.png b/versioned_docs/version-7.x/user/spaces/img/why-spaces/spaces.png
new file mode 100644
index 000000000..95ee417f8
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/why-spaces/spaces.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/img/why-spaces/spaghetti.png b/versioned_docs/version-7.x/user/spaces/img/why-spaces/spaghetti.png
new file mode 100644
index 000000000..7ba9019cc
Binary files /dev/null and b/versioned_docs/version-7.x/user/spaces/img/why-spaces/spaghetti.png differ
diff --git a/versioned_docs/version-7.x/user/spaces/index.md b/versioned_docs/version-7.x/user/spaces/index.md
new file mode 100644
index 000000000..894306679
--- /dev/null
+++ b/versioned_docs/version-7.x/user/spaces/index.md
@@ -0,0 +1,38 @@
+---
+sidebar_position: 0
+id: spaces-overview
+title: Working in teams with Spaces
+---
+
+# Working in teams with Spaces
+
+Spaces are shared work areas in OpenCloud. They help teams organize content, manage access, and keep project or team files separate from personal storage.
+
+## In this section
+
+- [Why Spaces?](./why-spaces.md)  
+  Learn why Spaces are better suited for teamwork than traditional sharing.
+
+- [Create a Space](./create.md)  
+  Create a new Space for a team, project, or department.
+
+- [Add members](./add-user.md)  
+  Invite people to a Space and assign the appropriate permissions.
+
+- [Edit Space quota](./quota.md)  
+  Adjust the storage quota available for a Space.
+
+- [Disable and Enable a Space](./enable-disable.md)  
+  Temporarily disable a Space and enable it again later when needed.
+
+- [Delete a Space](./delete.md)  
+  Permanently remove a Space when it is no longer needed.
+
+- [Rename a Space](./rename.md)  
+  Change the name of an existing Space.
+
+- [Customize Spaces](./customize.md)  
+  Update descriptions, subtitles, images, and icons for a Space.
+
+- [Best practice](./spaces-best-practices.md)  
+  Follow recommended structures and naming conventions for Spaces.
diff --git a/versioned_docs/version-7.x/user/spaces/quota.md b/versioned_docs/version-7.x/user/spaces/quota.md
new file mode 100644
index 000000000..6d0cd61d5
--- /dev/null
+++ b/versioned_docs/version-7.x/user/spaces/quota.md
@@ -0,0 +1,30 @@
+---
+sidebar_position: 4
+id: space-quota
+title: Edit Space Quota
+description: Edit the quota of a Space
+draft: false
+---
+
+# Edit the quota of a Space
+
+As a Space administrator, you can adjust the storage capacity (quota) of a Space to increase or decrease the available storage space as required.
+
+## Steps to edit the Space quota
+
+- Select the Edit quota option in the Top-Bar or in the Context-Menu
+
+  <img src={require("./img/quota/context-menu.png").default} alt="Context-Menu" width="1920"/>
+
+- Two options are available in the window that opens:
+- Select a default size (e.g. 5 GB) from the drop-down menu.
+
+  <img src={require("./img/quota/select.png").default} alt="Select-quota" width="1920"/>
+
+- Enter an individual storage size.
+
+  <img src={require("./img/quota/enter.png").default} alt="Enter-quota" width="1920"/>
+
+- Click on Confirm to apply the change.
+
+The quota of the space is updated according to the new settings.
diff --git a/versioned_docs/version-7.x/user/spaces/rename.md b/versioned_docs/version-7.x/user/spaces/rename.md
new file mode 100644
index 000000000..a9963ce85
--- /dev/null
+++ b/versioned_docs/version-7.x/user/spaces/rename.md
@@ -0,0 +1,22 @@
+---
+sidebar_position: 7
+id: rename
+title: Rename a Space
+description: Rename a Space in OpenCloud
+draft: false
+---
+
+# Rename a Space in OpenCloud
+
+You can rename an existing Space at any time to better reflect its purpose or content.
+
+- Click on the three dots menu or do a right click on the Space in the Space Overview and select Rename
+
+  <img src={require("./img/rename/rename.png").default} alt="Rename" width="1920"/>
+
+- Enter the new name for the Space and confirm.
+
+  <img src={require("./img/rename/confirm.png").default} alt="confirm" width="1920"/>
+
+- Now your Space is renamed.
+  <img src={require("./img/rename/renamed-space.png").default} alt="Renamed Space" width="1920"/>
diff --git a/versioned_docs/version-7.x/user/spaces/spaces-best-practices.md b/versioned_docs/version-7.x/user/spaces/spaces-best-practices.md
new file mode 100644
index 000000000..db54e721f
--- /dev/null
+++ b/versioned_docs/version-7.x/user/spaces/spaces-best-practices.md
@@ -0,0 +1,113 @@
+---
+sidebar_position: 9
+id: best-practice
+title: Best practice
+description: Best practice how to use Spaces
+---
+
+# Best Practices for Organizing Spaces in OpenCloud
+
+Spaces are collaborative areas meant to be used by multiple users. Unlike personal storage, they must be structured in a way that supports clarity, collaboration, and scalability. This guide helps you set up and maintain well-organized, long-term usable Spaces.
+
+## General Principles
+
+- Plan first – Don't treat Spaces like ad-hoc storage. Think ahead.
+- Think in roles and teams – Structure based on how people work together.
+- Keep it scalable – Choose a structure that works now _and_ with more users later.
+- Apply consistency – Naming, access, and structure should follow shared rules.
+
+## Folder Structure: Recommended Patterns
+
+### Example: Family
+
+```plaintext
+📁 Family Space
+ ├── 📂 Documents
+ │    ├── 🧾 Insurance
+ │    └── 📑 Contracts
+ ├── 📂 Photos
+ │    ├── 📸 2024
+ │    └── 📸 2023
+ └── 📂 Shared Notes
+```
+
+### School / Kindergarten
+
+```plaintext
+
+📁 2024
+ ├── 📂 Class 3B
+ │    ├── 📂 Teaching Materials
+ │    ├── 📂 Parent Communication
+ │    ├── 📂 Homework Submissions
+ │    └── 📂 Events & Photos
+ ├── 📂 Class 4C
+ │    ├── 📂 Teaching Materials
+ │    ├── 📂 Parent Communication
+ │    ├── 📂 Homework Submissions
+ │    └── 📂 Events & Photos
+
+```
+
+### Company / Team
+
+```plaintext
+📁 Marketing Team
+ ├── 📂 Campaigns
+ │    ├── 📂 Q1-2025
+ │    └── 📂 Q2-2025
+ ├── 📂 Templates
+ ├── 📂 Reports
+ └── 📂 Meeting Notes
+```
+
+## Naming Conventions
+
+- Use clear, descriptive names – avoid "new folder" or cryptic titles
+- Prefer lowercase-with-dashes or Title Case
+- Add dates when relevant: `report-2025-Q2.pdf` or `Budget 2024.xlsx`
+- Avoid special characters: `& % $ § !` may break integrations
+
+## Ownership & Access Guidelines
+
+- Assign Space Owners: Responsible for structure and permissions
+- Use Groups where possible for access control (e.g. `staff`, `students`, `parents`)
+- Keep sensitive content in separate folders with restricted access
+- Define editing vs. viewing rights clearly
+
+## Archiving & Clean-Up
+
+- Set up an archive folder for old or unused files
+- Annually review the Space and remove outdated content
+- Use versioning or export before deletion if unsure
+
+## Common Pitfalls to Avoid
+
+| ❌ Don’t                        | ✅ Instead                       |
+| ------------------------------- | -------------------------------- |
+| Dump all files in root folder   | Use clear subfolders             |
+| Mix personal and shared content | Keep personal data in "Personal" |
+| Give all users full access      | Apply least-privilege principle  |
+| Use inconsistent naming         | Define and follow conventions    |
+
+## Shareable Quick Start Template
+
+You can use this as a template for new Spaces:
+
+```plaintext
+📁 [Team/Project Name]
+ ├── 📂 Documents
+ ├── 📂 Planning
+ ├── 📂 Resources
+ ├── 📂 Archive
+ └── README.md (Space purpose, structure, rules)
+```
+
+## Summary
+
+| Goal                         | How                                |
+| ---------------------------- | ---------------------------------- |
+| Make Spaces easy to navigate | Use clear folder names & hierarchy |
+| Avoid permission chaos       | Define ownership and roles         |
+| Keep things clean            | Review regularly and archive       |
+| Support collaboration        | Use group access & standard naming |
diff --git a/versioned_docs/version-7.x/user/spaces/why-spaces.md b/versioned_docs/version-7.x/user/spaces/why-spaces.md
new file mode 100644
index 000000000..27a974bf1
--- /dev/null
+++ b/versioned_docs/version-7.x/user/spaces/why-spaces.md
@@ -0,0 +1,42 @@
+---
+sidebar_position: 1
+id: why-spaces
+title: Why Spaces?
+description: Why you should use Spaces
+draft: false
+---
+
+# Why you should use Spaces – and now they differ from classic sharing
+
+## The problem with classic sharing
+
+### Let’s take a simple example
+
+- Alan creates a folder called "Project" and shares it with several Persons
+  <img src={require("./img/why-spaces/spaghetti.png").default} alt="Member menu" width="500"/>
+- Later, Alan leaves the organization
+- As Alan's account is deleted, some shared folder disappears
+- User loses access to some folders and their content
+
+  <img src={require("./img/why-spaces/alan-left.png").default} alt="Member menu" width="500"/>
+
+### This scenario highlights several risks
+
+- Potential data loss when the original owner leaves
+- Project data counts toward personal quotas, which is not ideal for teamwork
+- Administrative overhead when ownership needs to be transferred
+- Spaghetti sharing chaos – users get lost in their "Shared with me" or "Shared with others" sections
+
+## The Benefits of Using Spaces
+
+Spaces are designed to overcome these limitations and provide a more stable, team-friendly solution
+
+- Organization-owned: Spaces belong to the organization, not individuals.
+- Collaborative management: Multiple users can manage a Space together.
+- Dedicated quota: Each Space has its own storage limit, separate from personal quotas.
+
+  <img src={require("./img/why-spaces/spaces.png").default} alt="Member menu" width="500"/>
+
+:::note
+Spaces make collaboration simpler, safer, and more scalable — especially in professional environments.
+:::
diff --git a/versioned_sidebars/version-7.x-sidebars.json b/versioned_sidebars/version-7.x-sidebars.json
new file mode 100644
index 000000000..5b1a869c5
--- /dev/null
+++ b/versioned_sidebars/version-7.x-sidebars.json
@@ -0,0 +1,20 @@
+{
+  "user": [
+    {
+      "type": "autogenerated",
+      "dirName": "user"
+    }
+  ],
+  "admin": [
+    {
+      "type": "autogenerated",
+      "dirName": "admin"
+    }
+  ],
+  "dev": [
+    {
+      "type": "autogenerated",
+      "dirName": "dev"
+    }
+  ]
+}
diff --git a/versions.json b/versions.json
index 483d0c198..853f1306c 100644
--- a/versions.json
+++ b/versions.json
@@ -1,3 +1,4 @@
 [
+  "7.x",
   "4.0"
 ]