diff --git a/docs/ai_actions/ai_actions.md b/docs/ai_actions/ai_actions.md
index caf5d6c5e2..1db6b24180 100644
--- a/docs/ai_actions/ai_actions.md
+++ b/docs/ai_actions/ai_actions.md
@@ -13,5 +13,6 @@ You can also extend it to perform other tasks or support additional AI services.
 
 [[= cards([
 "ai_actions/ai_actions_guide",
-"ai_actions/install_ai_actions"
+"ai_actions/install_ai_actions",
+"ai_actions/extend_ai_actions",
 ], columns=4) =]]
diff --git a/docs/ai_actions/extend_ai_actions.md b/docs/ai_actions/extend_ai_actions.md
index 7c82f38ddb..a2d29742e5 100644
--- a/docs/ai_actions/extend_ai_actions.md
+++ b/docs/ai_actions/extend_ai_actions.md
@@ -59,7 +59,7 @@ To manage configurations of an AI Action you need to use another concept: Action
 ### Manage Action Configurations
 
 Action Configurations allow you to store the parameters for a given Action in the database and reuse them when needed.
-They can be managed [through the back office]([[= user_doc =]]/ai_actions/work_with_ai_actions.md), [data migrations](importing_data.md#ai-action-configurations), or through the PHP API.
+They can be managed [through the back office]([[= user_doc =]]/ai_actions/work_with_ai_actions/), [data migrations](importing_data.md#ai-action-configurations), or through the PHP API.
 
 To manage Action Configurations through the PHP API, you need to use the [ActionConfigurationServiceInterface](../api/php_api/php_api_reference/classes/Ibexa-Contracts-ConnectorAi-ActionConfigurationServiceInterface.html) service.