Skip to content

rebranding - organization branding customization #35

@edospadoni

Description

@edospadoni

Overview

Implement Rebranding feature allowing organizations to customize branding assets for supported products. Owner can enable/disable rebranding per organization, with automatic hierarchy inheritance (distributor → reseller → customer).

Requirements

Core Features

  • Enable/disable rebranding per organization (Owner only)
  • Upload branding assets per product (logos, favicon, background, product name)
  • Hierarchy inheritance: child organizations inherit parent's rebranding
  • Systems fetch rebranding config via authenticated API

Assets per Product

  • Logo light/dark (rectangular and square variants)
  • Favicon
  • Background image
  • Custom product name

Supported Products

  • nethvoice (application)
  • webtop (application)
  • ns8 (system)
  • nsec (system)

Backend APIs Available

All necessary REST APIs are implemented:

Backend (JWT auth):

  • GET /api/rebranding/products - list rebrandable products
  • PATCH /api/rebranding/:org_id/enable|disable - toggle rebranding
  • GET /api/rebranding/:org_id/status - get org rebranding status
  • GET /api/rebranding/:org_id/products - get org products with assets
  • PUT /api/rebranding/:org_id/products/:product_id - upload assets (multipart)
  • DELETE /api/rebranding/:org_id/products/:product_id - delete product assets
  • GET|DELETE /api/rebranding/:org_id/products/:product_id/:asset - single asset

Collect (Basic auth for systems):

  • GET /api/systems/rebranding - get rebranding config (grouped by type)
  • GET /api/systems/rebranding/:product_id/:asset - get asset binary

Design mockup: #36

Sub-issues

Metadata

Metadata

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions