Is there a way I can hide sensitive data based on access role without having to remove it?

[James Conlon]

Example. I have confidential customer data and I am giving someone access to view only. Is there a way I can blur this out or hide it from their view without having to delete the data?

[Benjamin · Accepted solution]

Not out of the box. You will need a plugin. However, most plugins I've seen are for on-premise. 

[James Dellow]

The Visibility for Confluence add-on is available on Cloud.

[Bill Bailey]

I have written macros that only show content based on group membership. Pretty easy solution, BUT no user macros on the Cloud. I have always felt that user macros were a very powerful feature to allow users to plug holes in Confluence. Now with Cloud they are gone.

[James Dellow]

"Now with Cloud they are gone." needs to be qualified.

User Macros were never in Cloud, instead, we use the Atlassian Connect framework. It does have a higher barrier to entry than user macros, but is available to everyone if they want to write their own customisation.

Now we have Forge (in beta atm), which reduces the barrier to entry a little (you don't need to worry about hosting) and it is also bringing new features that weren't available in user macros or connect.

[Bill Bailey]

Yes, what I meant was that they are not a part of your Confluence solution matrix in Cloud, one that has a long history and is well understood. I see many questions here that could be easily addressed with a user macro in short order.

And yes, there may be new things you can do with the new beta tools, but the fact that you cannot have a custom domain and the limited branding, makes Cloud a non-starter for corporations (sort of like have an AOL email address). Plus I really don't want to have to re-engineer my entire set of solutions. Not to mention no version control - a feature can suddenly disappear.

Now if I were new to Confluence, the Cloud might be OK, once they allow custom domains (been an open issue nearly for 10 years - see CLOUD-6999).

[James Dellow]

You would need to move the confidential part to another page (say a child of the original page), then restrict access to that child page. Next use the except macros to include the confidential content back into the original page.