# Module properties, theme tokens, Style Overrides

URL: https://kywi-docs-production.up.railway.app/authoring/module-properties-theme-tokens-style-overrides
Type: docPage

Every module's own props are editable with no developer needed, and Style Overrides adds four free CSS properties per module — theme tokens aren't wired in yet.

Select a module and its properties rail opens on the right — every prop the module declares, as its own control: plain text, a picklist, a longer text area, rich text, a number, a toggle, a color swatch, a date, an image or file picker, or a structured JSON field for the handful of modules that need one. Nothing here needs a developer; a picklist's choices are the only ones fixed in advance, everything else takes whatever you put in it.

## Sections and hints in a long panel

On a module with many fields — several tiles, each with an image, alt text and a caption — the developer can gather fields into sections. Each section is a heading you can open and close, and some may start closed: if a field you expect isn't showing, open the module's sections before assuming it's missing. A line of small text under a field is the developer's hint about what goes in it, such as the format a crop position takes.

## Sections are only as tidy as the module

Sections exist only where the module's developer declared them. A module without them still lists every field in one column, in the order it was built.

## Theme tokens aren't in the rail yet

A theme defines its own closed sets of colors, spacing, typography, corner radius and shadow values, each one addressable by name rather than as free CSS — and a theme can choose to allow custom values on top of its set, category by category. None of that reaches you here, though: the color control on the props rail is a bare native color picker, not a picker of the theme's own swatches, so nothing stops you from typing in a color that doesn't match anything the theme defines. Treat the theme's documented palette as the source of truth and match it by eye until this is wired through.

## Style Overrides: four properties, no developer

Below a module's own props, a collapsed **Style Overrides** section opens onto exactly four free-text fields — padding, margin, background color, and text align — written straight into that module's own inline style. That's the full set; there's no add-a-property option and no reaching any other CSS declaration from here.

## Look for Style Overrides collapsed, not missing

The section starts closed on every module, so if you're expecting to see padding or alignment controls and don't, expand it rather than assuming the module doesn't support them — all four properties are available on every module type.

See [The module palette](/authoring/the-module-palette-47-built-ins-in-seven-categories/) for what's available to add in the first place, and [Themes and design tokens](/developing/themes-and-design-tokens/) for how a theme's own token set is defined.
