Settings and Branding

Branding Is About Trust

Branding in Supademo isn't about making demos look pretty. It's about trust.

When branding is consistent, demos feel legitimate, thoughtful, and professional. When it's inconsistent, even a strong demo can feel slightly off. Viewers may not be able to explain why, but they feel the difference.

That's why Supademo treats branding as something intentional, not something you make up as you go.

Workspace-Level Branding

Most branding is defined at the workspace level through themes, and that's by design. At the workspace level, admins set the visual and behavioral standards that every demo inherits automatically. This includes things like logos, colors, fonts, hotspot styles, CTAs, and other shared defaults. We'll cover workspace themes in more detail later in the course on workspaces.

Once those standards are in place, every new Supademo created in that workspace follows them by default. This removes guesswork for creators and keeps demos consistent across teams.

The principle here is simple. Individual creators shouldn't be making branding decisions on the fly. Branding should be defined once by admins or designated owners, then reused everywhere.

That said, this lesson focuses on the places where flexibility makes sense at the demo level.

Demo-Level Branding

While workspace branding covers most needs, there are scenarios where demo-level branding is useful. One common example is multi-brand organizations operating within a single workspace. If multiple child brands need to coexist and separate workspaces aren't available, demo-level branding can help accommodate different identities. This requires discipline to manage, but it provides practical flexibility when needed.

Demo-Level Settings

Beyond branding, demo-level settings also play a big role in how demos are experienced.

Autoplay is one of the most commonly used demo-level settings, especially for marketing. When autoplay is enabled, a demo behaves more like a video. It plays automatically and works well for homepage embeds, landing pages, or hero sections where viewers expect passive consumption first.

Sound and Music

Sound is another setting that affects how demos feel.

Background music can add polish when used thoughtfully. It helps demos feel more dynamic and less like static walkthroughs. Teams can choose from built-in tracks or upload custom audio, usually keeping volume low so music supports the experience without distracting from it. Campaign- or season-specific music can be effective when it's subtle and on-brand.

Comments and Collaboration

Demo-level settings also shape collaboration.

Comment controls determine how teams and viewers interact with demos. Internal comments allow teammates to review and refine demos before sharing them externally. External comments allow viewers to leave feedback directly on a demo, even without a Supademo account.

This is especially valuable for real-time product feedback, customer insights, and sales discovery. Comments can be replied to, resolved, or deleted, and notifications ensure feedback doesn't get lost. This creates a lightweight loop that keeps demos aligned with real user needs.

Accessibility

Accessibility is another important part of professionalism.

Closed captions are enabled by default when voiceovers are present, and they should generally stay on. Captions support viewers in noisy or silent environments and improve accessibility across devices and contexts. This matters for demos used on websites, shared publicly, or shown at events.

SEO and Discoverability

Finally, demo-level settings extend into discoverability.

Supademo supports SEO configuration at the demo level. Titles and meta descriptions are generated automatically, but they can be customized when needed. Creators can upload custom social sharing images, control whether step descriptions appear on the share page, and decide whether demos should be indexed by search engines.

When step descriptions are exposed, demos can also function as structured, searchable documentation without creating separate content.

Summary of Best Practices

To summarize a few best practices for demo-level branding and settings:

• Define branding standards at the workspace level whenever possible
• Use demo-level overrides intentionally, not casually
• Enable autoplay and music only when they support the context
• Keep comments and captions enabled to support collaboration and accessibility
• Use SEO settings to improve clarity and discoverability

What's Next

This wraps up the course on editing and personalization.

You now know how to structure demos, update them over time, personalize them with variables and voice, localize them with translations, and control how they look, sound, and behave at the demo level.

Next, we'll move into the course on sharing. That's where we'll cover how to distribute demos as links or embeds, how to share one demo versus many, and how to choose the right sharing method depending on your audience and goals.