Options for embedding Grist widgets in other sites about grist-core HOT 9 OPEN

Domain restrict.
Need Grist to be embedded only on specific sites. This is must have because if you sell datas in your websites, other people cannot somehow find the link and embed in their websites

from grist-core.

Data scraping protection is impossible these days. I think Grist can protect 70% is somewhat perfect:
1/ With bots: The best way i can think of is make your "embedded table/dashboard" integrate with "data scraping service" like scrapeshield https://blog.cloudflare.com/scrapeshield-the-scaled-up-deep-intelligence/
2/ Human: "forget bot, I will drag all the table and copy to my excel"
Grist: "I have 2 options, (can drag all table to copy) and (cannot drag all table to copy) when share to public, and... in the backend I can choose the switch buttons off/on: can download, can filter,...)

from grist-core.

Great embed-related requests from users I've spoken with:

• Enable search bar on embed
• Ability to remove "download" and "print" options on embed
• Full document embed that allows "jumping" to referenced tables/pages

from grist-core.

Thanks @smithqueen1991. We do plan to generalize access control by origin (mentioned https://support.getgrist.com/access-rules/#access-rule-conditions) to allow users to control which documents can be accessed from which site. I think that will address your main concern.

Imagine for a minute that restriction by domain is set up. Are there other security measures that are important for you? Do you worry about people simply copying and pasting your data into their own site, or retyping it if copy/paste is disabled?

from grist-core.

We've documented what is possible so far at https://support.getgrist.com/embedding/#embedding-grist

from grist-core.

Related: #91

from grist-core.

+1 wish for "embed editable anonymous table". There are use cases where this approach makes sense. Of course security measures are often also needed unless the table is served from server side on a web app. Additionally, embedding a user (even on URL like ?login=username&password=userpassword) has also use cases.

from grist-core.

@tietoafinlandoy I believe if you add /m/default?embed=true to a URL, and set public access on the document to editor, viewers of the embedded page will have edit access. The /m/default overrides switching to read-only mode, as Grist does by default currently for embeds.

from grist-core.

@paulfitz Actually, turns out that ?embed=true locks the fields (show the lock icon when trying to edit) when using iframe to embed the table but using ?style=light leaves it editable! So it works now for us. Thank you for answering. We went on to learn the trick here: https://support.getgrist.com/embedding/

from grist-core.