Source

Integrations, import & export — found from sitemap — Lucidspark

Checked for Lucidspark on 1 Nov 2026

Technical details

type: page
http status: 200
content hash: sha256:9a6c95459b95dae96391a64543ad193e85b74246b11a97e86c906918ff3a4777
permission: robots_ok
screenshot: Screenshot on file (internal exhibit, not published)

Cited by

Cookie embed recommendation Report an error

“We recommend using cookie-based embeds for most use cases, because the API is significantly easier to use.”
Token embed access Report an error

“However, if you want users to be able to view embedded documents even if they don't have access in Lucid (or don't have a Lucid account), then you'll want to use token-based embeds instead.”
Token embed oauth management Report an error

“The token-based embedded experience requires your integration to manage the granting and storage of OAuth 2.0 tokens securely. Cookie-based embeds do not require any token management.”
Cookie embed no access behavior Report an error

“The iframe will display a "request access" or "log in" message, as appropriate.”
Embed auto update Report an error

“Lucid embeds always update when changes are made to the original document, with one exception: token-based embeds can be configured by the user to not automatically update, in which case they display a snapshot of the document at the time the embed was created.”
Embed third party cookies Report an error

“the embed APIs use the browser's Storage Access API to request cookie access as needed.”
Breakout board embed Report an error

“Currently, breakout boards can't be selected in the document picker, so cookie embeds are the only way to embed these boards.”