clarify MFA for team use case #1576
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Clarify MFA for team use case by making it clear that the only secure and recommended way is to add members to the organization.
Background & Motivation
Background is per https://github.com/elastic/sdh-control-plane/issues/9470#issuecomment-2820959159 and https://github.com/elastic/support-tech-lead/issues/1564, which I had with @brunofarache internally that we should clarify the docs to make it clear that the only recommended way is to add members to the org.
Before / After PR merged
:: Before
https://www.elastic.co/docs/cloud-account/multifactor-authentication
:: After
Orange part will show up.