Published Document iframe Embedding

I am attempting to embed a published document into an iframe on a site and so far the result is a blank iframe. The point of using the published document vs the embed function is to eliminate the Open in Coda button in the top left corner. Has anyone successfully done this and am I missing something obvious?

Dear @Justin_Kelley

Sorry, to clarify I’m trying to do the opposite. I’m trying to embed a published coda doc into an external site. I am aware that you can use the Embed tab of the share function to do this, but that includes the Open in Coda button in the top right instead of the published clean version of the page.

1 Like

Hey Justin,

I’ve done that a number of times but remember - this is not super secure and anyone can find a way to reach out to your data anyway:

@Stefan_Stoyanov

This looks like the implementation I need, but I am a bit unclear on how you get it to be non-editable even when mode=play …

Does this have to do with the class = frame? Or does this rely on a web flow component?

I really know very little about the mechanics of the html (obviously)

Basically my goal is to get the published version to appear in an iframe… But as far as I can see, it will not embed the custom domain

Thanks!

Hi Damon,

In short - I embedded the iframe and told the content within the iframe to be moved with up a certain percentage so that the awful links that lead to the data tables are “hidden” from the frame. It’s nothing too special and I haven’t had breaches but is not near secure enough. It’s just visually deceiving the visitor.

Until Coda remove these links to tables from the upper left corner, I would not recommend using a document that has sensitive data hidden. Coda sucks in security.

1 Like

Gotcha… Thanks for the quick response.

Beyond hiding elements, I noticed your example cannot be edited and is in play mode…

Oddly enough for mine … also in play, you can edit elements but these changes don’t show up… Is this due to locking settings?

Yes. As far as I remember (I dont’ use Coda actively anymore for the reason we discuss here) you would need Teams account to be able to set the right settings for Play access but without allowing the people to actually edit elements because they are restricted to only view them.

Again, the whole access rights thing in Coda is absolute mess. It’s more like a Lab where you mix and experiment, rather than proper Settings. So get ready for 20-30 hours in experimenting, if you are looking for a more complex document.

1 Like

Thanks so much for being generous with your time! @Stefan_Stoyanov