Skip to main content
The new Customer Portal is organized as customizable templates for different pages and flows. Each template supports a fixed set of Liquid tags. Firmhouse automatically loads the default templates for your project. During this tech preview, those defaults will continue to improve and receive updates regularly. If you want to customize the portal, you and your developers can find the templates in your Firmhouse project under Customer Portal > Templates.

​
Managing template versions

When you save a template, Firmhouse creates a new saved version. Saved versions do not change what customers see until you publish one. Use the version selector in the template editor to switch between saved versions. You can update a version title to make it easier to recognize later. To check how all current saved versions work together, click Preview latest package. This enables a one-hour browser preview where Customer Portal pages use the latest saved version of every template where one exists. Templates without a saved version keep using the live version. This is useful when changes span multiple pages or shared layout templates. The package preview does not publish anything and only affects the browser where the preview link was opened. A preview banner appears at the bottom of Customer Portal pages when the previewed package differs from the live portal. Use View live portal from that banner, or disable preview from the preview confirmation page, to return that browser to the live portal. To make a saved version live for customers, select it and click Publish. The templates overview shows which version customers currently see. If you use the Customer Portal Agent in chat, it can share a latest package preview link for the current project, rename saved versions, and help publish a template version. The agent only publishes after you explicitly confirm the exact template file and version number to publish.

​
Starting from the Firmhouse default

If you want to use the Firmhouse default template as a starting point without changing the customer portal yet, click Start from default. This creates a new unpublished version based on the current Firmhouse default template. If you want customers to immediately see the Firmhouse default template again, click Reset. Resetting does not delete saved versions; you can still return to an earlier version and publish it later.

​
API options

You can also manage Customer Portal template versions through the GraphQL API. Create a project access token in Settings > Integrations > Access Tokens and choose Customer Portal templates as the access type when the token should only read and write Customer Portal templates.
  • Query selfServiceCenterTemplate or selfServiceCenterTemplates to read a template, including versions, latestVersion, and publishedVersion.
  • Use saveSelfServiceCenterTemplateVersion to create an unpublished version. Pass title when you want the version to have a recognizable name in Firmhouse.
  • Use publishSelfServiceCenterTemplateVersion to publish a saved version for customers.
  • Use resetSelfServiceCenterTemplateToDefault to immediately reset a template to the Firmhouse default.
  • Use updateSelfServiceCenterTemplate only when you want to save and publish a template body in one step. Pass title to name the published version created by the mutation.
For field names, input types, and payloads, see the GraphQL API Reference. This section documents, per page template:
  • Which Liquid tags are supported
  • Which parameters those tags accept
  • The HTML they typically render

​
Page templates

​
Shared reference

​
Notes

  • Tag parameters use Liquid tag attributes, for example: {% add_product size: "small" %}
  • Most parameters are optional and have defaults.
  • Some tags are block tags and must be closed, for example:
{% additions_form_wrapper %}
  ...
{% endadditions_form_wrapper %}