The signer app gets the sender's brand, not Kamo's

FixESigService
Shipped
August 26, 2026 at 7:26 PM UTC
Author
Kamo
Commit
e9faf11

Two separate ways the same wrong assumption showed up. The signing page's logo URL was https://<org fqdn>/theme/logo-full.<ext>, which is not a path anything serves — the theme host answers 308 — so a branded envelope fell back to plain text on every document. It is the theme bucket now, the same one every other surface reads. The watermark stamped onto signed documents derived its folder from the org's FQDN. An org that has brought no domain has none, so those orgs got no watermark at all, silently, on every document they had ever signed. Both take the org's ALIAS — mandatory, unlike a domain — through OrgThemeAssets. OrgBranding carries it to the signer app, which was threading orgFqdn into its own copy of the folder derivation for the same reason and with the same result.

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