docs review

Author: alexisintech

clerk-typedoc/shared/use-organization-params.mdx

@@ -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/add-members/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/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" \| "revoked" \| "pending" \| "accepted")[]; \} & \{ 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" \| "revoked" \| "pending" \| "accepted"; \} & \{ 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> |

clerk-typedoc/types/check-authorization-params-from-session-claims.mdx

@@ -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/control-access/roles-and-permissions) to check for.                                                       |
+| <a id="permission"></a> `permission?`         | `DisallowSystemPermissions`\<`P`\>                               | The [permission](/docs/guides/organizations/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/control-access/roles-and-permissions) to check for.                                                             |
+| <a id="role"></a> `role?`                     | `string`                                                         | The [role](/docs/guides/organizations/roles-and-permissions) to check for.                                                             |

clerk-typedoc/types/organization-custom-role-key.mdx

@@ -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/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.
+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.

docs/_partials/has-warning.mdx

@@ -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/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.
+> 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.

docs/guides/billing/for-b2b.mdx

@@ -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/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.
+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.
 
 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.
 

docs/guides/development/custom-flows/account-updates/user-impersonation.mdx

@@ -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/control-access/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/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.
 

docs/guides/development/custom-flows/organizations/accept-organization-invitations.mdx

@@ -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/add-members/invitations) link, Clerk first checks whether a custom redirect URL was provided.
+When a user visits an [organization invitation](/docs/guides/organizations/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/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.
+**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.
 
 This guide demonstrates how to use Clerk's API to build a custom flow for accepting organization invitations from a link.
 

docs/guides/development/custom-flows/organizations/manage-membership-requests.mdx

@@ -5,7 +5,7 @@ description: Learn how to use the Clerk API to build a custom flow for managing
 
 <Include src="_partials/custom-flows-callout" />
 
-This guide will demonstrate how to use the Clerk API to build a custom flow for managing [organization membership requests](/docs/guides/organizations/add-members/verified-domains#membership-requests).
+This guide will demonstrate how to use the Clerk API to build a custom flow for managing [organization membership requests](/docs/guides/organizations/verified-domains#membership-requests).
 
 <Tabs items={["Next.js", "JavaScript"]}>
   <Tab>

docs/guides/development/custom-flows/organizations/manage-organization-invitations.mdx

@@ -5,14 +5,14 @@ description: Learn how to use the Clerk API to build a custom flow for creating
 
 <Include src="_partials/custom-flows-callout" />
 
-Organization members with appropriate [permissions](/docs/guides/organizations/control-access/roles-and-permissions) can invite new users to their organization and manage those invitations. The invitation recipient can be either an existing user of your application or a new user. If they are a new user, they will need to sign up in order to accept the invitation.
+Organization members with appropriate [permissions](/docs/guides/organizations/roles-and-permissions) can invite new users to their organization and manage those invitations. The invitation recipient can be either an existing user of your application or a new user. If they are a new user, they will need to sign up in order to accept the invitation.
 
 Users with the appropriate permissions can also revoke organization invitations for users that have not yet joined, which will prevent the user from becoming an organization member.
 
 This guide will demonstrate how to use the Clerk API to build a custom flow for inviting users to an organization and managing an organization's pending invitations.
 
 > [!NOTE]
-> This guide is for creating and managing organization invitations client-side. You can also create an organization invitation using the Backend API. See the [organization invitations reference](/docs/guides/organizations/add-members/invitations) for more information.
+> This guide is for creating and managing organization invitations client-side. You can also create an organization invitation using the Backend API. See the [organization invitations reference](/docs/guides/organizations/invitations) for more information.
 >
 > Also, see the [custom flow for accepting organization invitations](/docs/guides/development/custom-flows/organizations/accept-organization-invitations).
 

docs/guides/development/custom-flows/organizations/manage-roles.mdx

@@ -5,7 +5,7 @@ description: Learn how to use the Clerk API build a custom flow for managing mem
 
 <Include src="_partials/custom-flows-callout" />
 
-Organization members with appropriate [permissions](/docs/guides/organizations/control-access/roles-and-permissions#permissions) can manage a member's [role](/docs/guides/organizations/control-access/roles-and-permissions#roles) and remove members within an organization.
+Organization members with appropriate [permissions](/docs/guides/organizations/roles-and-permissions#permissions) can manage a member's [role](/docs/guides/organizations/roles-and-permissions#roles) and remove members within an organization.
 
 This guide will demonstrate how to use the Clerk API to build a custom flow for managing member roles in an organization.