Skip to main content

Publish & share demos

Publish and share a demo: create it from a template, then set who can open it, the opening screen, what viewers see, notifications, and embed code in Demo preferences.

Updated Nov 5, 2026

Publish & share demos

Overview​

If you’ve been working through the Create Demos series in order, you already know how to:

Create and share templates

Set display settings

Capture screens

Create guides for guided demos

If those workflows feel familiar, you’re ready for the next step.

This guide covers how to publish demos, share them, and manage the settings that shape the viewer experience after a demo goes live. Whether your demo includes guides or not, the publish and share workflow is the same.

Why this matters:
Publishing is more than generating a link. It is where you define access, viewer experience, CRM connection points, demo behavior, and how the asset will actually be used in the field.


Preview Demos​

Before you publish and share, use Preview to review the demo the way viewers will see it.

This is the best moment to catch anything you want to adjust before the demo goes live.

Preview button in Walnut Editor

How to Preview a Demo Before Publishing​

Open the template in Edit mode.

From the header, click Preview and review the demo.

If you want to make edits, return to the editor and update the template.

Once the experience looks right, you are ready to publish and share.


How to Share Demos​

Walnut demos can be shared in a few different ways depending on how you want the experience to be used.

Direct demo linkEmbed code for a webpage or external experiencePlaylist as part of a broader packaged experience

The rest of this guide focuses on how to publish the demo itself and configure the settings around that share workflow.


Create Demos​

Create and Share Demo button in Walnut

Before you click Create & Share Demo, it is worth thinking through how the demo should behave once it is live.

Helpful questions to ask before publishing:

Do you want to personalize the demo with customer or organization names?Do you want to include a specific welcome message?Who should be able to access the demo?Do you want to connect the demo to a CRM opportunity?Who should be able to make changes later?For guided demos, which elements or moments should be emphasized?

Best practice: The strongest publish workflows start with the end use in mind. Think about audience, access, CRM tracking, personalization, and where the demo will be shared before generating the link.

How to Create and Share a Demo​

Navigate to the template and click Create & Share Demo in the header. The launcher opens in two steps:

  1. Demo Details — name the demo (use the prefilled name or update it), select a Goal, connect a CRM opportunity (select an existing one or enter a new one), and fill in any variables.
  2. Demo Preferences — the same groups, in the same order, as the Demo preferences modal you open from the library later: who can open the demo, the opening screen, what viewers see, presenting and sharing, notifications, Buyer Xpert, and embed code.

Click Continue to Demo Preferences to move from the first step to the second. When everything looks right, click Save Demo & Copy Link. The choices you made in the launcher are already applied when you open Demo preferences from the library.


Email Verification​

When you collect viewers' emails, you can also require viewers to verify that address before the demo opens — so the emails in your analytics are real mailboxes, not typos or throwaways.

Turn it on for a single demo​

  1. Open Demo preferences on the demo and go to Demo opening screen.
  2. Under Email gate, turn on Collect viewer emails.
  3. Turn on Verify emails.

Verify emails only works while Collect viewer emails is on — verification has nothing to verify without it. If the demo has an embedded lead form, email collection (and therefore verification) is unavailable until you remove the form. For playlists, use the playlist's Settings panel.

Set the default for your whole account​

Settings → Access Control → Email verification has three options:

OptionWhat it does
OnNew demos and playlists start with verification on. Creators can turn it off on their own assets.
RequiredNew demos and playlists require verification and creators can't turn it off. Existing demos and playlists keep their current setting.
OffNew demos and playlists won't ask viewers to verify.

With Required, Verify emails appears on and locked in Demo preferences, with the reason shown next to it, and Collect viewer emails is locked on with it. Access Control needs Collect Viewers Email on before you can set this.

What the viewer sees​

  1. The viewer enters their email in the welcome message (email gate).
  2. They get a Check your email screen, and an email with a verification link.
  3. Clicking the link opens the demo.

Good to know:

  • The link expires 15 minutes after it's sent.
  • Viewers can send themselves a new link after 60 seconds. The new link replaces the previous one.
  • A verified viewer stays verified in that browser for a while, so returning viewers aren't asked again.
  • Use a different email on the waiting screen lets the viewer start over with another address.
  • In an embedded demo, verification can't finish inside the embed, so embedded viewers continue in a new tab to verify.

Bulk-Add to Allow and Block Lists​

Gating a demo to a long list of approved buyers — or blocking an entire competitor list — does not require typing one email at a time. You can add a whole list in a single action.

Paste or Upload a Whole List​

In Demo preferences → Who can open it, set Link access to Specific people. The list appears below it.

Paste in your emails and domains, separated by commas, spaces, or new lines — mixed separators are fine.

Or upload a CSV containing the list.

Everything is added at once, and a toast confirms how many entries landed.

The List Cleans Up as You Go​

You do not have to pre-clean your input. Walnut handles the messy parts and tells you what it did:

Duplicates are skipped — the same address twice in your paste is added once.

Entries already on the list are skipped — re-uploading an updated list will not create duplicates.

Invalid rows are flagged rather than silently dropped, so you can see exactly what did not make it and fix it.

Pro tip: Because already-listed entries are skipped rather than rejected, keeping one master CSV per list and re-uploading it whenever it changes is a safe, repeatable workflow.

Find Entries in a Long List​

Once a list grows, the list is searchable and filterable, so you can confirm whether a specific address or domain is on it without scrolling.

Set the Company-Wide Default (Admins)​

Admins can apply an uploaded list in one of two ways:

To a single demo — the list applies only to the demo you are configuring.

Merged into the company-wide default — the list becomes part of the default applied across the company's demos.

Merging is additive: existing entries are never overwritten. This makes the company default safe to extend over time — for example, adding newly identified competitor domains to the block list without disturbing what is already there.

🔑 Learn more about Roles & Permissions.


Get Ready to Publish & Share​

Once the launcher's Demo Details and Demo Preferences steps are set, click Save Demo & Copy Link. The demo link is copied to your clipboard and the demo is ready to share.

Tip: Before sending the link externally, open the live demo once and do a final viewer-side review. You can change any setting afterwards in Demo preferences, covered in the next section.


Set Demo Preferences​

Demo preferences give you control over a demo after it's published: who can open it, what viewers see first, how the player behaves, who gets notified, and how it's embedded. You can change them at any time, including after the demo has been shared. For a full tour of the modal, see Demo preferences.

How to Open Demo Preferences​

Go to your library and find the demo you want to update. Click the three-dot menu and select Demo preferences. (Get embed code on the same menu opens it straight on the Embed code group.)

The modal shows a rail of groups on the left, each with a one-line summary of its current state (for example, Anyone with the link or Guides on), and the selected group's settings on the right:

  • Who can open it
  • Demo opening screen
  • What viewers see
  • Presenting and sharing
  • Notifications
  • Buyer Xpert
  • Embed code

Every change saves as you make it — there's no Save button. The header shows Saving and then Saved. The footer has an Embed button that jumps to Embed code, and Copy link, which copies the share link built from your saved settings.


Who Can Open It​

Who can open it in Demo preferences, showing Link access, Access code and Expiration date

  • Link access — Anyone with the link, Specific people (allow or block emails and domains), or No one (pauses the demo for everyone).
  • With Specific people, choose Only these people or Everyone except, then add emails or domains. If a viewer is blocked and tries to open the demo, they see This demo is no longer available. To add many at once, see Bulk-Add to Allow and Block Lists.
  • Access code — viewers type a code before the demo opens. Codes are case-sensitive and 6 to 255 characters.
  • Expiration date — the demo stops opening at the end of that day, UTC.

Demo Opening Screen​

Demo opening screen in Demo preferences, with the Email gate and Welcome screen settings

  • Email gate — Collect viewer emails, Verify emails (see Email Verification above), and Accept personal emails.
  • Welcome screen — shown when email collection is on: Show your avatar (taken from your template or company settings), Colors (Branded or Neutral), and Welcome message. Click Preview to see the gate the way viewers will.

What Viewers See​

What viewers see in Demo preferences, with the Guidance settings

  • Guidance — Show guides; Guides toolbar, with When the demo opens (Closed or Open) and Position (Bottom left or Bottom right); and Highlight clickable elements, a soft pulse that shows viewers where they can click.
  • Playback — Autoplay (guides advance on their own) and Narration (guides read their text aloud). While Autoplay is on, you can also set Seconds on each step (leave it empty to keep the demo's own pace) and Loop (start again from the first step at the end).
  • Language — shown when the demo has translated guides: the Demo language viewers see first, and a Language picker that lets viewers switch. See Set the default language of a demo.
  • Branding — the demo's Theme. A theme change saves right away and new links show it at once.

What viewers see in Demo preferences, scrolled to the Playback and Branding settings

If a setting is dimmed with Update this demo to use this setting. It was published before the setting existed., run Update Demo on the live demo first, then come back and change it.


Presenting and Sharing​

Presenting and sharing in Demo preferences, with Share button, Readable by AI and search engines, Seller Co-pilot and Pre-flight


Notifications​

Notifications in Demo preferences, with Deal owner, Account owner and Teammates

Under Tell me when someone views this demo, turn on Deal owner and/or Account owner (both from your CRM, by email or Slack), and use Add teammates to pick anyone else on your team. Learn more in Notify deal owners and teammates.


Buyer Xpert​

Turn Buyer Xpert, the in-demo AI guide, on or off for this demo, set its hand-off (show a lead form or open a link), and pick its welcome video. Only company admins can change Buyer Xpert settings for a demo.


Embed Code​

Embed code in Demo preferences, with the Full page layout toggle and the Copy embed code button

Turn on Full page layout if the demo should fill the whole page instead of a frame, then click Copy embed code.

Embed notes:

Paste the embed code into the target section of your webpage.

The default embed uses 100% width and height of the container, but those values can be adjusted.

The embed code is built from your saved settings, so copy it again whenever you change them. A shared link, by contrast, reflects the current saved settings each time it opens.

By default, a Walnut watermark appears on the bottom-left side of the demo. White label custom domains remove the watermark as part of that paid add-on.

Always preview the embedded demo to confirm spacing and layout. Learn more in Embed Demos.


Make Changes to Published Demos​

If you need to adjust a published demo, go back to the template, make the updates, and republish or update the live demo depending on your goal.


Update a Demo​

Updating a demo is useful when you want to improve or refine a live version without changing its URL or embed code.

However, updates overwrite the current live demo version, which means analytics remain grouped under the same demo. If version comparison matters, you may want to create a new demo instead.

See it in action:

Update a Demo from the Template​

Navigate to the demo template.

Click Create & Share Demo.

Click the three-dot menu next to the version you want to update.
Update demo option in WalnutClick Update Demo. The URL remains the same.

Update a Demo Without Opening the Template​

Make sure the latest changes are already saved in the template.

In the relevant library, hover over the demo row or click into it.

Open the three-dot menu and select Update Demo.
Update demo from library menu in Walnut


Create Multiple Demos from One Template​

One template can support many demo versions.

This is especially useful when you are changing variables such as company name, avatar, welcome message, or use-case framing and want to preserve the current live demo while creating a separate version.

How to Create Multiple Demos from One Template​

Open the template in Edit mode and make the changes you want.

Preview the updated experience.

Click Create & Share Demo.

Rename the new demo version.

If the share settings are correct, continue.

Click Save Demo & Copy Link.

The next time you create a demo from that template, you will see the previously created demo versions in the same workflow.


For more on connecting demos to Salesforce, see Connect to Salesforce.


Specific Use Cases​

Here are a few common scenarios and how they work.

1. Delete a Guide in a Template After You Publish a Demo​

Once a demo is published, it is standalone. Deleting a guide from the template will not change the already-published demo automatically.

However, if you later run Update Demo, the live demo will pull the latest template content and the deleted guide will no longer appear.


2. “Demo Not Available” Message​

If you see this message, here are the first places to check:

In Demo preferences → Who can open it, check the following:

  • Expiration date: If it's on, make sure the date hasn't passed. Extend it or turn it off.
  • Link access: No one pauses the demo for everyone. With Specific people, confirm the viewer isn't blocked.
  • Access code: If it's on, make sure the viewer is using the correct code.

Summary​

Publishing and sharing is the stage where a demo moves from build mode into real use.

It is where you decide how the experience should be named, who can access it, how it should look, whether it connects to CRM workflows, and how it should behave once it is live.

With the right publish settings, demo preferences, and update strategy in place, you can turn one strong template into a scalable demo workflow that is easier to personalize, track, and manage over time.

Final Takeaway:
A strong demo is not finished when the build is done. It is finished when the share experience, access settings, and live behavior are all aligned with how the demo will actually be used.

Was this helpful?