# Prompt.screen.text custom text variables resolve empty inside Universal Login partials

**URL:** <https://community.auth0.com/t/prompt-screen-text-custom-text-variables-resolve-empty-inside-universal-login-partials/203401>\
**Category:** Get Help\
**Tags:** login, auth0\
**Created:** [September 16, 2026, 11:10am UTC](https://community.auth0.com/t/prompt-screen-text-custom-text-variables-resolve-empty-inside-universal-login-partials/203401 "2026-09-16T11:10:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sclark1](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/sclark1/32/72768_2.png) [@sclark1](https://community.auth0.com/u/sclark1)\
**Post date:** [September 16, 2026, 11:10am UTC](https://community.auth0.com/t/prompt-screen-text-custom-text-variables-resolve-empty-inside-universal-login-partials/203401/1 "2026-09-16T11:10:50Z")

</div>

## Problem

The Support email is down right now, so I can’t open a ticket for our customer. I’m trying to render a small localized string inside a Universal Login partial using the documented custom-text variable mechanism, and it’s coming up empty. I’ve verified all the usual suspects and want to check whether this is a known behavior or limitation before I spin further.

## What I’m trying to do

Per the docs, define a custom text variable with the Management API for a given screen, then reference it in a partial as `{{ prompt.screen.text.varX }}` and have it render on that screen.

I defined `var-broker-login` (a neutral example rather than our real one, which is an alternate sign-in link):

```auto

```

```auto
PUT /api/v2/prompts/{screen}/custom-text/en
{ "screen": { "var-broker-login": "Use a different sign-in option" } }

```

And referenced it in the screen’s `secondary-actions-start` partial:

```auto

```

```auto
{{ prompt.screen.text.varBrokerLogin }}

```

What I’ve verified

- Storage is correct. `GET /prompts/{screen}/custom-text/{en,nl}` reads back the exact object, keyed under the screen name.
- The body key must be the screen name. If I use the prompt-family name as the body key instead, the API rejects it with `"Invalid screen \"<family>\""`.
- Partials DO inject. Static HTML/CSS in the same partial renders fine (e.g. CSS that hides a button works).
- Other template variables work. A test partial containing `{{ locale }}` rendered `en`.
- Rendering mode is `standard`. I deliberately avoided `advanced`/ACUL, which I understand disables partials.

The actual problem

Every `prompt.screen.text.*` reference renders empty when the screen is served over the custom domain. I tried all accessor forms in the same partial:

```auto

```

```auto
{{ prompt.screen.text.varBrokerLogin }}
{{ prompts.screen.text.varBrokerLogin }}
{{ prompt.screen.text['varBrokerLogin'] }}
{{ prompt.screen.text['var-broker-login'] }}

```

All come back blank. I also tried a built-in text key the same way and it also rendered empty, which suggests the entire `prompt.screen.text` object is not being injected into the partial render context, not just my custom variable.

My tenant setup

- `universal_login_experience: new`
- `identifier_first: true` (so the identifier-first screen is the one being rendered)
- Tenant `sandbox_version`: `22`
- Custom page template configured and applying correctly (both `auth0:head` and `auth0:widget` present; custom header/footer render)
- Custom domain is `ready`, TLS provisioned, marked default
- Rendered via an `/authorize` flow on the custom domain (a raw `*.auth0.com` host doesn’t apply partials, which I understand is by design)

Workaround I’m using for now

Since `locale` is available in the partial, I replaced the custom-text reference with a Liquid conditional:

```auto

```

```auto
{% if locale == "nl" %}...{% else %}...{% endif %}

```

That renders correctly, which confirms the partial and template context are healthy, and isolates the failure specifically to the custom-text bridge.

---

<div class="post-metadata">

**Author:** ![sclark1](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/sclark1/32/72768_2.png) [@sclark1](https://community.auth0.com/u/sclark1)\
**Post date:** [September 16, 2026, 11:36am UTC](https://community.auth0.com/t/prompt-screen-text-custom-text-variables-resolve-empty-inside-universal-login-partials/203401/2 "2026-09-16T11:36:59Z")

</div>

nevermind:  
it’s not `prompts.screen.text`, it’s `prompts.screen.texts`

---

<div class="post-metadata">

**Author:** ![sclark1](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/sclark1/32/72768_2.png) [@sclark1](https://community.auth0.com/u/sclark1)\
**Post date:** [September 16, 2026, 11:48am UTC](https://community.auth0.com/t/prompt-screen-text-custom-text-variables-resolve-empty-inside-universal-login-partials/203401/3 "2026-09-16T11:48:56Z")

</div>

Please update the documentation on this page to reflect this:

> **[Customize Universal Login Text Elements - Auth0 Docs](https://auth0.com/docs/customize/login-pages/universal-login/customize-text-elements)**
>
> Learn how to customize Universal Login text elements using the Auth0 Dashboard or Management API

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [September 18, 2026, 11:49am UTC](https://community.auth0.com/t/prompt-screen-text-custom-text-variables-resolve-empty-inside-universal-login-partials/203401/4 "2026-09-18T11:49:02Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
