Setting "Owned By" to a Group?
Asked by Victoria Philips:

I would love to be able to set the "Owned By" feature at the top of Confluence Cloud pages to a group, instead of an individual. Our teams change a lot and it may also not be a single person on the team that owns the content. Is there any way to choose a group instead?


Answers:
author: Michel Neeser
body: Hi [@Victoria Philips](/t5/user/viewprofilepage/user-id/3124602) and welcome!

Just to add to the comment of [@Shawn Doyle - ReleaseTEAM](/t5/user/viewprofilepage/user-id/815120): A central concept of Jira and Confluence in general is to always have an individual being responsible for a single piece of information, as nobody is *really* responsible if something belongs to a group. That's why you can't assign "Owned by" to a group.

If by "Our teams change a lot" you mean that users are deactivated on the instance, you can use the new Content Manager to find the pages without an active owner. Since you're on Premium, this feature is available to you, and you can find more information [here](https://support.atlassian.com/confluence-cloud/docs/manage-your-content-tree/).

Hope this helps!

comments: author: Victoria Philips
body: Hi Michel,  
Thank you for your answer :).  

We don't necessarily have people leave that often. Our Development teams just swap members a lot and they often move to other projects. However, their knowledge and responsibilities are transferred to their replacements. Groups can help a lot with automating department and team changes.

We use ownership for many different things, depending on the content. For policy, we do want a sole owner. However, we think guides and resources can be owned and upkept by a community.

Documentation is a secondary function to running our business. If we assign ownership to one person, they have too much responsibility. When instead, someone could reach out to a team and get support from one of several content experts.

There are times when I prefer individual ownership for certain content, but it would be nice to have both options, so that individual ownership could still be applied, but group ownership could be too.  


author: Kristian Klima
body: [@Victoria Philips](/t5/user/viewprofilepage/user-id/3124602)

You can... create a technical 'collective user'.

Say you have an IT team that needs to share ownership of their content. They probably have a corporate email like it@company.com.

So you can create a user in Confluence (with its own seat of course) using that email. You can then assign the ownership over the documents to that collective entity while the individual users would only contribute to the content.

Hope this helps :)

comments: author: Victoria Philips
body: Hi Kristian!

That is an intriguing idea. I'm going to explore this and see if it can help :).


author: Aron Gombas _Midori_
body: As [@Michel Neeser](/t5/user/viewprofilepage/user-id/1828853) wrote having multiple owners means that there is no real owner in practice, therefore it is discouraged. It is the same exact problem why a Jira issue can have only a single assignee.

Having said that, I see people regularly asking for multi-assignee implementations so there is a definite need for that. In Jira, you can use a "Multiple users" type custom field to implement it (although with some limitations).

In Confluence, the [Better Content Archiving](https://marketplace.atlassian.com/apps/123/better-content-archiving-and-analytics-for-confluence?hosting=cloud&tab=overview) app implements [page owners](https://midori-global.com/products/better-content-archiving-for-confluence/cloud/documentation/manage-the-content-lifecycle/quick-actions#set-owner) with the following advantages compared to the built-in owners:

* You can have *multiple* owners per page!
* You can have owners that own a *whole tree of pages*, we call these "content tree owners" (in other words, the owner is inherited by descendant pages!)
* You can have owners for blogs, too

It looks simply like this (note that both selectors allow multiple users and they can even be combined):

![quick-actions-dialog-set-owner-cloud.png](https://community.atlassian.com/t5/image/serverpage/image-id/331056i7EE2DE97F7237401/image-size/large?v=v2&px=999 "quick-actions-dialog-set-owner-cloud.png")

As you can have multiple users, it can help with your use case, too.

Give it a try!

*(Discl. it is a paid and supported app developed by our team. Free for 10 users!)*

comments: author: Victoria Philips
body: Hi Aron!

Thank you for the information about this app! That might be just what we need. I'll investigate this further with my team to see if it will meet our needs.


author: Shawn Doyle - ReleaseTEAM
body: Spaces and Pages can't be owned by a Group, only by an user.


Tags: cloud

confluence-cloud

ownership