docs(AI-act): Add note that config changes are logged in audit log

Signed-off-by: Marcel Klehr <mklehr@gmx.net>

Author: marcelklehr

admin_manual/ai/eu_ai_act.rst

@@ -14,6 +14,7 @@ This section describes of how Nextcloud and its AI products implemented the tran
 - Agentic interactions with third parties always include a note that the interaction was generated by AI (e.g. E-Mails sent on behalf of the user, calendar events created on behalf of the user, etc.).
 - Employees of Nextcloud GmbH have been instructed through the internal AI policy to inform audience when they send or publish content that were generated by AI or significantly altered by AI.
 - All interactions of users with AI in Nextcloud are retained in the database for observability and transparency. Refer to :ref:`Insight and Debugging<ai-insight-and-debugging>` for details on how to explore and examine these records.
+- All changes to AI configuration will be logged in the :ref:`audit log<config-admin-audit>`.
 
 Reliability and robustness
 --------------------------

admin_manual/configuration_server/logging_configuration.rst

@@ -138,6 +138,8 @@ Empty value are written as two dashes: ``--``.
 Admin audit log (Optional)
 --------------------------
 
+.. _config-admin-audit:
+
 By enabling the **admin_audit** app, additional information about various events can be logged. Similar to the normal logging, the audit log can be provided to any of the existing logging mechanisms in :file:`config/config.php`. The default behavior, if no parameters are specified after the app is enabled, is ``file`` based logging to a file called ``audit.log`` stored in the ``datadirectory``.
 
 If you wish to override this and log to syslog instead the following would be one approach: