Is it possible to disable 'likes/reactions' per space in Confluence cloud?"

[Helen Gosper]

I'm aware of how to disable reactions (i.e, 'likes' etc) for an entire site, but does anyone know of a way to disable them for one space only on confluence cloud? 

[Dominic Lagger · Accepted solution]

Hi @Helen Gosper 

This is not possible on confluence cloud. 

Regards, Dominic

[Johnson_ Paul]

Why is this not possible?  Can you fix this?  This is a big over site.

[Jennifer Choban]

It really should be. It makes sense that we would want to use reactions internally, but wouldn't want them on customer-facing documents.

[Lizzie Burns]

another use case is that if i want to apply a custom footer to my space, it appears below the reactions, labels, comments. this reduces visibility of my custom footer. in order to get it to appear above those elements, i have to manually add it to every page in my space.

[Shaziya Tambawala]

Hi @Helen Gosper and @Jennifer Choban - I'm a Product Designer on Confluence Cloud Asmin Experiences and would love to learn more about how disabling likes/reactions would be helpful. Wondering if your concerns are related to any of the following:

• Security - if only the reaction count showed (without user details) would disabling still be important?
• Notifications on certain spaces?

Look forward to hearing from you - thanks!

[Jennifer Choban]

Hi @Shaziya Tambawala ,

We find reactions useful internally. We give a thumbs up to acknowledge that we've read a page,  etc. However, we have our public-facing product documentation in Confluence and I think  it looks a bit sloppy and unprofessional to have reactions on those pages.

Thanks  for working on this.

[Helen Gosper]

@Shaziya Tambawala my use case is identical to @Jennifer Choban's above, thanks.

[Johnson_ Paul]

It would be helpful to disable them because we don't want them on a given page.  There does not need to be another reason.  What is wrong with you?  Can't you trust your customer enough to give them what they ask for.  Is there a reason it needs to be there?  Other then you seem to think is does?

We could do this on the server version with an HTML script.  That's not supported in the cloud.  Please fix this.