KNOWLEDGE FOR TEAMS

Implement with clear ownership

Use the technical tutorials as a controlled implementation path for administrators, moderators and support teams.

IntegrationsFree plan

Web Widgets

From explicit field selection to a tested embed: keep customer-facing information current from one governed publication center.

◷ 11 MIN READ✓ 5 stepsReviewed: 10 October 2026
START GUIDE ↓
01
THE MODULE

What does Web Widgets?

Publish controlled service, roadmap, event, and support widgets on approved business websites without exposing internal workspace or member data.. This guide covers readiness, configuration, validation, launch, and ongoing ownership.

SERVER-SPECIFIEKPlan, settings, permissions, and AI Credits always belong to the selected server.
02
OUTCOMES

What you will achieve

01

Only deliberately selected fields become public

02

Every publication is responsive, accessible, and restricted to approved domains

03

Pausing or withdrawing a publication makes the public widget unavailable immediately

03
READINESS

Before you start

✓HubNova is online on the selected Discord server
✓You can manage the selected server workspace
✓You control an HTTPS website where an iframe or the HubNova loader can be installed
04
LEAST PRIVILEGE

Access & permissions

⌁

Dashboard: management access to the selected server workspace

⌁

Website: access to install the generated embed code on an approved HTTPS domain

⌁

Discord: no additional permissions for manually entered public content; connected sources retain their own module access

05
PLAYBOOK

Web Widgets setup

Complete the steps in order. Your progress is stored only in this browser.

STEP 1

Choose a widget type

Start with a Community Card, or choose Events, News, Roadmap, Status, Support, Goal, Giveaway, or a combined panel when your plan supports it.

STEP 2

Select public fields explicitly

Approve exactly which title, description, location, count, or status may appear on an external website. Personal member and staff data are always excluded.

STEP 3

Design and inspect the exact preview

Choose language, theme, accent, density, and corners, then review the same renderer used after publication on desktop and mobile.

STEP 4

Restrict publication to your domains

Add complete HTTPS origins only, read the disclosure, and publish after every visible field has been deliberately reviewed.

STEP 5

Install, test, and govern

Use the recommended auto-resize loader or direct iframe, test the live publication, and pause or rotate access when a website should no longer show it.

07
SUPPORT

Troubleshooting

01The widget does not appear on my website+

Confirm that it is published and add the website's exact HTTPS origin. Paths, http addresses, and subdomains are different origins.

02The widget is empty or shows an outdated status+

Open the editor, check the selected public sources, and publish a new snapshot. Expired status checks are deliberately shown as unknown.

03The height does not adjust automatically+

Use the recommended HubNova loader once on the page and verify that your site allows HubNova scripts and iframes.

08
BEST PRACTICES

Best practices

  • Check the selected server before every change.
  • Publish only fields that are meant for completely anonymous visitors.
  • Test desktop, mobile, keyboard navigation, and the unavailable state before launch.
  • Pause first when consent, source data, or domain ownership changes.
09
NEXT UP

Continue learning

Free · Integrations

Ready to implement: Web Widgets?

Open the correct organisation workspace, assign an owner, and complete the runbook.

OPEN WORKSPACE →