Add organization key concepts and a Configuring Organizations page

[jpshackelford]

• I have read and reviewed the documentation changes to the best of my ability.
• If the change is significant, I have run the documentation site locally and confirmed it renders as expected.

Summary of changes

The Organizations overview never explained what a personal organization, a team organization, the current organization, a super admin, or the default organization is, and it told every reader to "create a new organization from the OpenHands Cloud dashboard", which is not possible on OpenHands Enterprise, where only a super admin can create one. The VM install Admin Console page lists the default-organization and OEM user-creation options in one line each, and no page explains the Helm userProvisioning.enabled value.

This adds a "Key Concepts" section to the overview, with Enterprise-only parts marked, and fixes Getting Started step 2. It also adds a "Configuring Organizations" page, placed after the overview, with the settings for VM installs (Admin Console) and Kubernetes installs (Helm env values), their defaults, what each default-organization setting does, how hiding personal workspaces behaves, what user provisioning registers, and a four-step path for moving an existing installation to organizations without disruption. The admin console page now links to it from the Default OpenHands Organization section and the Enable OEM User Creation Flow row.

Behavior described on the new page was checked against the OpenHands/enterprise server and frontend code and the OpenHands-Cloud Replicated config and Helm chart. mint broken-links reports no broken links. The page has not been viewed rendered yet, so the second checkbox is open until the Mintlify preview has been reviewed.

This PR was drafted by an AI agent on behalf of the user.

[mintlify]

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

Project	Status	Preview	Updated
all-hands-ai	🟢 Ready	View Preview	Oct 15, 2026, 1:46 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

[rajshah4]

Thanks for doing this, i need to work through this in the app to test it all out myself.
Reading through this, i did see we used "personal organizations" and we have "personal workspaces". Not sure if this is the place, but getting that standardized would be nice -- assuming they cover the same concept.

[jpshackelford]

@rajshah4 Thanks, good catch. They are the same concept, so I standardized on personal workspace in edaecd2. The Key Concepts heading is now "Personal Workspaces and Team Organizations", and the body text and the "Default Organization" paragraph use the same term. The Hide Personal Workspaces setting name already matched. A team organization is still called an organization.

I did not change event-automations.mdx, which says "personal org", or the cookbook/ pages, which are generated from OpenHands/enterprise-cookbook. I'll follow up on those separately.

This comment was created by an AI agent (OpenHands) on behalf of jpshackelford.