Skip to content

docs(frontend): tenant self-service branding in the dashboard#234

Open
marcelo-maciel wants to merge 1 commit into
fullstackhero:mainfrom
marcelo-maciel:docs/dashboard-tenant-branding
Open

docs(frontend): tenant self-service branding in the dashboard#234
marcelo-maciel wants to merge 1 commit into
fullstackhero:mainfrom
marcelo-maciel:docs/dashboard-tenant-branding

Conversation

@marcelo-maciel

Copy link
Copy Markdown
Contributor

Companion docs for kit PR #1329 — the dashboard Settings → Branding tab that lets a tenant admin edit their own tenant's TenantTheme.

The Multitenancy module already exposed current-tenant theme endpoints gated on Tenants.ViewTheme (basic) + Tenants.UpdateTheme (tenant-assignable, not root-only), but the only UI lived in the admin console. #1329 adds a permission-gated, current-tenant-scoped editor in the dashboard.

  • frontend/dashboard — settings tab list + the per-tenant branding paragraph now describe the dashboard editor alongside the admin one.
  • frontend/theming — the "two layers" intro now names both editors (admin + dashboard) writing TenantTheme, and clarifies that per-tenant rendering of app chrome is still opt-in (the Branding tab edits the stored theme without consuming it for its own paint).
  • changelog — 2026-07-04 entry.

Prose + table edits only; no code fences changed.

Document the dashboard Settings > Branding tab (kit PR #1329): a tenant admin
can now edit their own tenant's TenantTheme (palettes + brand assets) from the
dashboard, gated on Tenants.UpdateTheme and current-tenant-scoped, alongside the
existing operator editor in the admin console.

- frontend/dashboard: settings list + per-tenant branding paragraph.
- frontend/theming: two editors (admin + dashboard) now write TenantTheme;
  clarify that per-tenant *rendering* of app chrome is still opt-in.
- changelog: 2026-07-04 entry.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant