Hi!

 Talk - Advanced Inline Comments has a feature that allows setting visibility restrictions for the comments on a space level or/and for the specific comment thread. Say, you want your comments to be visible only internally. You can set space permissions for the comments only for a group or/and users who can view them. However, any user who can make comments can change restrictions for specific comment threads.

This means, that by default all the comments in the space will be visible only to the groups and users listed. But if a user wants to change viewing for a specific comment (for example, to discuss something privately or restrict comment only for himself), they can do it.

Years go by and Atlassian continues to prove it is only interested in money, not its own users.  We are ditching all Atlassian products as soon as we can.

Our team have the same issues mentioned above. We cannot use inline comments as they are visible to anonymous users. It's such a shame.

We just spend time getting rid of talk, because, who wants a 3rd party plugin for things that are built in.... Since, confluece added inline comments, we found talk unnecessary... and then this... searchable comments .  please fix asap!

It would be so useful to be able to restrict the view permissions on comments. The feature isn't much use to us in its current state as we don't want external users to see internal feedback or change requests etc on live documentation.

The mentioned talk-inline plugin is useless for cloud accounts.

And it would be really great to have a built in solution for this quiet common request anyway.

With Talk-Inline Comments you can set default Space comments viewing permissions, as well as permissions for specific comments and do a lot [more|stiltsoft.com/blog/2015/01/comparison-talk-and-confluence-inline-comments/].

The inline comments could be a very cool feature, but right now what you get is a lot of added noise on the page for everyone reading the page because the editors are discussing things. IMHO inline comments make this more urgent and on top of that, permissions for normal and inline comments should be separate. They (can) serve a very different purpose, especially in technical documentation pages, so they need their own set of permissions.

The new inline comments only make this worse as customers reviewing the technical documentation can also see resolved comment threads. Inline comments and in-context comments on screenshots would have been so helpful when the team is reviewing product documentation and customer-facing KB.

I cannot understand why we can have the ability to hide comments in JIRA but not in Confluence. It makes it more difficult to use Confluence for technical documentation - which appears to be one of the primary uses for the wiki (from their documentation).