Blog Permission Questions

I've updated the documentation to state that the "Moderate and Review Abuse" permission is required at either the blog level, the group that the blog is within, or at the site level.

(+) How do I configure and use blog workflows? - User Documentation - Verint Community 12.x - Verint | Telligent Community

For the Reporting permissions, the group level permission is the lowest level of permission.  

Thanks for the update to the documentation.

Should the group level permission allow blog application reporting data to be seen for application in that group or does it need the manage blog permission for that application as well?

Viewing reports for a blog does not require the Manage Blog permission, however, it should have at least the Read Blog permission.

Hmm.. I must be running into an edge case or some other permission issue then. The user has all but Manage Blog, Manage Blog Theme, and Manage Custom Pages for the blog application itself, but when impersonating that user, I have found no access to the Reporting control panel in the blog application and the blog data is viewable at the group aggregate level but trying to look specifically at Blog Details when accessed from the group reporting control panel results in the blog not being found by the search tool (and not selectable in a dropdown)

Adjusting permissions for reporting will require running the Reporting ETL for the permission changes to take affect in most cases.  

Okay. I'll check tomorrow as I don't really want to try to manually reset the ETL to rerun (unless this has been made easier in 12.1 that I'm not aware of)

A little more clarification on the permissions.  If you change the permissions the user who you've granted the read permission for the blog and the Group - View Group Reports permission can see the report immediately if they navigate to the blog itself.  They will see the pencil icon, which will allow them to see the Manage Blog => Reporting option.  Clicking this will list the different reports the user can access and provide direct links to the reports filtered to the blog.

In reporting, searching for a group or application requires the read permissions be migrated to the Reporting database.  In this case, the ETL would need to run before the user can search for the blog.

A little more clarification on the permissions.  If you change the permissions the user who you've granted the read permission for the blog and the Group - View Group Reports permission can see the report immediately if they navigate to the blog itself.  They will see the pencil icon, which will allow them to see the Manage Blog => Reporting option.  Clicking this will list the different reports the user can access and provide direct links to the reports filtered to the blog.

In reporting, searching for a group or application requires the read permissions be migrated to the Reporting database.  In this case, the ETL would need to run before the user can search for the blog.

Brian Dooley Does this also affect a user's ability to view a group's reporting if/when they're added to a group as a manager/owner to be able to see the group's reports? eg. ETL has to be re-ran so they can see the reporting after being added?

If so, that's really not intuitive or explained on the platform.

No, only search in the Reporting side is affected by the permissions and would need the ETL reran.  Otherwise, they should be able to navigate via the Manage Group > Reporting links.

Search would include finding the group to report on as a filter in the reporting though, wouldn't it?

It was my experience when adding a user to manage/own a group, that they couldn't view the reporting as they couldn't 'search' in reporting to find the group that they had just been added to?

Yes, they would not be able to search for the group to filter until the ETL ran after the permission change.  However, then can navigate directly via the  Manage Group > Reporting links.