Skip to content

Conversation

kunisen
Copy link
Contributor

@kunisen kunisen commented Jul 1, 2025

Description

In a recent internal discussion, @alxchalkias shared his insights that we could update the doc to make it more clear that we only support one email factor.

This PR is to address this context piece.

Preview

cloud-account/multifactor-authentication.md

In a [recent internal discussion](https://elasticco.atlassian.net/browse/IAM-1778?focusedCommentId=251189), @alxchalkias shared his insights that we could update the doc to make it more clear that we only support one email factor. 

This PR is to address this context piece.
@kunisen kunisen requested a review from alxchalkias July 1, 2025 08:34
@kunisen kunisen requested a review from a team as a code owner July 1, 2025 08:34
@github-actions
Copy link

github-actions bot commented Jul 1, 2025

🔍 Preview links for changed docs:

🔔 The preview site may take up to 3 minutes to finish building. These links will become live once it completes.

@kunisen kunisen self-assigned this Jul 1, 2025
@kunisen kunisen added documentation Improvements or additions to documentation supportability ability enable self-service or support of product labels Jul 1, 2025
Copy link
Contributor

@alxchalkias alxchalkias left a comment

Choose a reason for hiding this comment

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

LGTM!

Copy link
Contributor

@yetanothertw yetanothertw left a comment

Choose a reason for hiding this comment

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

Thank you for adding this!
I've left a very minor editorial suggestion, in case you'd like to implement it.

@eedugon
Copy link
Contributor

eedugon commented Jul 1, 2025

I'm totally ok with the change, but I'd like to highlight that ideally we should try to get rid of the entire FAQ at some point (I worked with the migration of this section of the docs, and I don't remember there was this big FAQ here 🤦 )

From a tech writing and communication perspective it would be much better to identify the key items of the questions and introduce them properly within the doc, so the most important items are correctly highlighted and the narrative makes more sense.

But once said that, and considering we already have this FAQ, I'm ok with adding more questions until we decide to change it.

cc: @shainaraskas

PS - If @alxchalkias and @shainaraskas agree with it we could also create an issue to restructure this page and ensure we cover all items without the need of a FAQ, as after reading the questions I think it should be pretty straightforward. Of course this wouldn't be a task for @kunisen , but for us (core-docs team).

Copy link
Contributor

@eedugon eedugon left a comment

Choose a reason for hiding this comment

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

LGTM too!

@github-actions
Copy link

github-actions bot commented Jul 2, 2025

🔍 Preview links for changed docs

@kunisen
Copy link
Contributor Author

kunisen commented Jul 2, 2025

for us (core-docs team).

Thanks @eedugon!
IMHO it would be a huge effort to rewrite, which would be best to take some time to think and do it.
So from my point of view, it would be best to merge the current one first, and feel free to make further edits at your convenience. 🙏

That said, I will go and merge this one, but feel free to tweak the structure to avoid FAQ style if needed.
Thank you all!

@kunisen kunisen enabled auto-merge (squash) July 2, 2025 00:30
@kunisen kunisen merged commit fbd982c into main Jul 2, 2025
6 of 7 checks passed
@kunisen kunisen deleted the kunisen-docpr-jira-iam1778 branch July 2, 2025 00:32
@alxchalkias
Copy link
Contributor

PS - If @alxchalkias and @shainaraskas agree with it we could also create an issue to restructure this page and ensure we cover all items without the need of a FAQ, as after reading the questions I think it should be pretty straightforward. Of course this wouldn't be a task for @kunisen , but for us (core-docs team).

I agree we could restructure the page, but this isn't a very high prio thing to do, so I'd let core-docs team decide on the timing of this.

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

Labels

documentation Improvements or additions to documentation supportability ability enable self-service or support of product

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants