Multi-org GA content

[shainaraskas]

REBASE AFTER MERGE OF #5818

Summary

Fixes https://github.com/elastic/docs-content-internal/issues/833
Builds on #5351

Changes

Also made some tag cleanup changes, but those don't impact the display

Admin facing

Page	Description
🆕 Manage multiple organizations	Page created in #5351, unhidden here. Topics include: viewing all of the orgs you have access to creating a new org inviting users to join additional orgs seeing users' org memberships reconciling alternative email addresses
Manage your Cloud organization	Intro page for organization management. Clarified definition of an org to make room for the possibility of multiple orgs Introduced the concept of managing multiple orgs, why you might need multiple orgs, and what resources "belong" to an org Clarified that org management must be done from inside the org
Sign up	This is the top of funnel page for Elastic Cloud. It used to contain both content for signing up and creating an org. Removed the connection between the email address and the org / 1email:1org restriction, clarified that a user can be a member of multiple orgs. Now talks about trial:org limitations Updated "Remove trial limitations" to mention marketplace conversion alongside credit card
Manage users	Some small rewordings around how management of users is org level. New procedure for inviting users to join additional orgs, reconcile alternative email addresses, viewing org memberships

Marketplace stuff

for marketplace-only reviews, see https://github.com/elastic/docs-content/pull/5320/files/f0ec3b1865977d27b60cecda73bbe36fa31ecb78..62ed742a4dbc702843723fc084e6778a0eb68a2f

Page	Description
🆕 Convert a trial to a marketplace subscription	New page. Covers converting an existing Elastic Cloud trial to a marketplace subscription Separate stepper flows for AWS/GCP (org picker) and Azure (resource creation) Documents which orgs are eligible for conversion
Subscribe from a marketplace	Added marketplace benefits to intro New "How marketplaces, organizations, and accounts work together" section explaining marketplace:org:account relationships with per-provider info (AWS, GCP, Azure) New "Multi-cloud strategy" section Links to new conversion page
AWS Marketplace	Updated "Before you begin" to remove pre-multi-org restrictions, added one-sub-per-billing-account constraint Updated troubleshooting to recommend signing in with existing account instead of changing email Added conversion page link
Azure Native ISV Service	New "Multi-org accounts and the Azure portal" section documenting that Azure portal can't handle ambiguous multi-org situations (no org picker) Updated prerequisites to remove "can't use existing email" restriction Rewrote trial conversion section to link to new conversion page Updated billing section to remove old "must not be part of an existing org" guidance
GCP Marketplace	Added conversion page link
Add your billing details	Added link to marketplace trial conversion as alternative to credit card

End user facing

Page	Description
🆕 Switch between Elastic Cloud organizations	New page. Indicates that you can belong to multiple orgs, why you might be a member of multiple orgs, and how you can view and switch between your orgs
Manage your Cloud account and preferences	Reorganized the page to make room for a "manage your organizations" H1, introducing the concept of multiple organizations and the related tasks (join/leave, view/switch)
Join or leave an organization	Reworked the page to clarify that you can be a member of multiple orgs, basics about switching between orgs you have joined. Removed steps for making your email address available to join another organization (no longer needed)
Update your email address	Removed hints about emails being bound to only one org at a time. Left the steps to sign up using an existing email address (until we can determine they are no longer needed)

Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?

• Yes
• No

2. If you answered "Yes" to the previous question, please specify the tool(s) and model(s) used (e.g., Google Gemini, OpenAI ChatGPT-4, etc.).

Tool(s) and model(s) used: cursor auto

[github-actions]

Vale Linting Results

Summary: 4 warnings, 9 suggestions found

⚠️ Warnings (4)

File	Line	Rule	Message
deploy-manage/deploy/elastic-cloud/aws-marketplace.md	56	Elastic.Spelling	'signup' is a possible misspelling.
deploy-manage/deploy/elastic-cloud/aws-marketplace.md	94	Elastic.EndPuntuaction	Don't end headings with punctuation.
deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md	94	Elastic.Spelling	'ecloud' is a possible misspelling.
deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md	15	Elastic.BritishSpellings	Use American English spelling 'toward' instead of British English 'towards'.

💡 Suggestions (9)

File	Line	Rule	Message
deploy-manage/cloud-organization.md	47	Elastic.FirstPerson	Use caution when using first-person pronouns such as 'my.'
deploy-manage/cloud-organization/_snippets/switch-orgs.md	9	Elastic.FirstPerson	Use caution when using first-person pronouns such as 'My.'
deploy-manage/cloud-organization/_snippets/switch-orgs.md	12	Elastic.FirstPerson	Use caution when using first-person pronouns such as 'My.'
deploy-manage/cloud-organization/_snippets/view-orgs.md	9	Elastic.FirstPerson	Use caution when using first-person pronouns such as 'My.'
deploy-manage/cloud-organization/_snippets/view-orgs.md	11	Elastic.FirstPerson	Use caution when using first-person pronouns such as 'My.'
deploy-manage/cloud-organization/_snippets/view-orgs.md	20	Elastic.FirstPerson	Use caution when using first-person pronouns such as 'My.'
deploy-manage/cloud-organization/manage-multiple-organizations.md	19	Elastic.FirstPerson	Use caution when using first-person pronouns such as 'my.'
deploy-manage/cloud-organization/manage-multiple-organizations.md	41	Elastic.FirstPerson	Use caution when using first-person pronouns such as 'My.'
deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md	193	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.

---

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

[github-actions]

🔍 Preview links for changed docs

• cloud-account/index.md
• cloud-account/join-or-leave-an-organization.md
• cloud-account/multifactor-authentication.md
• cloud-account/switch-organizations.md
• cloud-account/update-your-email-address.md
• deploy-manage/cloud-organization.md
• deploy-manage/cloud-organization/billing.md
• deploy-manage/cloud-organization/billing/add-billing-details.md
• deploy-manage/cloud-organization/billing/billing-faq.md
• deploy-manage/cloud-organization/manage-multiple-organizations.md

More links …

• deploy-manage/cloud-organization/operational-emails.md
• deploy-manage/cloud-organization/tools-and-apis.md
• deploy-manage/deploy/elastic-cloud/aws-marketplace.md
• deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md
• deploy-manage/deploy/elastic-cloud/create-an-organization.md
• deploy-manage/deploy/elastic-cloud/google-cloud-platform-marketplace.md
• deploy-manage/deploy/elastic-cloud/marketplace-trial-conversion.md
• deploy-manage/deploy/elastic-cloud/subscribe-from-marketplace.md
• deploy-manage/users-roles.md
• deploy-manage/users-roles/cloud-organization/manage-users.md

[shainaraskas]

also todo:

In the future (multi-org) that docs page should tell users to invite the desired user/email to the org and delete other/alternative user/emails from it.

https://www.elastic.co/docs/cloud-account/update-your-email-address#sign-up-existing https://www.elastic.co/docs/deploy-manage/deploy/elastic-cloud/create-an-organization

done

[shainaraskas]

todo for marketplaces https://github.com/elastic/docs-content-internal/issues/833#issuecomment-4049645047