Manage public company and trust pages
Reviewed by Customer Help Product Support on July 23, 2026. Verified for release 2026.07.
The Public information area is available only to a verified system administrator. It manages the reviewed Customer Help pages at /about, /contact, /privacy, /terms, /security, and /pricing, plus their Spanish versions under /es/.
The product includes factual bilingual defaults. A published custom version replaces the matching default and remains active until it is updated again. This editor is for Customer Help platform information, not a business tenant’s brand or location page.
Customer Help loads the Public information editor only after an authorized system administrator opens this area. A loading status appears while the editor and current published fields are requested. This keeps the editor out of the initial portal download for people who do not use it.
Choose the page
Section titled “Choose the page”Page — Select About, Contact and support, Privacy, Terms, Security, or Plans and pricing. The preview links open the currently published English and Spanish pages in new tabs. Changing the selector does not save unfinished edits.
Use each page for its stated purpose:
- About explains the product and its reviewed-information practice without inventing company history, offices, customer counts, or awards.
- Contact and support points to monitored support paths. Do not publish an email, phone number, or service promise that is not actively supported.
- Privacy describes current product data practices. It must not claim a complete legal policy unless the required legal details have been approved.
- Terms provides an operational overview and must not replace or conflict with an applicable executed agreement.
- Security describes implemented controls. Do not claim certifications, compliance attestations, uptime, data residency, or testing practices without evidence.
- Plans and pricing explains the billing model. Current amounts, availability, quantities, and proration shown in the signed-in portal remain authoritative.
Edit both languages
Section titled “Edit both languages”The English and Spanish fields are saved together so public language alternates do not drift.
Page title — Enter the visible H1, search title basis, and social title, up to 90 characters.
Search description — Write a factual 50–200 character summary for search and social previews.
Eyebrow — Add the short category label above the page title, up to 60 characters.
Page summary — Explain the page’s purpose in 30–320 characters. This appears directly below the title.
Reviewed by — Name the accountable reviewing team or approved reviewer. Do not enter an unverified organization or credential.
Last reviewed — Choose the calendar date when the published claims were actually reviewed. This date appears on the page. Saving also records the real publication time used by the sitemap.
Body (reviewed Markdown) — Use ## or ### headings, paragraphs, bullet lists, **bold text**, and links. Links must be same-site paths, HTTPS URLs, or mailto: addresses. Raw HTML, unsafe protocols, empty content, and oversized content are rejected. The renderer escapes authored text before it creates approved markup.
Publish
Section titled “Publish”Publish both languages — Validate and publish the English and Spanish versions immediately. This is not a draft action. Review legal, privacy, security, pricing, and contact claims before selecting it.
Customer Help records the system administrator, publication time, page, languages, and changed field names in its audit history. It does not copy full page bodies into that event.
Published pages receive a canonical URL, reciprocal English and Spanish hreflang, structured page information, a public Content Signal, Markdown negotiation, and an accurate sitemap lastmod. The homepage and feature-page footer links to these pages and the Help center.
Permissions and visibility
Section titled “Permissions and visibility”- Only a system administrator can open or update the editor.
- The editor and its responses are private,
noindex, and use the restrictive Content Signal. - Saved content is public immediately. Never paste credentials, private conversations, customer data, unpublished sources, or internal incident details.
- If publishing storage is temporarily unavailable, the reviewed defaults remain public but saving is unavailable.
Troubleshooting
Section titled “Troubleshooting”- The Public information area is unavailable: sign in again and confirm the account is a system administrator.
- The editor could not load: select Retry after connectivity is restored. A failed editor download is cleared before the retry, and other system-administration areas remain available.
- The published fields could not load: select Retry in the editor. Customer Help requests the current fields again before enabling editing.
- Publishing failed: the publish button becomes available again. Keep the page open, review the displayed error, and select Publish both languages again after correcting the problem.
- Saving is temporarily unavailable: check Platform readiness and ask the deployment owner to restore publishing storage before trying again.
- A field is rejected: check its displayed length, use a real
YYYY-MM-DDreview date, remove raw HTML, and correct unsafe links. - The page still shows older content: reload the canonical public URL. Its document uses revalidation and its sitemap uses a five-minute cache policy.
- The languages disagree: correct both columns and publish them together; do not use one language as a placeholder for the other.