One possible way is to change community permissions
if people from certain permission group should be able to publish content across community ( selected community or root community) and other users can only view it.
This can be implemented by changing community permissions to view only for "Everyone" and adding the group with required permissions.
Hopefully all the sub communities will also inherit the permissions but not very sure and need to check it.
I tried your solution and sadly it doesnt seem to work. Here is what I tried (I hope I understood your tip correctly) :
- I've set the permission on the default space (root) to view only for "Everyone"
- I've set the permission relative to blogs so that "Everyone" could only read and comment personnal and system blogs.
So now if a standard user try to create a blog post, he can only post it to a specific space (no more posting in a personnal blog, wich is what I want).
But, for the following contents types, the same standard user can still post to everyone (in the community) :
I really wish I could achieve the same result I'm having with blog post with all the other contents.
Do you have a clue as to what can be done?
You are right
Even after removing the Everyone and Registered Users, and adding custom group with custom permission levels, users are able to contribute to the root community.
It seems it is inherently taking the permissions for these two groups. I tested this with jive 6.
I am not sure why this is happening.
Finally, I've got confirmation that there is no way to configure Jive to achieve this. The only way to do it would be to customize the template to hide the where you choose "publish to the community".
This approach has one issue
What if user directly hits the create action url (maybe saved or bookmarked earlier)
1 person found this helpful
The solution can be to create a permission filter and add it to security filters (Filter chain proxy) to check for permissions again (without current bug) in a plugin along with UI customisation as mentioned by you.
I hope this will work
Thanks! We will keep that in mind if we decide to go that way after all.