Skip to content

Multi-org membership (tech preview)#5351

Open
shainaraskas wants to merge 4 commits intomainfrom
multi-org-preview
Open

Multi-org membership (tech preview)#5351
shainaraskas wants to merge 4 commits intomainfrom
multi-org-preview

Conversation

@shainaraskas
Copy link
Collaborator

@shainaraskas shainaraskas commented Mar 3, 2026

Summary

Adds a hidden one-pager for the multi-org membership tech preview. Audience for this page is administrators (end user content will come for GA unless @alxchalkias wants it now)

Preview: Manage multiple Elastic Cloud organizations

A couple of things are in snippets because I know they will be shared by the admin and end user audiences (GA content draft is here)

Generative AI disclosure

  1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?
  • Yes polish stuff
  • No

@github-actions
Copy link
Contributor

github-actions bot commented Mar 3, 2026

Vale Linting Results

Summary: 7 suggestions found

💡 Suggestions (7)
File Line Rule Message
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 17 Elastic.FirstPerson Use caution when using first-person pronouns such as 'my.'
deploy-manage/cloud-organization/manage-multiple-organizations.md 38 Elastic.FirstPerson Use caution when using first-person pronouns such as 'My.'

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
Copy link
Contributor

github-actions bot commented Mar 3, 2026

🔍 Preview links for changed docs

@shainaraskas shainaraskas requested a review from alxchalkias March 3, 2026 22:19
@shainaraskas shainaraskas marked this pull request as ready for review March 3, 2026 22:19
@shainaraskas shainaraskas requested a review from a team as a code owner March 3, 2026 22:19

% ## Delete an organization

% Can it be done? Do we want to document this?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not something that can be done by the user. They can only leave an org and we have guardrails for the last Org owner to leave the org (bills paid and resources terminated).

@lloydmeta to double-check

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

confirmed.


If a user already has an {{ecloud}} account, then they don't need to sign up again. Instead, they can log in with their selected login method.

If your organization uses [SAML SSO](/deploy-manage/users-roles/cloud-organization/configure-saml-authentication.md), then you don't need to invite users to join the organization. Users are added to the organization automatically when they log in to your identity provider SSO URL.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nathalie-tran can you confirm this will work as described here?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it should (we are trying to push to QA to test the real full flow to ensure that it will work as described here).


If your organization uses [SAML SSO](/deploy-manage/users-roles/cloud-organization/configure-saml-authentication.md), then you don't need to invite users to join the organization. Users are added to the organization automatically when they log in to your identity provider SSO URL.

Organizations can have different authentication requirements. For example, one organization might enforce SAML SSO, while another organization might enforce email-based authentication. If your organization enforces a specific login method, then the user will need to use that method to log in, and might be prompted to re-authenticate.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

email-based auth cannot be enforced. The second example of enforcement is Google/Microsoft login (which is a different flavor of SSO)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤦 working too fast. thanks for catching

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants