Add useOrganizationCreationDefaults to create organization custom flows guide

[LauraBeatris]

🔎 Previews:

• https://clerk.com/docs/pr/laura-update-custom-flows-docs-org-creati-2eb757/guides/development/custom-flows/organizations/create-organizations
• https://clerk.com/docs/pr/laura-update-custom-flows-docs-org-creati-2eb757/react/reference/hooks/use-organization-creation-defaults

What does this solve?

Resolves ORGS-1263

Introduces useOrganizationCreationDefaults hook to the custom flow guides for managing organizations

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-docs	Ready	Preview	Feb 3, 2026 6:09pm

[LauraBeatris]

Waiting on clerk/javascript#7690 to get merged first

[LauraBeatris]

We still have to release the clerk-js changes in case you'd like to test in production, but I've opened the PR already to get a review on the copy

[alexisintech]

left a review to use a partial for the duplicated code between the hook reference guide and the custom flow. other than that, i'd like sarah to update the "related sources" section as she recently did work across the docs related to that.
once that's done, i'm sure she will give you an approval 😸💖 thanks laura!!! great work on the docs here, thanks for adding all those sdk examples

[SarahSoutoul]

left a review to use a partial for the duplicated code between the hook reference guide and the custom flow. other than that, i'd like sarah to update the "related sources" section as she recently did work across the docs related to that. once that's done, i'm sure she will give you an approval 😸💖 thanks laura!!! great work on the docs here, thanks for adding all those sdk examples

Have revamped the "Related guides" sections and made them consistent: Make next steps consistent. Will review the rest of the PR @LauraBeatris!

[SarahSoutoul]

Okay have got two things I've noticed @alexisintech:

1. When selecting any SDKs that isn't included in the custom flow components, this is how it appears. I'm not sure if this is what we want, or we may a default Next.js example to be showing when one is on the Express SDK for e.g.

   

2. Now that the custom flow uses two different hooks, think we can simplify the intro to be less redundant with "The following example" being used twice. Happy to revamp it if you'd like @LauraBeatris but interested to get your thoughts on the first point.

[SarahSoutoul]

Also, I've realized we can bring the parameters and returns from Typedoc like the other hooks, so made a PR in javascript to make that happen. And then got this commit to use the Typedoc output. @LauraBeatris @alexisintech

[alexisintech]

Okay have got two things I've noticed @alexisintech:

1. When selecting any SDKs that isn't included in the custom flow components, this is how it appears. I'm not sure if this is what we want, or we may a default Next.js example to be showing when one is on the Express SDK for e.g.
   
2. Now that the custom flow uses two different hooks, think we can simplify the intro to be less redundant with "The following example" being used twice. Happy to revamp it if you'd like @LauraBeatris but interested to get your thoughts on the first point.

ahh very good catch!! yes let's fix for sdk specificity

[SarahSoutoul]

Remove duplication of following example

Okay have pushed a commit for point number 2.

Will think of how to tackle point number 1.

[SarahSoutoul]

Here is what I did for point 2: Add SDK specificity. Let me know what you guys thin @alexisintech @LauraBeatris

[alexisintech]

i think that looks great, sarah, thank you

i've also added setting the created org as the active org as i feel like that's an important step in the org creation process that we should show users how to do!

[alexisintech]

perfection 😸💖

[alexisintech]

@LauraBeatris oh wait, is this for core-2 or core-3? if it's for core-3, we need to change the base branch to the core-3 branch!

[LauraBeatris]

@LauraBeatris oh wait, is this for core-2 or core-3? if it's for core-3, we need to change the base branch to the core-3 branch!

@alexisintech This hook is in both core 2 and core 3

[alexisintech]

@LauraBeatris oh wait, is this for core-2 or core-3? if it's for core-3, we need to change the base branch to the core-3 branch!

@alexisintech This hook is in both core 2 and core 3

then i think this is good to merge, when you're ready :)