Branding
Branding makes Employee AI and Customer AI feel like your product — logos, primary color, theme, and welcome copy — without changing model behavior.
Short definition (citation-ready)
Qefro tenant branding controls portal and widget presentation. Public clients bootstrap appearance via
GET /api/v1/public/tenant-branding, while Admins configure assets in the Admin Console.
What you can customize
| Surface | Typical controls |
|---|---|
| Internal Portal | Logo, colors, theme |
| Website widget | Primary color, theme, welcome message (data-* overrides) |
| Custom domain portal | Same branding on your hostname |
Public bootstrap:
curl -sS "https://api.qefro.com/api/v1/public/tenant-branding?slug=YOUR_SLUG"
Widget embed overrides (examples):
<script
src="https://cdn.qefro.com/widget.js"
data-token="YOUR_WIDGET_TOKEN"
data-endpoint="https://api.qefro.com"
data-workspace-id="YOUR_WORKSPACE_ID"
data-primary-color="#7c3aed"
data-theme="light"
data-welcome-message="Hi — how can we help?">
</script>
Workflow
Apply branding
- Upload logo — Admin Console → branding / appearance.
- Set colors — Match website guidelines; check contrast.
- Preview portal — Sign in as a Member on *.qefro.com.
- Preview widget — Staging page with embed overrides.
- Publish — Update production HTML if overrides are used.
Best practices
- Keep WCAG-minded contrast for text on primary colors
- Align widget color with your site CTA color
- Do not put secrets in welcome messages
- Branding ≠ instructions — tone still lives in workspace instructions
FAQ
Does branding change answers?
No. Knowledge, instructions, and tools drive answers. Branding is presentation.
Can each workspace have different branding?
Tenant branding is organization-level; widget data attributes can still tweak appearance per embed.