Skip to content

chore: document organization settings flows#2614

Open
jonas-jonas wants to merge 1 commit into
masterfrom
jonas-jonas/documentOrgsSettings
Open

chore: document organization settings flows#2614
jonas-jonas wants to merge 1 commit into
masterfrom
jonas-jonas/documentOrgsSettings

Conversation

@jonas-jonas

Copy link
Copy Markdown
Member

Related Issue or Design Document

Checklist

  • I have read the contributing guidelines and signed the CLA.
  • I have referenced an issue containing the design document if my change introduces a new feature.
  • I have read the security policy.
  • I confirm that this pull request does not address a security vulnerability.
    If this pull request addresses a security vulnerability,
    I confirm that I got approval (please contact security@ory.com) from the maintainers to push the changes.
  • I have added tests that prove my fix is effective or that my feature works.
  • I have added the necessary documentation within the code base (if appropriate).

Further comments

Copilot AI review requested due to automatic review settings June 8, 2026 20:53

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR expands the Ory Kratos documentation to describe how organization membership can be established via the user settings flow, and cross-links the settings-flow docs with the organizations docs to make the flow discoverable.

Changes:

  • Added an info note to the settings-flow documentation describing organization-scoped settings flows and linking to the organizations guide.
  • Added a new “Bind an identity to an organization through the settings flow” section to the organizations documentation, including expected behavioral differences.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File Description
docs/kratos/self-service/flows/user-settings.mdx Adds a note about scoping the settings flow to an organization and links to the organizations doc.
docs/kratos/organizations/organizations.mdx Documents how linking an org SSO connection in settings binds the identity to the organization and describes behavior changes.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +620 to +622
You can scope the settings flow to an organization by passing the `organization` query parameter. The flow then returns link nodes
only for that organization's SSO connections, and linking one binds the identity to the organization. See
[Bind an identity to an organization through the settings flow](../../organizations/organizations.mdx#bind-an-identity-to-an-organization-through-the-settings-flow).
Comment on lines +270 to +271
To scope a settings flow to an organization, pass the organization ID in the `organization` query parameter when you initialize
the flow:
https://$PROJECT_SLUG.projects.oryapis.com/self-service/settings/browser?organization=$ORGANIZATION_ID
```

The same parameter works for the API (native) flow at `/self-service/settings/api`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants