Sign inBook demoStart free
Docs/Sharing

Embed a thread

Share a thread by link, or embed it in another tool with view, comment, or edit permissions.

Last updated 2026-05-09

A thread can be shared three ways: a link to view in Arcus, an embed for another product, or an export to a static file.

This guide walks the link and embed paths, and the permission model behind them.

Share by link

Open any thread, click Share in the toolbar. You'll see three permission options:

  • View — recipient can read the thread, including all citations and the chart, but can't add turns or edit. Most common.
  • Comment — view, plus the recipient can leave inline comments on turns. Useful for review workflows.
  • Edit — full access. Recipient can ask follow-ups in the thread. Counts as a tenant seat.

Click Copy link. Send it however you send links. The recipient opens the URL — if they're not signed in, they see a sign-in prompt; if they are, they go straight to the thread.

Permission scopes

Every share link has a scope. Three are common:

  • Anyone with the link — public link, no sign-in needed for view-only. Useful for a CFO who wants to forward an answer to a board member without onboarding them.
  • Tenant members only — anyone signed into your Arcus workspace can open the link. Default for comment and edit.
  • Specific people — only the email addresses you list can open the link. Sign-in required.

Public links can be revoked at any time from Settings → Sharing → Active links. Comment and edit links can also be revoked there.

For sensitive data, prefer "specific people" — public links can leak.

Embed in another tool

For embedding a thread inside another product (a CS dashboard, a portal, a customer-facing app), use the embed path.

In Settings → Sharing → Embed, generate a signed embed URL. The URL contains:

  • A signed token (HMAC) tied to your tenant.
  • A scope: which thread, which permission, which expiry.
  • Optional parameters: a viewer_id for per-user access, a theme for light/dark.

Drop the URL in an <iframe>:

<iframe
  src="https://arcus.usearcus.ai/embed/thread/abc123?token=..."
  style="width:100%; height:600px; border:none;"
  title="Q1 paid pulse"
></iframe>

The embed renders just the thread — no Arcus sidebar, no settings. The iframe respects the permission encoded in the token.

RLS still applies

Embed permissions don't override row-level security. If the embed token is for a viewer who doesn't have access to the underlying warehouse rows, the answer card renders empty with a "no data" placeholder.

For customer-facing embeds where you want each customer to see only their own data, encode viewer_id in the token and configure the semantic layer to filter by that field. Contact us at hello@usearcus.ai if you're setting up multi-tenant embedding — there are a few patterns we recommend.

Export to PDF / Notion / Slack

For static export, the thread toolbar has Export with three options:

  • PDF — generates a printer-friendly PDF with all turns, charts, and citations. Useful for board prep.
  • Notion page — pushes the thread to a Notion database (requires connecting Notion in Settings → Integrations).
  • Slack post — posts a formatted summary of the thread to a channel.

Exported content is a snapshot — it doesn't refresh.

Comments

If you shared with Comment permission, recipients can leave inline notes on any turn. Comments are threaded (reply chains) and can be resolved.

You'll get an email + an in-app notification when someone comments. Reply from email or in Arcus.

Comments are part of the audit log — every add, edit, resolve, and delete is logged with timestamp and user.

Revoking access

From Settings → Sharing → Active links, every active share has a row with:

  • Thread title.
  • Scope (anyone / tenant / specific).
  • Permission (view / comment / edit).
  • Created by + created at.
  • A Revoke button.

Revoking is immediate. Anyone with the link gets a "this link has been revoked" page. The thread itself isn't deleted.

Related