We just updated to 6.0 last weekend (yay!) and I recently learned from several of the managers of our groups that they no longer have the option to "Edit" discussions in their communities. That ability used to be available for community managers in 4.5.6, which is the previous version that we were on. I would have thought that community managers would continue to have the ability to edit any posts that were created in their communities, but it looks like they cannot.

Also, community managers cannot edit the tags on discussions posted in their communities, even if they have "Quick Tagging Mode" turned on. They can still edit tags on documents, but not discussions. I still have the ability to edit both discussion tags and posts, as a full administrator of the site, so I didn't realize that this capability was different for others.

Is this something I have configured wrong in our admin console? Or just a strange new quirk in Jive 6? Does anybody else who has Jive 6 have any thoughts on this?

The ability for space/group admins to edit discussions, and to update the discussion tags, went away in 5.0. There has been discussion about it elsewhere, can't remember if there is an idea created to change to permissions back. John Schwiller might remember.

Hi Caitlin, I recently discovered this in Jive 5.0... and I was curious if it would be fixed in 6... I guess not . If you find the idea, please post it back here as I would love to vote on it. Our groups admin complain about this all the time

And I also just realized that people who author a blog in a space or group where they aren't an admin also can't move or delete their own blog. I'm a bit baffled and annoyed by this. If I wrote it, I want to be able to change my mind about whether it is seen and where, without getting someone else to do it for me.

This is really disappointing. One of the major benefits with Jive is the power of the search. Our average users are not accustomed to the concept of tagging, and therefore, we community managers need the capability to help them out and tag/re-tag discussions, documents, blogs, etc, particularly after we better learn our users search habits.

Max Calderon from memory I discussed this on a case for one of our clients last year where I no longer have access to the cases. It might have been handled by Izabela Sowula or a colleague in UK, possibly in the first half of 2013. You might be able to find it on a quick search in the appropriate secret group?

I recall that the response was that a customer had previously raised the ability to edit as a security concern and that edit rights had been removed by Product Management. I think the end result of the case was that our concern would be fed back as a request to reinstate this functionality. Hope you can find what I'm remembering. I wouldn't have raised an idea on it as Support passed the request back to PM.

I think the issue here goes to something we've seen happen several times. One or more customers complain or raise security issues, and Jive disables a feature entirely. What I wish would happen instead is that the feature would become configurable. It is very frustrating for communities that are less restrictive to have to live with implementations made to accommodate highly regulated businesses.

I think generally this is the case in roadmap conversations, and ends up guiding feature build discussions so that Jive ends up building the feature a certain direction before any configuration is made available, totally agreed (and have voiced the same opinion) that we need to have more configuration available.

Also, community managers cannot edit the tags on discussions posted in their communities, even if they have "Quick Tagging Mode" turned on. They can still edit tags on documents, but not discussions. I still have the ability to edit both discussion tags and posts, as a full administrator of the site, so I didn't realize that this capability was different for others.

and although I need to confirm with Products I'm pretty sure this sits at the same place, where anyone with "admin" permissions on a group cannot edit these items in a discussion. That said, this isn't the same for spaces, so larger areas and folks with certain overrides can manager these.

I spent quit some time reading all the tagging related discussions in the Jive community. Having implemented Jive 5 at a large organization I was also used to the model, that a community owner is in full control of it's content (including tagging). With Jive 6 this changed to a more restrictive approach giving more "power" to the content creators. Personally I fully agree with Belinda Benton 's comment - a community owner should be able to tag any content in her/his community.

What is the general go-forward strategy for tagging & tag-management with Jive 7 and Jive 8?

I believe there is still a lot of potential for clarification and maybe optimization in the area of tagging. It would be great to get some insights where this is going.

For our implementation of Jive, we ran (and are still running) a project on self-service groups for various internal applications and services.

These groups rely on users being able to find information easily and since tagging underpins search augmentation and discovery, it's imperative to have good hygiene. As expected (and I agree with Scott Brown on this one), whilst the users are discovering how the tagging system (and the concept itself) works, allowing community managers to curate the tags is essential. Not only that, but they also help lead by example and set the standards.

On one hand, I understand the need to preserve any messages as intended (i.e. not allowing group owners to edit discussions), but curating the meta-data should be something that groups admins have the power to do.

Thank you for the heads up. Indeed, it is similar but not exactly the same.

However, I did discover which could use some up votes.

My own idea would be a subset of this: "Allow group owners / administrators to modify tags for all discussions in their group". This retains the 'sanctity' of users not having their discussions modified, but still allows group owners to curate the meta-data to aid search and discovery.