diff --git a/docs/authorization/authorization-server.md b/docs/authorization/authorization-server.md
index ccb53ffe..9209f7da 100644
--- a/docs/authorization/authorization-server.md
+++ b/docs/authorization/authorization-server.md
@@ -15,7 +15,8 @@ When a request to access a resource is made, the PEP intercepts the request and
 
 Remember that to use the PEP endpoint and the Keycloak Authorization Services, you need to enable authorization for your client in the Keycloak admin console.
 
-![authz-arch-overview](/assets/authz-arch-overview.png)
+<!-- ![authz-arch-overview](/assets/authz-arch-overview.png) -->
+![authz-arch-overview](https://media.githubusercontent.com/media/NikiforovAll/keycloak-authorization-services-dotnet/main/docs/public/assets/authz-arch-overview.png)
 
 > [!TIP]
 > See Keycloak's documentation - [Authorization Server Architecture](https://www.keycloak.org/docs/latest/authorization_services/index.html#_overview_architecture) for more details.
diff --git a/docs/authorization/resources.md b/docs/authorization/resources.md
index c2687770..ca79418b 100644
--- a/docs/authorization/resources.md
+++ b/docs/authorization/resources.md
@@ -53,15 +53,18 @@ The *Keycloak Authorization Server* evaluates these policies whenever a user att
 
 💡 Here an example of how to create a permission for scopes:
 
-![permission](/assets/read-workspace-permission.png)
+<!-- ![read-workspace-permission](/assets/read-workspace-permission.png) -->
+![read-workspace-permission](https://media.githubusercontent.com/media/NikiforovAll/keycloak-authorization-services-dotnet/main/docs/public/assets/read-workspace-permission.png)
 
 💡 Here is an example of how to create a resource and associate a scopes with it:
 
-![permission](/assets/my-workspace-resource.png)
+![my-workspace-resource](/assets/my-workspace-resource.png)
+![permission](https://media.githubusercontent.com/media/NikiforovAll/keycloak-authorization-services-dotnet/main/docs/public/assets/my-workspace-resource.png)
 
 💡 Keycloak provides a UI to evaluate permissions for a given resource, user, scopes, etc. This feature enables you to prototype and troubleshoot more easily. Here is an example of how to evaluate permissions for an admin user:
 
-![permission](/assets/evaluate-permissions-for-admin.png)
+![evaluate-permissions-for-admin](/assets/evaluate-permissions-for-admin.png)
+![evaluate-permissions-for-admin](https://media.githubusercontent.com/media/NikiforovAll/keycloak-authorization-services-dotnet/main/docs/public/assets/evaluate-permissions-for-admin.png)
 
 ## Add to your code