One row per settings area, in the panel's own order. "Who" names the lowest role that can change shared settings. Owners and administrators manage those settings within their permissions. Initiating an ownership transfer and reading the audit log require the owner. A viewer reads permitted configuration for assigned sites but cannot change it. Every person can manage their own profile and notification preferences. Read-only areas explain the restriction and disable unavailable changes. Areas marked per site apply to the currently selected site. The rest belong to the account or person named in the table.

This site

Area	Who	What it holds
Site	admin	Name, domain, other addresses, time zone, the primary revenue currency, retention, and blocked query parameters. The name defaults to the domain, written the way you typed it even when an international name is stored in punycode. The currency only chooses which one commerce reports open on: recorded currencies always stay separate, and Kehai never converts or adds them. Retention is one of ten spans, and lowering it deletes what falls outside the new window, which the screen says before you do. Blocked query parameters are the names your pages carry that must never reach storage, from an editable list initialized with credential names. The installation tag carries no list of its own: intake applies the site's configured list to every arriving event, with no extra fixed exclusions. Updates apply to the next event that arrives; nothing needs refreshing. No repasting is needed. Intake also applies the current site list before storage.
Install	admin	Your snippet with your id and dropped parameters on it, the pixel, event examples, and the live wiring check. The guide
Integrations	admin	One active commerce source per site, connection setup, delivery status, and disconnect. WordPress tracking can also be installed without commerce. The guide
Modules	admin	Which report families exist for this site, and the plan each needs. The table
Goals	admin	Outcomes with names: event, page, and order goals, plus pacing targets. The guide
Rules	admin	Block at intake or exclude at read. The two are different in a way worth thirty seconds: block and exclude
Alerts	admin	Watches on one number over one slice of the site that say something when a day breaks its own pattern. Anybody with the site can switch their own mail for an alert on or off. How an alert decides

Access

Area	Who	What it holds
People	admin	Invitations and roles: owner, admin, viewer, and which sites a viewer sees. A pending invitation can be sent again from here. The owner can offer administrative ownership to an active administrator; both sign in again and the recipient accepts within 24 hours. This leaves the legal purchaser and subscription unchanged. Bring your team
API keys	admin	Keys with read, commerce, or full scope, shown once, plus ready requests with your site filled in. The guide
Assistants	every role reads it	The door for an assistant: the endpoint, the configuration for Claude Code, Claude, Cursor, and VS Code, a check that a pasted key really answers, and the tool list your modules expose. The guide

Data

Area	Who	What it holds
Imports	admin	Daily history from GA4, Plausible, or Umami, with old conversions mapped onto goals. The guide. A Kehai archive is imported under Your data instead
Search Console	admin	The Google account and the Search Console property whose queries appear on the Referrers screen, pulled once a day. Its own Google consent, for Search Console alone, and never tied to an import. Search terms
Your data	admin	Site settings and retained analytics datasets in one NDJSON file, plus import into an existing site. Archive import restores supported configuration and raw data, reports skipped records, and can leave partial changes if interrupted. Exports lists what the file contains. Export is available on every plan
Audit	owner only	Administrative changes: who did it, when, which area, and which fields changed. Profile presentation preferences, such as accent color, are outside this log. Values are never stored, only field names. Entries are chained and the database refuses to rewrite or delete one. Copy or download it as CSV

Account

Area	Who	What it holds
Notifications	each person	Your own weekly or monthly digest per site, and the full history behind the bell: alerts, digests, billing and service messages, filtered, read one by one, deleted for you alone. The bell and the inbox
Billing	admin	The plan, the visit band, the history add-on, and Stripe's own portal for the card, invoices, cancellation, and plan changes. Card numbers never touch Kehai. The guide
Profile	each person	Your name, your accent color, email with a verified change flow, password, the second factor with backup codes, passkeys, and every open session of yours, revocable one by one
Sites	admin	Every site on the account, where a new one is made, and the only place a deleted site still shows: under Deleted, with the day it is erased and a Restore button that works for 30 days. More sites, and a deleted one

Danger zone

The one area drawn in red holds the two writes on a site that ask you to type its domain first, and they are different things:

Erase what this site has measured empties the analytics and keeps the site: the snippet, the settings, the goals, the rules, the alerts, and the people all stay, and counting continues from the next visit. There is no grace period and nothing to bring back. For a site that measured a staging period or a test you want gone whole.
Delete the site takes it out of the panel and stops counting at once. Nothing is erased for 30 days, and until then it can be restored from Sites. After that the events, orders, and imported history go for good.

Exporting your data first lives one area up, which is not a coincidence.

What you will not find in Settings

Currency conversion. There is none anywhere: money is reported in the currency it was earned in, always separate. The site's primary currency only picks the tab commerce reports open on.
A way to edit collected data. Rules can exclude it from reports, retention and deletion can remove it, and the export can hand it to you, but no screen rewrites what was measured.
Channel rule overrides. Classification lives in code and is the same for every site, which is what makes two sites comparable. The rules