Everything is configured through a single object passed to `init()`:

```js
lightning("init", {
  theme: "light",
  position: "bottom",
  // …every other option is optional
});
```

If you are not sure which options your site needs, start with the [Lightning
configurator](https://demo.lightning-consent.io/). It helps you choose the right
tag-loading path before you tune appearance or regulation.

## What you set vs. what's supplied

- **`siteId`** is the only strictly required field — and the **license key
  usually supplies it**, so you rarely set it by hand.
- **Regulation** is [resolved at the edge](/how-it-works/#regulation-is-resolved-at-the-edge)
  from the visitor's region unless you force it with `geo`.
- Everything else has a sensible default (light theme, bottom banner, all
  categories, Consent Mode on, GPC honoured, floating button on).

## Central config merges over inline

You can manage settings **centrally per-site in the dashboard**. Dashboard config
is **merged over** your `init()` object, so you can change copy, theming or
categories without redeploying the page.

## Where to go next

- [Appearance & theming](/configure/appearance/)
- [Copy & locales](/configure/copy-and-locales/)
- [Categories & regulations](/configure/regulations/)
- [Google Consent Mode v2](/configure/consent-mode/)
- The complete field-by-field table lives in the
  [Config reference](/api/config-reference/).

:::note[More detail coming]
Being migrated from `docs/INSTALL.md` § _“Configuration reference.”_
:::