N
Noah Green
When provisioning a tenant through the Admin API, there is currently no way to
set the tenant's logo or color palette. It has to be done by hand afterwards in
the admin dashboard under Settings > My Interface.
This already works server-side. Uploading a logo in the dashboard posts to
settings.updateTenantBranding with entityId, palette and logoUrl, after
uploading the image through files.uploadS3Image. So this is about exposing
existing behavior on the public API, not building something new.
What would cover it:
  • branding fields on POST /v1/admin/tenants, so a tenant is created fully
configured, or
  • a PATCH endpoint against an existing tenant, e.g.
PATCH /v1/admin/tenants/{tenant_id}/branding taking logo and palette
Either works. The first is better for us because it means provisioning is a
single call.
Context: we are an MSP automating tenant provisioning off an internal form so a
project manager can spin up a client tenant without touching the admin console.
Branding is the one step that still requires someone to go in manually and
remember to do it, which makes it the step that gets missed.