Currently, tokens like {{Opportunity.Custom.FieldName}} don't work in Client Portal custom pages. When I try to use a token containing a URL in a custom page (for example, as a link), it treats the token as a literal string rather than parsing it.

Current Behavior:

• Create custom page with HTML: <a href="{{Opportunity.Custom.NotionDashboard}}">Dashboard</a>

• Click the link in the portal

• Browser tries to open: https://clients.domain.com/pages/%7B%7BOpportunity.Custom.NotionDashboard%7D%7D

• Result: Blank page

Expected Behavior:

Tokens should parse in custom page HTML, just like they do in: Email templates, Agreements and so on.

Use Case:

I want to create a custom "Resources" page in the Client Portal that displays client-specific links dynamically. For example, a page that shows:

• Link to their Notion project dashboard

• Link to their Slack channel

• Link to their Google Drive folder

All of these URLs are stored in custom fields and vary per client. Right now, I can use these tokens successfully everywhere else in Moxie except in Client Portal custom pages (or in Client Portal external links!).

Benefits:

Create dynamic, personalised client portal experiences

Eliminate manual configuration of portal content per client

Maintain consistency across all client touchpoints

Save time during client onboarding

Reduce risk of human error (wrong links, typos, etc.)