docs: replace 'customer' with 'tenant'

[dangrondahl]

Replaces 'customer' with 'tenant' in Cloud Capture docs.

Note: an updated diagram is still pending.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
kosli	🟢 Ready	View Preview	Sep 25, 2026, 3:48 PM

[claude]

Claude finished @dangrondahl's task in 1m 32s —— View job

---

Doc review

• Read the PR diff
• Read changed files at branch HEAD
• Check the rename sweep is complete across the site
• Check cross-file consistency (nav, redirects, links, images)
• Post findings

Two findings. No new, moved, or deleted pages, so config/navigation.json and config/redirects.json need no changes; no links were touched.

---

Critical — the rename sweep is incomplete

administration/cloud_capture/security.md is the page that carries most of this vocabulary, and only its heading changed. Seven occurrences of "customer" remain, including the sentence directly under the renamed heading:

Line	Text	Note
130	"a job for another Kosli customer presents"	mirror of the sentence reworded in overview.md:31
131	"even if that customer gave Kosli your provider"
166	"It differs per customer because more than one Kosli account serves customers"	description of kosli_aws_account_id; users copy this HCL
226	"# job for another customer runs under a different role"	comment in the copyable trust-policy sample
328	"each job runs under a role that is scoped to one customer"	first line under ## How Kosli isolates tenants
331	"A worker running for a different customer"
336	"cannot read any customer's ExternalId"
343	"does not hold any customer data"	contradicts overview.md:32, now "holds no tenant data"

overview.md lines 31–32 summarize the same isolation model that security.md lines 325–343 explain in full, and the two now use different words for the same actor. The reader most likely to notice is a security reviewer following the "See [Cloud Capture Security]" link from the overview straight into the detailed section.

Correctly left alone: "Kosli's Customer Success team" (overview.md:9, security.md:9, getting_started.md:9) — that's a team name, not the multi-tenancy sense.

Fix this →

Question — is "tenant" the right word here, or "organization"?

Worth settling before the sweep is finished, since it decides what the remaining seven lines say.

Kosli's own domain term for the thing being isolated is organization, and these sentences already use it: "scoped to your organization alone, so a worker running for another tenant cannot reach your cloud account" (overview.md:31) switches term mid-sentence for what is arguably the same entity. security.md uses "organization" 11 times.

Elsewhere on the site, "tenant" means deployment topology rather than an account: integrations/mcp_server.md:96 ("your own single-tenant endpoint") and helm/k8s_reporter/configuration.mdx:129 ("a single-tenant Kosli instance"). changelog/index.mdx:500 uses both senses in one line.

If the goal is to avoid "customer" in a security document, "another organization" reuses a term the page has already established and sidesteps the collision. If "tenant" is a deliberate choice for the isolation model specifically, that's reasonable — a one-line definition on first use in security.md would anchor it.

Minor

The overview.md:23 alt text now says "three tenant cloud accounts" while the rendered diagram still says customer. You've already flagged the diagram as pending; noting only because alt text is the whole image for screen-reader users, so the gap is worth closing in the same PR as the new asset.

Also see the inline comment on terraform-reference/resources/action.mdx:5 — a stray mode: "wide" unrelated to this rename.

---

Not checked here: spelling (enforced by vale-spellcheck). I did not run mint broken-links, but no links changed in this PR.
· replace-customer-with-tenant

[claude]

The heading was renamed to "tenants" but the sentence it introduces still says "customer", so the section contradicts its own title on the first line. Six further occurrences remain further down this file (130, 131, 166, 226, 331, 336, 343) — see the top-level comment for the full list.

Suggested change

	one customer:
	one tenant:

[claude]

This looks unrelated to the customer→tenant rename described in the PR body, and action.mdx becomes the only one of the ten pages in terraform-reference/resources/ with a mode field — the other nine (control, custom_attestation_type, environment, flow, logical_environment, policy, policy_attachment, service_account, service_account_api_key) have none, so this page will render at a different width from its siblings.

If it was committed by accident, drop it. If wide mode is wanted for the Terraform reference, it should be applied to all ten in a separate PR.