Database Read Only Embedding

[SH]

Hi,

I've started to play around with the new Database feature and it looks good.

Is there any way to embed a read-only view of a database on another page?

My concern is that someone may accidentally alter a field on the embedded database while navigating the page. Ideally, I would prefer a person with edit permissions to the database to navigate to the database directly to make changes, while at the same time for any page that has the database embedded to only show a read-only version, even for that same person with edit permissions.

Is this possible?

Cheers,
Simon 

[Petter Isberg]

Hi.

I was just looking for this very feature. I think it would be very valuable as the risk of someone accidentally renaming a database or adding partial data because the view doesn't show all columns seems rather high.

@Divya SriramIf this is not yet possible, will you consider implementing it?

Best regards
Petter

[Divya Sriram]

Hey folks, great question. We have permissions for databases where you can configure just a set of folks to have edit access to the database, leaving it as essentially view only for everyone else. Would this help keep the database collaborative for those with edit permissions while leaving it as view only for everyone else?

Petter, you bring up an interesting point that someone adding a new entry might only enter partial data because the view doesn't show all columns <-- I think this might be a separate issue which is interesting. It sounds like you'd want every entry added to be thoroughly filled out for all the columns, even if the current view only shows a subset is that right?

[SH]

Unfortunately, I don't think that will work for us.

Ideally, it would be great for it to work just like Pages do, where I have to consciously Edit the page and then save it. Imagine the trouble you could get into if all Pages in a space were able to be edited in line; that's how I see Databases at the moment.

With the permissions, the currently available permissions are applied to 'Pages & Databases', so changes to one will affect the other. While It would be better for Databases to be split out as their own permission set, it still wouldn't achieve the  outcome I need, the prevention of accidental changes to the Database (even by users who need to be able to edit it like myself).

Cheers,
Simon 

[Jeff Madison]

Sometimes I'd like the embedded database view to be read-only for everybody, even people who have edit permissions on the underlying database itself. It's too easy to accidentally make edits to the database while you are just trying to read a page its on. If I need to edit the database entries, I can go to the database itself (or another page that has a view that isn't marked as read-only). Or possibly include a read-only/edit mode toggle on the embed.

Or better yet, create a new feature that allows us to query a database and render the results on a page as opposed to embedding.

[Divya Sriram]

That makes sense, thank you for share - I'll bring that back to the team

[Bernd Raesig]

@Divya any updates to this view permission request?

[Peter Kaiser]

In the original version of the database feature it was possible to configure the embeded Database view so that it was readonly. I wonder why this configuration hat been removed?

In fact the current version makes the database feature nearly useless for us, because we have a strict workflow for page editing and page approval. 

[David Fathers]

Same for us - Confluence databases are basically useless without a read-only embed at the very least.  Please let us make read only views, including for the database owner/editor users.  No reason to allow accidental edits.