Custom portal pages

Customer portal documentation now has a dedicated section. This page remains available for existing links and MCP authoring instructions.

Authoring checklist

1. Read get_portal_configuration and inspect existing pages with list_portal_pages and get_portal_page. The portal must be enabled.
2. Upload supported files with upload_portal_asset. Reference returned literal relative paths in HTML and include all used IDs in save_portal_page.assetIds. MCP does not infer asset references from HTML.
3. Use save_portal_page to save a complete HTML draft at an exact path. The published version stays live. Keep CSS and JavaScript inline.
4. Use preview_portal_page to inspect the saved draft. Its private bearer link lasts 30 minutes; a new preview replaces the previous link.
5. Use publish_portal_page to make the saved draft and asset manifest public together. Publishing, unpublishing and deleting revoke previews.

Built-in home, article and category paths take precedence when Help center is on. Disable Help center to use custom pages at those paths; the master portal switch still needs to be on. HTML is limited to 512 KiB and assets to 2 MiB each. Custom pages run in an opaque-origin sandbox without cookies or local storage; public API fetches must use credentials: "omit". Keep secrets out of public HTML.

For complete guidance, read these pages through read_octocom_docs using the path shown below: