clerk · im2nguyen · Oct 31, 2025 · Oct 31, 2025 · Oct 31, 2025 · Oct 31, 2025
@@ -3,7 +3,7 @@
 | Property                                      | Type                                                             | Description                                                                                                                            |
 | --------------------------------------------- | ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
 | <a id="feature"></a> `feature?`               | `Autocomplete`\<<code> user:${string} \| org:${string} </code>\> | The [feature](/docs/guides/billing/overview) to check for.                                                                             |
-| <a id="permission"></a> `permission?`         | `DisallowSystemPermissions`\<`P`\>                               | The [permission](/docs/guides/organizations/roles-and-permissions) to check for.                                                       |
+| <a id="permission"></a> `permission?`         | `DisallowSystemPermissions`\<`P`\>                               | The [permission](/docs/guides/organizations/control-access/roles-and-permissions) to check for.                                                       |
 | <a id="plan"></a> `plan?`                     | `Autocomplete`\<<code> user:${string} \| org:${string} </code>\> | The [plan](/docs/guides/billing/overview) to check for.                                                                                |
 | <a id="reverification"></a> `reverification?` | [`ReverificationConfig`](reverification-config.mdx)              | The reverification configuration to check for. This feature is currently in public beta. **It is not recommended for production use.** |
-| <a id="role"></a> `role?`                     | `string`                                                         | The [role](/docs/guides/organizations/roles-and-permissions) to check for.                                                             |
+| <a id="role"></a> `role?`                     | `string`                                                         | The [role](/docs/guides/organizations/control-access/roles-and-permissions) to check for.                                                             |
@@ -1,3 +1,3 @@
 `OrganizationCustomRoleKey` is a type that represents the user's role in an organization. It will be string unless the developer has provided their own types through [`ClerkAuthorization`](/docs/guides/development/override-clerk-types-interfaces#example-custom-roles-and-permissions).
 
-Clerk provides the [default roles](/docs/guides/organizations/roles-and-permissions#default-roles) `org:admin` and `org:member`. However, you can create [custom roles](/docs/guides/organizations/roles-and-permissions#custom-roles) as well.
+Clerk provides the [default roles](/docs/guides/organizations/control-access/roles-and-permissions#default-roles) `org:admin` and `org:member`. However, you can create [custom roles](/docs/guides/organizations/control-access/roles-and-permissions#custom-roles) as well.
@@ -1,6 +1,6 @@
 The `Organization` object holds information about an organization, as well as methods for managing it.
 
-To use these methods, you must have the **Organizations** feature [enabled in your app's settings in the Clerk Dashboard](/docs/guides/organizations/overview#enable-organizations-in-your-application).
+To use these methods, you must have the **Organizations** feature [enabled in your app's settings in the Clerk Dashboard](/docs/guides/organizations/overview).
 
 ## Properties
 

@@ -1,6 +1,6 @@
 | Property                                              | Type                                                                                                                                                                                                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                                  |
 | ----------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <a id="domains"></a> `domains?`                       | <code>true \| \{ initialPage?: number; pageSize?: number; \} & \{ enrollmentMode?: "manual_invitation" \| "automatic_invitation" \| "automatic_suggestion"; \} & \{ infinite?: boolean; keepPreviousData?: boolean; \}</code> | If set to `true`, all default properties will be used.<br /> Otherwise, accepts an object with the following optional properties: <ul> <li>`enrollmentMode`: A string that filters the domains by the provided [enrollment mode](/docs/guides/organizations/verified-domains#enrollment-mode).</li> <li>Any of the properties described in [Shared properties](#shared-properties).</li> </ul>                                               |
+| <a id="domains"></a> `domains?`                       | <code>true \| \{ initialPage?: number; pageSize?: number; \} & \{ enrollmentMode?: "manual_invitation" \| "automatic_invitation" \| "automatic_suggestion"; \} & \{ infinite?: boolean; keepPreviousData?: boolean; \}</code> | If set to `true`, all default properties will be used.<br /> Otherwise, accepts an object with the following optional properties: <ul> <li>`enrollmentMode`: A string that filters the domains by the provided [enrollment mode](/docs/guides/organizations/add-members/verified-domains#enrollment-mode).</li> <li>Any of the properties described in [Shared properties](#shared-properties).</li> </ul>                                               |
 | <a id="invitations"></a> `invitations?`               | <code>true \| \{ initialPage?: number; pageSize?: number; \} & \{ status?: ("expired" \| "pending" \| "accepted" \| "revoked")[]; \} & \{ infinite?: boolean; keepPreviousData?: boolean; \}</code>                           | If set to `true`, all default properties will be used.<br /> Otherwise, accepts an object with the following optional properties: <ul> <li>`status`: A string that filters the invitations by the provided status.</li> <li>Any of the properties described in [Shared properties](#shared-properties).</li> </ul>                                                                                                                           |
 | <a id="membershiprequests"></a> `membershipRequests?` | <code>true \| \{ initialPage?: number; pageSize?: number; \} & \{ status?: "expired" \| "pending" \| "accepted" \| "revoked"; \} & \{ infinite?: boolean; keepPreviousData?: boolean; \}</code>                               | If set to `true`, all default properties will be used.<br /> Otherwise, accepts an object with the following optional properties: <ul> <li>`status`: A string that filters the membership requests by the provided status.</li> <li>Any of the properties described in [Shared properties](#shared-properties).</li> </ul>                                                                                                                   |
 | <a id="memberships"></a> `memberships?`               | <code>true \| \{ initialPage?: number; pageSize?: number; \} & \{ query?: string; role?: string[]; \} & \{ infinite?: boolean; keepPreviousData?: boolean; \}</code>                                                          | If set to `true`, all default properties will be used.<br /> Otherwise, accepts an object with the following optional properties: <ul> <li>`role`: An array of [`OrganizationCustomRoleKey`](/docs/reference/javascript/types/organization-custom-role-key).</li> <li>`query`: A string that filters the memberships by the provided string.</li> <li>Any of the properties described in [Shared properties](#shared-properties).</li> </ul> |
@@ -1,2 +1,2 @@
 > [!WARNING]
-> Using `has()` **on the server-side** to check permissions works only with **custom permissions**, as [system permissions](/docs/guides/organizations/roles-and-permissions#system-permissions) aren't included in the session token claims. To check system permissions, verify the user's role instead.
+> Using `has()` **on the server-side** to check permissions works only with **custom permissions**, as [system permissions](/docs/guides/organizations/control-access/roles-and-permissions#system-permissions) aren't included in the session token claims. To check system permissions, verify the user's role instead.
@@ -26,7 +26,7 @@ object has the type `OrganizationSyncOptions`, which has the following propertie
   - `personalAccountPatterns`
   - <code>[Pattern](#pattern)\[]</code>
 
-  URL patterns for resources that exist within the context of a user's [personal account](/docs/guides/organizations/overview#allow-personal-accounts).
+  URL patterns for resources that exist within the context of a user's [personal account](/docs/guides/organizations/configure#enable-organizations).
 
   If the route also matches the `organizationPattern` prop, the `organizationPattern` prop takes precedence.
 

@@ -0,0 +1 @@
+This happens because the choose-organization session task must be completed before the user's authentication process can be considered complete. Session tasks are pending requirements that users must complete after authentication. Learn more about [session tasks](/docs/guides/configure/session-tasks).
@@ -6,23 +6,23 @@ sdk: expo
 
 <TutorialHero
   exampleRepo={[
-  {
-    title: "Expo quickstart repo",
-    link: "https://github.com/clerk/clerk-expo-quickstart",
-  },
-]}
+    {
+      title: "Expo quickstart repo",
+      link: "https://github.com/clerk/clerk-expo-quickstart",
+    },
+  ]}
   beforeYouStart={[
-  {
-    title: "Set up a Clerk application",
-    link: "/docs/getting-started/quickstart/setup-clerk",
-    icon: "clerk",
-  },
-  {
-    title: "Create an Expo app",
-    link: "https://docs.expo.dev/get-started/create-a-project/",
-    icon: "expo",
-  },
-]}
+    {
+      title: "Set up a Clerk application",
+      link: "/docs/getting-started/quickstart/setup-clerk",
+      icon: "clerk",
+    },
+    {
+      title: "Create an Expo app",
+      link: "https://docs.expo.dev/get-started/create-a-project/",
+      icon: "expo",
+    },
+  ]}
 />
 
 <Steps>

@@ -6,12 +6,12 @@ sdk: ios
 
 <TutorialHero
   beforeYouStart={[
-{
-title: "Set up a Clerk application",
-link: "/docs/getting-started/quickstart/setup-clerk",
-icon: "clerk",
-}
-]}
+    {
+      title: "Set up a Clerk application",
+      link: "/docs/getting-started/quickstart/setup-clerk",
+      icon: "clerk",
+    }
+  ]}
 />
 
 <Steps>

@@ -12,7 +12,7 @@ Clerk Billing for B2B SaaS allows you to create plans and manage subscriptions *
 
 ## Create a plan
 
-Subscription plans are what your customers subscribe to. There is no limit to the number of plans you can create. If your Clerk instance has existing [custom permissions](/docs/guides/organizations/roles-and-permissions), the corresponding features from those permissions will automatically be added to the free plan for orgs. This ensures that organization members get the same set of custom permissions when billing is enabled, because all organizations start on the free plan.
+Subscription plans are what your customers subscribe to. There is no limit to the number of plans you can create. If your Clerk instance has existing [custom permissions](/docs/guides/organizations/control-access/roles-and-permissions), the corresponding features from those permissions will automatically be added to the free plan for orgs. This ensures that organization members get the same set of custom permissions when billing is enabled, because all organizations start on the free plan.
 
 To create a plan, navigate to the [**Plans**](https://dashboard.clerk.com/~/billing/plans) page in the Clerk Dashboard. Here, you can create, edit, and delete plans. To setup B2B billing, select the **Plans for Organizations** tab and select **Add Plan**. When creating a plan, you can also create [features](/docs/guides/secure/features) for the plan; see the next section for more information.
 

@@ -5,17 +5,17 @@ description: Learn how to allow users to sign up and sign in to your Clerk app w
 
 <TutorialHero
   beforeYouStart={[
-  {
-    title: "A Clerk application is required.",
-    link: "/docs/getting-started/quickstart/setup-clerk",
-    icon: "clerk",
-  },
-  {
-    title: "A Dropbox Developer account is required.",
-    link: "https://www.dropbox.com/developers",
-    icon: "user-circle",
-  }
-]}
+    {
+      title: "A Clerk application is required.",
+      link: "/docs/getting-started/quickstart/setup-clerk",
+      icon: "clerk",
+    },
+    {
+      title: "A Dropbox Developer account is required.",
+      link: "https://www.dropbox.com/developers",
+      icon: "user-circle",
+    }
+  ]}
 />
 
 Enabling OAuth with Dropbox allows your users to sign up and sign in to your Clerk application with their Dropbox account.

@@ -5,17 +5,17 @@ description: Learn how to allow users to sign up and sign in to your Clerk app w
 
 <TutorialHero
   beforeYouStart={[
-  {
-    title: "A Clerk app is required.",
-    link: "/docs/getting-started/quickstart/setup-clerk",
-    icon: "clerk",
-  },
-  {
-    title: "A Meta Developer account is required.",
-    link: "https://developers.facebook.com/docs/development/register",
-    icon: "user-circle",
-  }
-]}
+    {
+      title: "A Clerk app is required.",
+      link: "/docs/getting-started/quickstart/setup-clerk",
+      icon: "clerk",
+    },
+    {
+      title: "A Meta Developer account is required.",
+      link: "https://developers.facebook.com/docs/development/register",
+      icon: "user-circle",
+    }
+  ]}
 />
 
 Enabling OAuth with Facebook allows your users to sign up and sign in to your Clerk app with their Facebook account.

@@ -5,17 +5,17 @@ description: Learn how to allow users to sign up and sign in to your Clerk app w
 
 <TutorialHero
   beforeYouStart={[
-  {
-    title: "A Clerk app is required.",
-    link: "/docs/getting-started/quickstart/setup-clerk",
-    icon: "clerk",
-  },
-  {
-    title: "A Twitch account is required.",
-    link: "https://www.twitch.tv/signup",
-    icon: "user-circle",
-  }
-]}
+    {
+      title: "A Clerk app is required.",
+      link: "/docs/getting-started/quickstart/setup-clerk",
+      icon: "clerk",
+    },
+    {
+      title: "A Twitch account is required.",
+      link: "https://www.twitch.tv/signup",
+      icon: "user-circle",
+    }
+  ]}
 />
 
 Enabling OAuth with [Twitch](https://dev.twitch.tv/docs/api/reference#oauth-client-credentials-flow) allows your users to sign up and sign in to your Clerk application with their Twitch account.

@@ -33,7 +33,7 @@ The following table lists the available tasks and their corresponding components
 
 | Name | Component |
 | - | - |
-| [Personal accounts disabled (default)](/docs/guides/organizations/overview#allow-personal-accounts) | [`<TaskChooseOrganization />`](/docs/reference/components/authentication/task-choose-organization) |
+| [Personal accounts disabled (default)](/docs/guides/organizations/configure#enable-organizations) | [`<TaskChooseOrganization />`](/docs/reference/components/authentication/task-choose-organization) |
 
 > [!IMPORTANT]
 > Personal accounts being disabled by default was released on 08-22-2025. Applications created before this date will not be able to see the **Allow personal accounts** setting, because personal accounts were enabled by default.
@@ -272,7 +272,7 @@ The `useAuth()` hook and helpers that access the [`Auth` object](/docs/reference
 
 #### Example: Personal accounts disabled
 
-When organizations are enabled, [personal accounts are disabled by default](/docs/guides/organizations/overview#allow-personal-accounts) and your users will be required to select or create an organization after authenticating. Until completed, their session remains `pending`. Pages that are protected using Clerk's protection utilities will treat the user's session as signed-out.
+When organizations are enabled, [personal accounts are disabled by default](/docs/guides/organizations/configure#enable-organizations) and your users will be required to select or create an organization after authenticating. Until completed, their session remains `pending`. Pages that are protected using Clerk's protection utilities will treat the user's session as signed-out.
 
 For `useAuth()`, `isSignedIn` will be `false` and `userId` and `orgId` will be `null` if the user has a `pending` session.
 

@@ -13,7 +13,7 @@ This guide will walk you through how to build a custom flow that handles user im
 
 <Tabs items={["Next.js", "Expo"]}>
   <Tab>
-    The following example builds a dashboard that is only accessible to users with the `org:admin:impersonate` permission. To use this example, you must first [create the custom `org:admin:impersonate` permission](/docs/guides/organizations/roles-and-permissions#custom-permissions). Or you can modify the [authorization checks](!authorization-check) to fit your use case.
+    The following example builds a dashboard that is only accessible to users with the `org:admin:impersonate` permission. To use this example, you must first [create the custom `org:admin:impersonate` permission](/docs/guides/organizations/control-access/roles-and-permissions#custom-permissions). Or you can modify the [authorization checks](!authorization-check) to fit your use case.
 
     In the dashboard, the user will see a list of the application's users. When the user chooses to impersonate a user, they will be signed in as that user and redirected to the homepage.
 

@@ -5,11 +5,11 @@ description: Learn how to use the Clerk API to build a custom flows for acceptin
 
 <Include src="_partials/custom-flows-callout" />
 
-When a user visits an [organization invitation](/docs/guides/organizations/invitations) link, Clerk first checks whether a custom redirect URL was provided.
+When a user visits an [organization invitation](/docs/guides/organizations/add-members/invitations) link, Clerk first checks whether a custom redirect URL was provided.
 
 **If no redirect URL is specified**, the user will be redirected to the appropriate Account Portal page (either [sign-up](/docs/guides/customizing-clerk/account-portal#sign-up) or [sign-in](/docs/guides/customizing-clerk/account-portal#sign-in)), or to the custom sign-up/sign-in pages that you've configured for your application.
 
-**If you specified [a redirect URL when creating the invitation](/docs/guides/organizations/invitations#redirect-url)**, you must handle the authentication flows in your code for that page. You can either embed the [`<SignIn />`](/docs/reference/components/authentication/sign-in) component on that page, or if the prebuilt component doesn't meet your specific needs or if you require more control over the logic, you can rebuild the existing Clerk flows using the Clerk API.
+**If you specified [a redirect URL when creating the invitation](/docs/guides/organizations/add-members/invitations#redirect-url)**, you must handle the authentication flows in your code for that page. You can either embed the [`<SignIn />`](/docs/reference/components/authentication/sign-in) component on that page, or if the prebuilt component doesn't meet your specific needs or if you require more control over the logic, you can rebuild the existing Clerk flows using the Clerk API.
 
 This guide demonstrates how to use Clerk's API to build a custom flow for accepting organization invitations from a link.
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		This happens because the choose-organization session task must be completed before the user's authentication process can be considered complete. Session tasks are pending requirements that users must complete after authentication. Learn more about [session tasks](/docs/guides/configure/session-tasks).