PlanewardPlaneward Docs
PlanewardPlaneward Docs
Welcome
CRM overviewCustomersContactsFormsAnalytics and public resultsForm appearancePipelinesInvoices and paymentsClient portal

Developers

REST APIAuthenticationWebhooksMCPEmbedded projectsTask description contentDeveloper hub

API

CRM

Form appearance

Theme tokens, Storage logo, and the CSS classes for a custom form.

Open a form, then Settings → Appearance. Three things paint the form, in this order:

  1. Theme fields set CSS variables on .crm-public-form.
  2. The base stylesheet paints layout, type, controls, and interaction states when you have not overridden them.
  3. Custom CSS is injected after that. A rule with the same specificity replaces the base rule.

The same classes are on the public page, the embed, the builder preview, a Contact form block on a site, and the places a community asks the form: checkout forms, /checkout/{code} links, the waitlist, the after-payment form on /join, and the community onboarding (profile) form. Write the CSS once.

On a site block, the base sheet is what visitors see before your CSS. On the public page and embed, the app’s own controls are the starting look, and your CSS still targets the classes below.

Empty rules do nothing. The editor fills them in when Custom CSS is blank, so the class list is already there. Saving that skeleton does not change the form.

At checkout and in the community

In checkout, waitlist, /join and onboarding, the form keeps its layout, questions, paging and Custom CSS, but takes its colours and corners from your community theme, light and dark. Background, Accent and Corner radius apply only on the public page, the embed and site blocks. There is no card: the questions sit straight in the checkout, dialog or onboarding page, sized like the community's own fields.

  • No header. No logo, form name or description. A dialog already shows the form's name and description in its own header.
  • One section per page. A form with several sections shows "Page 1 of 3" with Back and Next. Next checks the page before moving on.
  • Submit button. In a dialog, the submit button sits under the questions in the community's button colour and shows the form's submit button label.
  • Pay and Continue wait for the last page. For a form inside the checkout card, the pay button stays disabled and reads Answer the form to continue until the buyer reaches the last page. In onboarding, Continue stays disabled until the last page.
  • Phone questions show the country code picker, as on the public page.

Changing the Custom CSS of a form used there works by form type: on a checkout or waitlist form attached to a product or plan needs the Manage commerce permission, and on an onboarding form it needs Manage community. An API key or MCP connection with the catalog:write scope can change the CSS of checkout and waitlist forms; an onboarding form's CSS can only be changed with a full-access key. Without the permission, the Custom CSS editor is locked.

Theme fields

FieldWhat to enterWhat it setsWhen it is empty
BackgroundA CSS color: #111827, rgb(17, 24, 39), white--crm-form-background, and the form backgroundSite block stays white. The public page keeps the page background
AccentA CSS color--crm-form-accent. The public page also sets --primary from it, which colors the submit buttonSite block buttons stay near-black (#18181b). The public page keeps its default button color
RadiusA CSS length: 12px, 0.75rem, 0, 1em, 8%--crm-form-radius. The public page also sets --radiusSite block corners stay 16px
LogoAn image from workspace Storage. Upload one or pick an existing file. There is no URL field.crm-form-logoPublic page shows the workspace icon. The site block shows no logo

Unsafe values are ignored: anything with ;, {, }, url(, or javascript: does not become a variable. A length must be a number plus px, rem, em, or %.

The logo is stored as /media/{assetId}, the same path a site image uses. On a site page that path loads directly. On the public page, embed, and builder preview, Planeward turns it into a short-lived Storage URL when the form is rendered. Do not paste that URL into Custom CSS. Target .crm-form-logo instead.

A logo that was saved earlier as a full https:// URL still shows until you replace or clear it.

Images and fonts

Custom CSS cannot load images or font files from other sites. A url(...) is removed unless it is a workspace file (/media/{assetId}) or a Google font file on fonts.gstatic.com.

A Google Fonts stylesheet is kept. Put it in Custom CSS as an @import from https://fonts.googleapis.com:

@import url("https://fonts.googleapis.com/css2?family=Inter:wght@400;600&display=swap");

.crm-public-form {
  font-family: "Inter", sans-serif;
}

Any other @import is removed. The preview on Appearance uses the same rules, so a blocked URL does not show up there either.

Variables

These are set on .crm-public-form. Override the variable to retint the form without restyling every node.

VariableSet byBase sheet uses it for
--crm-form-backgroundBackground, when setSite block background. Fallback #fff
--crm-form-accentAccent, when setSubmit button, focus ring, hovered options. Fallback #18181b
--crm-form-radiusRadius, when setSite block outer corners. Fallback 16px
--crm-form-textBase sheet (#18181b)Site block text and the Back button
--crm-form-mutedBase sheet (#71717a)Description, help, page label, success message
--crm-form-borderBase sheet (#d4d4d8)Control borders
--crm-form-dangerBase sheet (#dc2626)Invalid controls and .crm-form-error
--primaryAccent, on the public page and embedApp submit button and checked checkboxes
--radiusRadius, on the public page and embedApp control corners
.crm-public-form {
  --crm-form-accent: #0f766e;
  --crm-form-radius: 4px;
}

Classes

ClassElementWhen it is in the page
.crm-public-formRoot. A div on the public page and embed, a form on a site blockAlways
.crm-form-logoLogo image on a site block. Workspace mark on the public pageA logo is set, or the public page is showing the workspace icon
.crm-form-brandWorkspace name above the titlePublic page and preview, not the embed or a site block
.crm-form-titleForm name (h1)While the form is waiting for answers
.crm-form-descriptionForm descriptionThe form has a description and has not been submitted
.crm-form-page“Page n of m”More than one page
.crm-form-sectionThe current page’s questionsAlways, while answering. Hidden pages stay in the DOM on a site block with the hidden attribute
.crm-form-section-titlePage title, or a section field’s headingThe page or section has a title
.crm-form-section-descriptionPage or section descriptionThat text is set
.crm-form-fieldOne questionEvery visible question. Also on section headings
.crm-form-labelLabel or legendEvery labeled question
.crm-form-controlinput, textarea, select, or checkboxThe answer control
.crm-form-optionOne radio, checkbox, or yes/no rowradio, multi_select, and boolean
.crm-form-helpHelper text under a questionThe question has helper text
.crm-form-errorValidation messageThe visitor tried to continue with an invalid page
.crm-form-actionsBack / Next / submit rowThe form has questions
.crm-form-backBack buttonPage 2 or later
.crm-form-submitNext and the submit buttonThe form has questions
.crm-form-successThank-you blockAfter a successful submit
.crm-form-success-title“Thank you”After a successful submit
.crm-form-success-messageConfirmation copyAfter a successful submit

Field attributes

.crm-form-field carries:

  • data-field — the question slug, such as email or company_name
  • data-type — string, email, phone, number, textarea, select, radio, multi_select, boolean, section, or hidden

Hidden questions are <input type="hidden"> with data-field and data-type="hidden". They are not wrapped in .crm-form-field.

.crm-form-field[data-field="email"] .crm-form-control {
  text-transform: lowercase;
}

.crm-form-field[data-type="textarea"] .crm-form-control {
  min-height: 8rem;
}

States

The site block’s base sheet already defines these. On the public page and embed, the app controls have their own hover and focus, and the same selectors still match so you can replace them.

SelectorBase sheet
.crm-form-control:hoverBorder shifts to #a1a1aa
.crm-form-control:focus and :focus-visible2px accent outline, 1px offset, accent border
.crm-form-control:disabled60% opacity, not-allowed cursor
.crm-form-control:invalidBorder uses --crm-form-danger
.crm-form-submit:hoverSlightly brighter (brightness(1.08))
.crm-form-submit:focus-visible2px accent outline, 2px offset
.crm-form-submit:disabled60% opacity, not-allowed cursor. The preview disables submit
.crm-form-back:hoverLight gray fill
.crm-form-back:focus-visible2px accent outline, 2px offset
.crm-form-option:hoverLabel color becomes the accent
.crm-form-option:focus-within2px accent outline around the row
.crm-form-option:has(:checked)Row label becomes semibold

Checkbox and radio inputs sit inside .crm-form-option. The base sheet does not give those inputs the full text-field padding.

Replace a state by writing the same selector in Custom CSS:

.crm-form-control:focus-visible {
  outline: 2px solid #0f766e;
  outline-offset: 2px;
}

Example

Teal submit button, a teal focus ring, and one email field called out by its slug:

.crm-public-form {
  --crm-form-accent: #0f766e;
  --crm-form-radius: 12px;
}

.crm-form-submit {
  background: #0f766e;
  border-radius: 999px;
}

.crm-form-submit:hover {
  background: #115e59;
  filter: none;
}

.crm-form-submit:focus-visible {
  outline: 2px solid #0f766e;
  outline-offset: 3px;
}

.crm-form-control:focus-visible {
  outline: 2px solid #0f766e;
  border-color: #0f766e;
}

.crm-form-field[data-field="email"] .crm-form-label {
  color: #0f766e;
}

:hover on a submit button needs filter: none if you set your own background, because the base sheet brightens the button with filter.

Analytics and public results

Charts for every question, and a private link that shares the results.

Pipelines

Boards of opportunities with stages you name. Each stage is Open, Won, or Lost.

On this page

At checkout and in the communityTheme fieldsImages and fontsVariablesClassesField attributesStatesExample