Add MFA docs and session profiles to new docs structure - #710
Open
grahamritter wants to merge 5 commits into
Open
Add MFA docs and session profiles to new docs structure#710grahamritter wants to merge 5 commits into
grahamritter wants to merge 5 commits into
Conversation
moeodeh3
force-pushed
the
mfa-sessions-new-structure
branch
from
July 10, 2026 20:29
fcfc7c2 to
bd359a1
Compare
moeodeh3
force-pushed
the
mfa-sessions-new-structure
branch
2 times, most recently
from
July 16, 2026 15:39
846d88f to
d4c3f0c
Compare
Ports content from PR #619 (amir/mfa-docs) to the current docs structure: - Add MFA pages: overview, satisfying-mfa, enforcement-and-recovery, examples - Add session profiles page - Convert sessions.mdx to sessions/overview.mdx with scoped sessions section - Update docs.json navigation with Sessions and MFA groups - Fix all cross-references to use features/authentication/sessions/overview - Add redirects for old session paths - Fix internal links to use current paths (features/policies/, api-reference/, etc.) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
moeodeh3
force-pushed
the
mfa-sessions-new-structure
branch
from
August 17, 2026 18:20
d4c3f0c to
03900bf
Compare
hadrelandon
reviewed
Aug 17, 2026
| activity.resource == 'MFA_POLICY' && activity.action == 'DELETE' | ||
| ``` | ||
|
|
||
| With this setup, when a user is locked out, you can verify their identity through your own process and then delete the MFA policy using the DA user to restore access. |
Contributor
There was a problem hiding this comment.
nit: i assume somewhere else we have DA means delegated access, but it might be worth mentioning that DA abbreviates from delegated access.
we also switch between DA and delegated access user a lot in this doc, is there a reason or should we mention once and inform the abbreviation and use the abbreviation throughout?
hadrelandon
reviewed
Aug 17, 2026
| ] | ||
| } | ||
| ], | ||
| order: 0, |
Contributor
There was a problem hiding this comment.
nit: we mention userId: "<target-user-id>", // Required: the user this MFA policy applies to
would it be useful to have a comment on this order so people know its the order they apply in?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary
features/authentication/)sessions.mdxtosessions/overview.mdxwith scoped sessions sectiondocs.jsonnavigation with Sessions and MFA groups under AuthenticationContext
PR #619 was written against the old
authentication/structure. This PR adapts that content to the currentfeatures/authentication/structure on main, with corrected internal links throughout.Test plan
/authentication/sessionsand/features/authentication/sessionspaths🤖 Generated with Claude Code