Skip to main content

Sharing Your Database Schema with Anyone

· 3 min read
Mishall Afzal
Mishall Afzal
Co-founder, CTO

Database schemas are collaborative artifacts. They're discussed in PR reviews, included in RFCs, pasted into architecture docs, and explained to stakeholders who've never written a line of SQL. But getting a non-engineer to open a migration file and understand it is asking a lot.

Public threads solve this with a shareable link to a read-only, interactive version of your schema — no account, no installation, no friction.

What is a public thread?​

Every thread in TalkingSchema has a canonical URL. By default, that URL requires authentication. When you make a thread public, it becomes accessible to anyone with the link — fully rendered, pannable, zoomable, and readable.

Viewers can:

  • Browse the entire ERD on the canvas
  • Click into any table to see its fields, types, and constraints
  • Follow relationship lines between tables
  • See enum definitions

Viewers cannot make any changes. The schema is read-only. There's no "edit" button, no chat input, no way to accidentally modify anything.

  1. Open any thread in TalkingSchema
  2. Click the Share button in the top toolbar
  3. Toggle Public access on
  4. Copy the generated URL

The link looks like:

https://talkingschema.ai/public/{thread-id}

You can share it anywhere — a Slack message, a Notion page, a GitHub issue, a product spec. Anyone who opens it sees the current state of the schema.

tip

Public thread links are live. If you update the schema, the link always reflects the latest version — there's no need to regenerate it.

Embedding a schema in a page​

Public threads also work as iframe embeds. This is useful for documentation pages, blog posts (like this one!), or internal wikis where you want the schema visible in context.

Here's an example of a live, embedded public thread — an e-commerce schema with orders, products, customers, and inventory tracking:

E-commerce Schema
Open full screen ↗

To embed in your own MDX or HTML:

<iframe
  src="https://talkingschema.ai/public/{your-thread-id}"
  width="100%"
  height="640"
  style="border: none; border-radius: 12px;"
  title="Schema diagram"
  sandbox="allow-scripts allow-same-origin allow-forms allow-popups allow-popups-to-escape-sandbox"
  allowfullscreen
></iframe>

In pull requests — link the relevant schema thread so reviewers can see the data model without having to read migration files. They can click through relationships, check foreign keys, and confirm field types all from the PR page.

In architecture docs — embed the schema directly in your Notion, Confluence, or internal wiki page. The schema stays live; you don't need to update a screenshot every time a table changes.

In onboarding materials — new engineers can explore the schema at their own pace. Tables are clickable, relationships are visual, and there's no risk of accidentally changing anything.

With external stakeholders — designers, product managers, and clients can understand the data model without needing to learn SQL or get access to your database.

Privacy and access control​

A few things worth knowing:

  • Public links can be revoked at any time — toggle public access off and the link immediately stops working
  • The link doesn't expose your conversation history or any agent context, only the schema itself
  • Public threads are indexed by URL but not by any search engine or directory (no SEO crawling)

Public threads and shareable links are available on all plans. To try it, open any thread and hit Share.