diff --git a/documentation/spring-integration/index.md b/documentation/spring-integration/index.md
index e0fc9e3f..8117134c 100644
--- a/documentation/spring-integration/index.md
+++ b/documentation/spring-integration/index.md
@@ -251,6 +251,29 @@ It could be a Service, Repository or anything which modifies domain objects.
 
 From now, all objects passed to the annotated methods will be automatically versioned by JaVers.
 
+<h3 id="at-javers-auditable-conditional-delete">@JaversAuditableConditionalDelete for any kind of repositories</h3>
+
+If you’re using any kind of reposity, and have delete methods with conditions, you can put `@JaversAuditableConditionalDelete` annotation on the methods to audit these events.
+
+For example:
+
+```java
+@Repository
+class UserRepository {
+    @JaversAuditableConditionalDelete
+    public User deleteByLogin(String login) {
+        ...//
+    }
+
+    @JaversAuditableConditionalDelete
+    public List<User> deleteAllByLogin(String login) {
+        ...//
+    }
+}
+```
+
+These delete methods must return either an Entity or a collection of Entity.
+
 <h2 id="jpa-entity-manager-integration">JPA EntityManager integration</h2>
 Transaction management is the important issue for applications backed by SQL databases.
 Generally, all SQL statements executed by `JaversSQLRepository`