Skip to main content

Add custom portal code safely

Review, publish, and test trusted client-facing scripts without disrupting portal access.

Written by Geoff Mina

Add trusted client-facing scripts only when a standard portal feature cannot meet the need, and test the complete sign-in experience after every change.

Before you add code

  • Only workspace owners and implementers can change this setting.

  • The code runs for signed-in clients on every portal page.

  • Third-party scripts may receive client-facing data, so use only providers you trust.

  • Keep a copy of the last working snippet before replacing it.

Moxie Advanced client portal settings with a custom-code editor and safety checklist

The warning and review step are intentional because a broken script can affect the entire portal.

Publish custom code safely

  1. Paste or edit the trusted snippet under JavaScript embed code.

  2. Select Review and save.

  3. Read the confirmation carefully and acknowledge the risk.

  4. Open the live portal in a separate browser session.

  5. Test sign-in, navigation, custom pages, forms, and mobile layouts.

If the portal stops working

Return to Advanced settings, remove or restore the most recent snippet, save again, and repeat the live-portal checks. Avoid scripts that replace Moxie navigation, authentication, or core page content.


Continue exploring Client portal

Did this answer your question?