Thanks Karl Cyr. It is a beautifully written very useful post, and we did try that - but a system level set up is too broad for us.
It would have been okay if I could set it up at global/system level and can restrict the interceptor to specific content type - for example: Keyword interceptor (moderation) at system level that only pushes documents and uploaded content with the keyword "project escalation" to the moderation queue.
Can I set it up like that by adding an additional property/modifying an existing one?
That also brings us to the second point that I had mentioned: the keyword interceptor email notifications mode kicks off an email when the keyword is used anywhere in these projects, but the keyword interceptor moderation mode does not route the content from the projects to the moderation queue (but it works fine for content posted in the space).
I went by the moderation inheritance rule in Jive 7 documentation (going by that, the moderation mode should work in my projects as well)
- Projects inherit the moderation settings of their container space or sub-space and are moderated by the Space Moderator(s), if there is one, and if not, by the Global Moderator(s). If there is no Global Moderator, the application will send the moderation request to the Full Access user(s).
Note: Projects inherit the moderation settings of their container space or sub-space except in the case of status updates posted in projects, which are moderated the same way as status updates posted in a group.
We are currently stuck at this point!