docs: add page for setting default organization

[dangrondahl]

Summary

• Adds administration/managing_organizations.md documenting how a user sets their default Kosli organization from the profile settings page.
• Wires the page into config/navigation.json under Administration.
• EU and US instance URLs are presented as a labelled bullet list inside the first Step.

Notes

• Pairs with the "Default organisation on user profile" platform release entry in the changelog.
• Page placement under Administration is provisional; if more account-scoped settings pages appear, a dedicated "Account" top-level category would be a better long-term home.

[mintlify]

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

Project	Status	Preview	Updated (UTC)
kosli	🟢 Ready	View Preview	Jun 3, 2026, 8:07 AM

[claude]

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

---

PR Review: Add page for setting default organization

• Read CLAUDE.md and doc-review skill
• Read changed files
• Check navigation config
• Validate links and conventions
• Post review findings

---

Nice, clean how-to page. The <Steps> component is the right choice, navigation entry is in place, and the writing follows the active-voice style. A few things to flag:

administration/managing_organizations.md

Improvement — Title casing on the page title (line 2): CLAUDE.md requires sentence case for all headings. "Managing Organizations" → "Managing organizations". The same applies to the existing managing_tags.md title, so this is a repo-wide pattern, but worth fixing going forward.

Improvement — Verify the API link (line 24): The link /api-reference/user/set-default-organization targets an auto-generated OpenAPI page. This can't be validated locally — please confirm this endpoint exists in the live OpenAPI spec (https://app.kosli.com/api/v2/openapi.json) or via mint dev, otherwise readers hit a 404. Fix this →

Suggestion — Consider a <Tabs> for EU / US links (lines 14–15): Other pages in the Administration section (e.g., managing_tags.md) use <CodeGroup> or <Tabs> to present EU/US variants. A bullet list works fine here, but tabs would be more consistent with the rest of the site. Low priority.

config/navigation.json

Looks good. The page is added as the first entry under Administration (line 38), which is a reasonable position for an organization-level setting.

Summary

Category	Count
Critical	0
Improvement	2
Suggestion	1

Overall this is a solid, well-scoped addition. The two improvements worth addressing before merge are the title casing and verifying the API link resolves correctly.