Brand your portal

Your portal doesn’t have to look generic. From Settings in the dashboard you can set your accent color and theme, upload a logo, link your real site, choose whether visitors see view counts, and drop in a tracking or chat script, no code, no deploy. The Display and Advanced tabs of Settings are visible to the forum owner and admins; see Sign in to your dashboard for what every role can reach.

There’s no Save button on the Display tab: settings auto-save as you edit. Type a new name or paste a hex color and it saves a moment after you stop typing; the theme and view-count buttons save the instant you click them. A small “Saving” then “Saved” note next to the tabs confirms each change, and if a save fails, an error notice tells you why (what you typed stays in the field, so you can fix it and carry on). The one exception is custom scripts, which only save through an explicit Validate and save button, see below.

A View your portal link sits at the top of Settings. It opens your portal in a new tab with a fresh copy, so you see your latest changes right away instead of a cached version.

Accent color and theme

Two settings drive your portal’s look:

Accent color: buttons, links, and highlighted elements (like the “Ask a question” button and vote controls). Pick it with the color picker or type a hex value directly (#rrggbb or the shorthand #rgb).
Theme: Light, Dim, or Dark, a fixed set of palettes for the rest of your portal (page background, cards, text, borders). Your accent color applies in every theme.

Changes apply across your whole portal within a minute.

Visitors aren’t stuck with your choice either: a theme switcher in the portal navbar lets each visitor pick Light, Dim, or Dark for themselves. That choice is saved in their own browser and only changes how the portal looks to them, not to other visitors, and it doesn’t touch your Settings.

Logo

Upload a logo from the Display tab of Settings: PNG, JPEG, or WEBP, up to 2 MB. It becomes your portal navbar’s brand: with a logo set, the navbar shows only the logo, replacing both the default initial badge and the forum name text, so a wordmark isn’t doubled up by the same name printed next to it.

A wide, rectangular wordmark works best. The preview boxes and the navbar all show your logo uncropped, so a wordmark keeps its shape instead of being cut down to a square.

Your portal has three theme modes (Light, Dim, Dark, see above), and you can upload a separate logo for each:

Light is your primary logo, the one every other mode falls back to. It’s the only one you have to set.
Dim and Dark are optional overrides for visitors in those modes. Leave either one unset and it inherits: Dim falls back to your Dark logo if you’ve set one, otherwise to Light, and Dark falls back to Dim before Light, the same dark-leaning preference in both directions. In other words, upload one dark-mode logo and both Dim and Dark visitors get it.

Each mode has its own card in Settings, previewed against that mode’s real portal colors so you can see exactly what a visitor in Light, Dim, or Dark will get. A card showing an inherited logo (rather than one you uploaded yourself) renders it at reduced opacity with a small label naming where it’s coming from. The swap between modes is instant and works with the visitor theme switcher too, there’s no flash or reload.

Leave every mode unset and your portal falls back to a simple initial badge in your accent color. A Remove button next to each card’s upload button clears that mode’s own logo: on the Dim/Dark cards it reverts that mode to inheriting again, the chip comes back. Removing the Light logo while Dim or Dark variants still exist reverts Light-mode visitors to the initial badge and forum name (Light never borrows a dark-mode logo, it would usually look wrong on a white header); Dim and Dark visitors keep their own variants. In general, any mode that ends up with no logo at all shows the initial badge and name for exactly that mode.

Favicon

Upload a favicon from the Display tab of Settings, right below the logo: a square PNG, JPEG, or WEBP, up to 2 MB (SVG isn’t supported). It’s the small icon that shows in the browser tab, separate from the logo in the navbar.

Leave it unset and visitors see the default favicon until you set your own. Once you upload one it replaces the default everywhere on your portal, and the same Remove button clears it back to that default.

Your favicon also identifies the forum in your dashboard’s forum list, so if you staff several forums, each card shows its own icon (or an initial badge in the forum’s accent color until a favicon is set).

Website URL

Add your real site’s URL in the Website URL field and a small link to it appears on the right side of the portal navbar, just the bare hostname (for example acme.com) with a small external-link icon, pointing wherever you’ve set. Leave it blank and no link shows at all.

View counts

Every question tracks how many times it’s been viewed, and that tracking never stops. The Show view counts toggle on the Display tab only controls whether the number itself is displayed to portal visitors, like the “123 views” line on a question page.

The public API and MCP server honor the toggle too: with it off, portal question responses return no view counts (the field is null). Sorting is not affected. The “Most viewed” option on the portal and the views sort in the API keep working either way, they just don’t reveal the numbers behind the order.

It’s on by default. Turn it off if you’d rather not surface view counts to customers, for example if a low count on a niche question might look like a sign nobody’s looking at it.

Your own staff aren’t affected: the moderation queue always shows view counts to owners, admins, and agents, regardless of this setting, since it’s an internal tool, not something a visitor sees.

Custom scripts

The Custom scripts field accepts any script or embed snippet: Google Analytics, a support chat widget, a heatmap tool, whatever you need. Paste it in and click Validate and save.

Unlike the rest of Settings, this field never auto-saves: scripts run on every page of your portal, so nothing changes until you explicitly click Validate and save. While you have unsaved edits, a Discard changes button next to it puts the field back to the last saved version.

Content must be <script> tags: an external embed (a src attribute), inline JavaScript, or both, one after another. HTML comments between tags are fine too. Anything else, plain text or any other HTML tag, is rejected.

A few things worth knowing:

This only runs on your public portal: the pages your customers see. It never runs on your team dashboard. That’s a deliberate boundary: your dashboard is where billing and forum configuration live, and a script pasted here has no way to reach or interfere with those pages, even for an owner or admin account.
Custom scripts are a plan-level capability. If the field is disabled, your current plan doesn’t include it, see Plans & limits.
Snippets are validated when you save. The JavaScript inside each inline <script> tag is syntax-checked, so a typo can’t take down every page of your portal. If something’s off, the exact error appears under the field and nothing is saved until it’s fixed.
There’s no sandboxing or review of what you paste beyond that syntax check. Treat this like adding a script tag to any site you control, and only add snippets from sources you trust.

The “Powered by” badge

Every portal, on every plan, shows a small “Powered by” badge; it isn’t something you can turn off. Where it appears depends on your plan:

Basic: a small floating badge in the bottom-left corner of the screen, so it’s visible without getting in the way of anything you’ve added to the bottom-right (like a chat widget).
Pro: it sits quietly at the bottom of the page, in the footer, alongside your other footer content.

Where this lives

All of the above is configured on the Display and Advanced tabs of Settings in your dashboard (/w/{your-forum}/settings), owner and admins. The Badges tab of Settings is the same owner-and-admin surface, see Staff profiles & badges.