How to Brand a Salesforce Experience Cloud Login Page When Passwordless Login Is On

Turn on passwordless login for an Experience Cloud site and the login page’s Logo, Background, and Footer fields disappear from Setup. You’re left with the stock Salesforce cloud logo, a grey background, and a ”© Salesforce, Inc.” footer. It looks locked. It isn’t. A NetworkBranding metadata deploy sets all three.

Why the fields disappear

Passwordless login runs on a Login Discovery Page, which is hosted by Salesforce, not Experience Builder. There are no components on it to edit. On an Enhanced LWR site, setting Login Page Type to Login Discovery Page hides the Logo, Background, and Footer fields in Login & Registration, and the classic Login Settings link just redirects to that same hidden page.

Don’t switch to an Experience Builder Page

The obvious move is to flip Login Page Type to Experience Builder Page, where the branding fields exist. That removes the Login Discovery Handler and breaks passwordless. Don’t do it.

The fix: NetworkBranding metadata

The hidden fields are writable through the NetworkBranding metadata type. Deploy them and the login page picks them up. The component name is cb plus your network name (ours is cbHipTen_Portal). The fields:

• staticLogoImageUrl: your logo (see below)
• loginQuaternaryColor: page background. We set #FFFFFF to kill the grey
• loginFooterText: footer text, e.g. your company name
• loginPrimaryColor: login button colour

The logo is a per-org public URL

staticLogoImageUrl needs a public image. Use a Salesforce Document with IsPublic = true, served from the ImageServer:

https://<site-domain>/servlet/servlet.ImageServer?id=<15-char-Document-Id>&oid=<15-char-Org-Id>

This URL isn’t portable. It embeds the site domain, Document Id, and Org Id, all of which differ per org, so you upload the image and rebuild the URL in dev, test, and production separately. Use a high-resolution transparent PNG, and confirm the URL returns HTTP 200 before wiring it in.

Deploy and publish

sf project deploy start -m "NetworkBranding:<yourNetwork>" --target-org <alias>
sf community publish --name "<Your Site>" --target-org <alias>

The login page sits behind a CDN that caches hard, so a normal refresh shows the old page. Check in a private window and give it a few minutes before deciding the deploy failed.

What you still can’t change

The “employees, log in here” link stays. The internal-login checkbox doesn’t remove it, it isn’t a NetworkBranding or CustomSite field, and the page is Salesforce-hosted so there’s no CSS hook. Dropping it means leaving the Login Discovery page, which breaks passwordless. Everything else (logo, background, footer) is yours.

Stuck on a “the platform won’t let us” problem in Salesforce? Talk to HipTen.