The customer reported an issue wherein while trying to make all social groups view only, by changing the access of registered users to 'view only', the testing shows that the user can still create or modify new content in social groups.
This article provides possible reasons for this issue.
It is not possible to make all social groups 'view-only'. Some of the reasons for not making the social groups 'view-only' are:
- There are four basic types of groups: open, members-only, private, or secret. Regardless of the type, content creation is not restricted.
- Permissions for each content type in a social group, are not configurable. They are essentially unlimited (read, create, comment, attach a file, etc.). Projects created inside a social group inherit these permissions. This explains why even if the user group was given 'read-only' access, the user was still able to post content within a social group.
- Content is visible to everyone in the community. Anyone can create, like, share, and comment on content.
Jive is not meant to be a "view only" platform so there is no easy way to give someone "view only" access. And the changes that would need to be made will affect all users - not just the one person.
- The customer would have to remove this user's access completely from the social groups, so they would not be able to see them either. If they give the user "view" access to social groups, they can still participate in an open or restricted group.
- The only way to prevent this is to make groups private or secret.
- The customer would have to remove the ability to create personal content from ALL users as this is a community-wide setting and cannot be controlled via permission groups.