Hi @sadiar
What you’re seeing is a side‑effect of domain separation. When you build a Workspace in the TOP or global domain, the experience, pages and underlying records (for example sys_ux_page, sys_ux_experience and sp_page tables) are stamped with that domain in their sys_domain field. Child domains can inherit some records, such as the landing page, but anything that belongs exclusively to the parent domain will be filtered out when you open the workspace from a lower domain. That’s why only your landing page is visible.
- Domain separation uses the sys_domain field to restrict record visibility. A record created in the TOP domain is not visible in child domains unless it is domain‑unrestricted.
- To make a workspace available everywhere, create it in the global domain so the records are domainless. Alternatively, copy or export the workspace and its pages into each lower domain; each domain maintains its own set of pages.
- Check the pages in sys_ux_page and sys_ux_experience and verify that their sys_domain is set appropriately. Updating the domain to global (or duplicating the record in a child domain) makes those pages visible in the lower domain.
- Be aware that Now Experience UI Builder currently has limited built‑in support for domain separation. Some components do not automatically replicate across domains, so using global domain or per‑domain copies is the recommended practice.
If you decide to run separate copies, consider packaging the workspace and pages into an update set or Application and apply it to the target domain. If you choose to change sys_domain, do it on a non‑production instance first to avoid unintentionally exposing data.
This response was drafted with the help of AI and briefly reviewed by a human. Please excuse any errors or formatting issues.
💥 Was this answer useful? 👉 If so, click 👍 Helpful 👍 or Accept as Solution ✅ 💡🛠️🧠🙌
