Database View - Ready Only - Share with Customers w/out a Login

[Daniel Warren]

Confluence Premium

We created a Release Notes page for our internal team that includes all bug/techdebt and feature updates.  This database has a column that determines if the release note displays on the "Customer View"

We then created a "Customer View" of this database and filtered to only show "Yes, show to customer" and then hide all columns not relevant/valuable to the customer.

Challenge:
1.  How to you embed ONLY the "Customer View" of that database in a new page?   It seems to always show the other views of the database.   
   ** we read about macros that would allow us to only embed the "view" and not all views, but we don't see an option to do that.  
2.  How can we share that new page with our customers, without requiring them to have a login.   (I think the answer is the "Public View" link, but then that exposes the page to anyone.  

[Staffan Redelius]

Hi @Daniel Warren and welcome.

As everyone else has already explained databases are all or nothing. I hope that we in the future can display only a view. 

For your second question you could investigate if the concept of Confluence guests could be an option to share information externally and still have control over who can access the information.

Confluence guests 

I hope this helps,
/Staffan

[Anna Mitina _Stiltsoft_]

Hi @Daniel Warren ,

Do you mean the Confluence database?

[Brant Schroeder]

@Daniel Warren The only way to do it currently is to clone the DB and remove what you do not want to share with the customer.  @marc -Collabello--Phase Locked- is correct it is all or nothing.

[Kris Klima _K15t_]

Hi @Daniel Warren and welcome to the Community.

The general notion on displaying selected content has two solutions.

A) You can experiment with excerpts / page include macros and permissions/restrictions.

The idea is that you can have a page with page-native content that you want to share and an excerpted/included content the original of which lives on a restricted page.

So if the original content is not available to public view (via permissions/restrictions), it should not be visible.

B) A more sophisticated (and manageable) approach is using conditional content but you need an app for that.

And because databases are a non-page entity, your mileage may vary when it comes to apps. 

[marc -Collabello--Phase Locked-]

Indeed, you can only share all or nothing.

Confluence databases, in their current form, are not suitable to data hiding and selective access.