Skip to main content
Version: Next (nightly)

Workspace branding

When people other than you use a workspace, it can wear your name instead of Cobblr's. Branding lives in a few places depending on who's looking, and most of it is set under the portal config.

The member portal​

Members don't land in the admin interface. They sign in to a portal, which is where branding matters most, and you set it under the portal config:

  • Display name: what the portal is called, shown to members in place of the raw workspace name.
  • Logo: an image you upload, stored inline so a self-hosted install needs no outside file host.
  • Theme: force light, force dark, or auto for the portal itself.
  • Colors, font, and corners: a set of look-and-feel tokens (background, cards, text, accent, borders, plus a font and corner rounding). You set tokens, not raw CSS, and anything left unset falls back to the Cobblr default.

The result is a member-facing surface that reads as your club, shop, or library rather than a generic tool.

Per-app themes​

A custom app can carry its own theme, set with the same look-and-feel tokens. So a lending app and a check-in app in the same workspace can each look distinct, and a member's whole experience can be one branded screen.

The admin interface​

The full interface you work in has its own theme setting too, separate from the portal's, so managers can run a comfortable working theme while members see the branded one. Where an admin sits on light versus dark also follows the theme resolution.

What branding does not touch​

Branding is skin. It doesn't change what a member can do or see. That's governed by their role and grants. A branded portal with the wrong permissions still shows the wrong things, so set both.