diff --git a/doc/bugs/Fails_to_drop_key_on_windows___40__Access_denied__41__.mdwn b/doc/bugs/Fails_to_drop_key_on_windows___40__Access_denied__41__.mdwn
index 664a808bfa..87a0c37e61 100644
--- a/doc/bugs/Fails_to_drop_key_on_windows___40__Access_denied__41__.mdwn
+++ b/doc/bugs/Fails_to_drop_key_on_windows___40__Access_denied__41__.mdwn
@@ -130,3 +130,4 @@ And here is the diff between the two sequences  (failure(-) vs success(+)
 This observation comes from an effort to implement a git-remote-helper that uses git-annex to enable fetch/push to and from any location that can be reached by any special remote. The fact that git-annex can be used to build things like this is just crazy cool! Thx much!
 
 [[!tag projects/datalad]]
+[[!tag projects/INM7]]
diff --git a/doc/bugs/git-remote-annex_doesn__39__t_work_on_Windows___40__perms__41__.mdwn b/doc/bugs/git-remote-annex_doesn__39__t_work_on_Windows___40__perms__41__.mdwn
index df2d612a32..10a823cca6 100644
--- a/doc/bugs/git-remote-annex_doesn__39__t_work_on_Windows___40__perms__41__.mdwn
+++ b/doc/bugs/git-remote-annex_doesn__39__t_work_on_Windows___40__perms__41__.mdwn
@@ -496,3 +496,5 @@ backups, where it gives structure to my image-based backup routines, so you coul
 say I'm a believer. :)
 
 [[!meta author=jkniiv]]
+
+[[!tag projects/INM7]]
diff --git a/doc/todo/Read-only_support_for_webdav.mdwn b/doc/todo/Read-only_support_for_webdav.mdwn
index c09271775f..cb7ca2e87c 100644
--- a/doc/todo/Read-only_support_for_webdav.mdwn
+++ b/doc/todo/Read-only_support_for_webdav.mdwn
@@ -5,3 +5,5 @@ A use case not possible with that approach is *authenticated* read-only access.
 Weighing the two approaches (read-only `webdav` vs authenticated `httpalso`), it appears that only the read-only `webdav` is compatible with [git-remote-annex](https://git-annex.branchable.com/git-remote-annex/), because a user would need to declare *one* special remote (configuration) to use for cloning.
 
 It would be great to have authenticated, read-only access to webdav shares. Thanks in advance for considering!
+
+[[!tag projects/INM7]]
diff --git a/doc/todo/compute_special_remote.mdwn b/doc/todo/compute_special_remote.mdwn
index a4c57c0b27..5b9fa5bca3 100644
--- a/doc/todo/compute_special_remote.mdwn
+++ b/doc/todo/compute_special_remote.mdwn
@@ -60,3 +60,5 @@ I believe that no particular handling of annex key that are declared inputs to c
 ### Trust
 
 We would need a way for users to indicate that they trust a particular compute introduction or the entity that provided it. Even if git-annex does not implement tooling for that, it would be good to settle on a concept that can be interpreted/implemented by such special remotes.
+
+[[!tag projects/INM7]]