Brand Kits give your client-facing work a consistent visual identity: your logos, colors, typography, buttons, form fields, and corners. Create the design once, preview it across different experiences, and publish it when you are ready for clients to see it.

Open Brand kits

Brand Kits belong to your workspace, not to an individual team member or client. Your role determines whether you can manage them:

Managing a kit includes creating and editing it, publishing, choosing the default, restoring a published design, and deleting a kit. Because publishing can change several client-facing experiences at once, agree with your team on who should publish shared design changes.

A kit is a reusable set of visual rules. You can have more than one: for example, your main business identity and a separate design for a particular service. Giving two documents the same kit helps them look related without making their content identical.

A kit is not a document template. Invoice and agreement templates still determine the content, layout, sections, and business settings. The kit supplies their visual identity. It does not change prices, taxes, payment terms, agreement wording, form questions, booking availability, or who can access a client portal.

Brand Kits style supported client-facing experiences. They do not reskin the internal Moxie workspace, rewrite existing content, or automatically replace every document’s individually chosen design.

During new-workspace onboarding, choose Professional, Studio, Casual, or Minimal and provide Primary, Secondary, and Accent colors. Moxie generates supporting colors and corner styles, with optional logo upload and a font selector. Leave the font blank to keep the personality’s recommended pairing. The live form and invoice previews show the result before saving. Saving creates and publishes the default kit and creates the matching default invoice template when no invoice templates exist; it does not replace existing templates. You can fine-tune the full kit afterward using the steps below.

The first kit published in a workspace with no default becomes the default automatically. Merely saving an unpublished kit does not make it a live workspace brand. Check the Default label instead of assuming that the first row in the list is the default.

The Default label identifies the workspace-wide choice; other kits remain available for individual uses.

Logos & identity supports a full horizontal logo and a square logo, each with a version for light and dark backgrounds. “Light” and “dark” describe the background the logo needs to work against—not necessarily the color of the logo itself.

Uploads use your workspace image library. A kit provides the artwork, but the document still needs a logo block where you want the logo to appear. Form logo blocks can choose which of the four variants to display.

Use the main palette to establish your identity, then use the more detailed controls only when a particular element needs a different treatment.

Canvas is not the same as a field’s fill or a page’s background. For example, a white form can sit on a navy canvas while its input fields use a pale fill. Embedded forms and schedulers blend into their parent rather than painting a separate full-page canvas. The portal uses its own Page/Surface mapping; changing Canvas is not how you recolor the entire portal.

The contrast indicators help you spot difficult text/background combinations. Always inspect the result too, especially muted text, selected options, and button labels.

Page, Surface, and Canvas serve different jobs; use the preview to see which layer you are changing.

Automatic derives a dark palette from the light palette. Its color chips show the computed result, but hex entry and color picking are disabled while Automatic is selected. This is a good starting point when you do not have separate dark-mode brand guidelines.

Choose Custom to edit the dark palette yourself. Use the Light and Dark preview controls to compare readability and logo visibility. Those preview controls do not publish the kit or force all documents into dark mode; each receiving experience determines which theme it displays.

Set a font, pixel size, and weight independently for H1, H2, H3, and Body. H1 is the strongest heading, H2 divides major sections, H3 supports smaller subheadings, and Body is the everyday reading text.

Use the matching heading or paragraph format in rich-text content so the hierarchy can take effect. If you do not have established brand fonts, keep the starter’s pairing and focus first on readability. You do not need four different fonts; a single heading family with decreasing sizes is often clearer.

Customize text roles provides finer control of labels, help text, answers, and button text. Start with inherited settings, then override only the role that needs to differ. Uploaded fonts are managed separately through Manage uploaded fonts; access to Brand Kits does not independently grant permission to manage uploaded fonts.

Use a deliberate heading hierarchy rather than making every heading the same size.

These settings have separate responsibilities. Changing button corners does not also change the corners of every input or panel.

For a blockier design, reduce each relevant radius—not only Buttons. For a softer design, increase them together while keeping inputs and compact controls practical. A radius of 0 creates square corners.

The Portal preview lets you judge the overall feel without leaving the kit designer.

Your workspace has one default kit. To change it, publish the desired kit, then use Make default from its actions menu in the list or editor. The editor and list both show a Default label.

The default has several specific jobs:

Default does not mean “overwrite everything.” It does not switch existing explicitly branded templates to another kit, assign every existing form or scheduler, or replace the captured branding on existing invoices and finalized agreements. The default Brand Kit is also different from your default invoice template: one chooses visual identity; the other chooses which invoice layout and content start an invoice.

When a portal uses a Brand Kit, manage the kit-owned logo/font settings in Brand Kits rather than the old manual portal controls. The separate favicon section is hidden; the square kit logo supplies the favicon when present. Existing workspaces with no default kit keep their legacy portal appearance.

Select a published kit in the form or scheduler’s design settings. A kit is optional: leaving it unselected retains the native styling controls. On forms, the Advanced custom-CSS tab is hidden while a kit is selected; removing the kit restores the native styling path instead of combining two competing designs.

A direct link uses the selected kit’s Canvas around the form or scheduler. Native forms and schedulers also have their own canvas setting, so they do not need a kit simply to choose that background.

An embedded form follows its parent even if the original form has a different kit. An unbranded parent stays native; it does not silently adopt the child’s kit. Forms embedded in agreements do not show their standalone Submit button—the agreement owns completion.

Open invoice templates and choose the kit in the template’s styling. The Professional, Studio, Casual, and Minimal starters provide different layouts; the kit then supplies your identity.

For example, if an invoice is created using published version 2, publishing version 3 does not restyle that invoice. New invoices use the template’s latest published branding. To deliberately update an existing editable invoice, use Refresh template in the invoice editor. Review the result because refreshing applies the template’s current design, not just a single color.

The online invoice and its PDF use the invoice’s captured branding. PDF dates may use your PDF Locale preference, so a date-format difference is not necessarily a branding problem.

Choose a kit in the agreement’s style settings. Drafts and reusable templates follow the latest publication so you can keep preparing a document with your current identity. Finalizing captures that version for the client-facing agreement, including its embedded forms and schedulers.

Returning an agreement to draft resumes the latest published kit. This is a document-lifecycle action, not a harmless appearance refresh: it can reset client signatures. Review the confirmation and signing consequences before using it. Brand styling does not change a signer’s chosen handwriting font. Agreement PDF generation is not part of this feature.

Save draft saves your work without changing the published design. Publish makes the saved design available; Save & publish saves your current edits and publishes them. A Saved label alone does not mean clients are seeing those edits.

Before publishing, check Forms, Scheduler, Portal, Agreement, and Invoice previews where relevant. Compare light/dark and desktop/mobile. The examples are illustrative: open an actual affected form, scheduler, portal, or document afterward to verify its real content and layout.

Restoration affects live consumers just like a new publication. It does not rewrite branding already captured by invoices or finalized agreements.

Inspect earlier designs before deciding whether to restore and publish one.

If someone else changes the kit while you are editing, reload the saved kit and reconcile the changes rather than overwriting blindly. Duplicate kit is useful when you want a separate design instead of changing everyone who uses the current one.

Use Delete kit from the actions menu. If the kit is the default or has live references, Moxie requires a different published kit to replace it. Review the usage information before continuing: replacement can move forms, schedulers, invoice templates, agreement templates, and agreement drafts to the replacement design.

Existing invoices and finalized agreement snapshots keep their captured branding. The deleted kit goes to the Trash can; restoring it does not automatically move references back from its replacement. Trash access has its own role requirements.

Publish the kit, confirm the resource is using that kit, then reload the live page. If it is an invoice or finalized agreement, its captured version is intentionally stable. If it is embedded, check the parent’s kit instead of the original form or scheduler.

Save and publish the kit first. Only published kits can be selected for live use or made default. If you cannot reach Brand Kits at all, ask the owner to check your role and Settings Access.

Change Fields → Corner radius for inputs. Use Choices for option cards/pills and Portal surfaces for tables and panels. These are intentionally separate settings.

Check Canvas, not Page or field fill. Publish the change and test the direct link. Inside an embed, the parent controls the surrounding presentation.

Check the appropriate light/dark and full/square variant, publish the kit, and confirm which kit the document actually uses. Make sure a document logo block exists. Browser favicons may stay cached after the rest of the page updates.

Automatic mode intentionally disables those controls. Select Custom if you want to edit each dark color yourself.

Continue exploring Moxie essentials

Back to Moxie essentials