A signing page wears the sender's brand, not Kamo's

Fixkamo-signer-monorepo
Shipped
August 26, 2026 at 7:29 PM UTC
Author
Kamo
Commit
8a1d384

getThemePath took a hostname and used its FQDN with dots turned into dashes as the bucket folder. That could only answer for an org that HAD a hostname, and a domain is optional now — so a sender who had brought none had their envelopes signed under Kamo's logo and colours. The folder is the sender's ALIAS, which the validated token's branding record now carries (OrgBranding.orgAlias). The components threaded orgFqdn into their own copy of the derivation for the same reason and with the same result; they thread the alias instead. The layout's meta loader mounts before any token has been validated, so its first pass has nothing to go on and paints nothing — correct, because the shared signing host names the platform, and no brand for a moment beats the wrong brand. SigningExperience re-applies once the sender is known.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing