add relevant links to sso and auth-checks

Author: tu

docs/guides/organizations/add-members/sso.mdx

@@ -5,7 +5,9 @@ metadata:
   title: Set up organization-level SAML and OIDC for B2B/B2C apps
 ---
 
-Clerk provides enterprise single sign-on (SSO) through a feature called **enterprise connections**. You can enable enterprise connections for specific organizations, allowing members to authenticate through their company's identity provider using SAML or OIDC protocols. When users sign up or sign in using an organization's enterprise connection, Clerk automatically adds them as members of that organization and assigns them the [default role](/docs/guides/organizations/control-access/roles-and-permissions#the-default-role-for-members).
+Clerk provides enterprise single sign-on (SSO) through a feature called [**enterprise connections**](/docs/guides/configure/auth-strategies/enterprise-connections/overview). You can enable enterprise connections for specific organizations, allowing members to authenticate through their company's identity provider using SAML or OIDC protocols. 
+
+When users sign up or sign in using an organization's enterprise connection, Clerk automatically adds them as members of that organization and assigns them the [default role](/docs/guides/organizations/control-access/roles-and-permissions#the-default-role-for-members). This process is known as [Just-in-Time (JIT) provisioning](/docs/guides/configure/auth-strategies/enterprise-connections/jit-provisioning).
 
 ## When to use enterprise SSO
 
@@ -72,6 +74,8 @@ To remove these users from the original organization, use either the [Backend AP
 
 Now that you've set up enterprise SSO, you can:
 
+- [Learn more about enterprise connections](/docs/guides/configure/auth-strategies/enterprise-connections/overview) for advanced configuration options
+- [Understand JIT provisioning](/docs/guides/configure/auth-strategies/enterprise-connections/jit-provisioning) to customize how users are automatically added to organizations
 - [Configure verified domains](/docs/guides/organizations/add-members/verified-domains) for users who don't use SSO
 - [Invite specific users](/docs/guides/organizations/add-members/invitations) to your organization
 - [Set up roles and permissions](/docs/guides/organizations/control-access/roles-and-permissions) to control what SSO users can access

docs/guides/organizations/control-access/roles-and-permissions.mdx

@@ -140,7 +140,7 @@ It's best practice to always verify whether or not a user is **authorized** to a
 
 Now that you've set up roles and permissions, you can:
 
-- [Learn how to limit access to content or entire routes based on a user's role or permissions](/docs/guides/organizations/control-access/check-access)
+- [Perform authorization checks](/docs/guides/secure/authorization-checks) to limit access to content or entire routes based on a user's role or permissions
 - [Learn how to automatically invite users to an organization based on their email domain](/docs/guides/organizations/add-members/verified-domains)
 - [Learn how to manually invite users to an organization](/docs/guides/organizations/add-members/invitations)
-- [Learn how to automatically add users to an organization based on their email domain](/docs/guides/organizations/add-members/sso)
+- [Learn how to automatically add users to an organization through enterprise SSO](/docs/guides/organizations/add-members/sso)

docs/guides/organizations/overview.mdx

@@ -78,6 +78,10 @@ The Clerk Dashboard provides comprehensive organization growth tracking with the
 
 For B2B products, organization-level analytics reveal which customer accounts are growing or churning. This helps you understand product-market fit at the account level, not just individual usage.
 
+### Monetize with subscription plans
+
+Clerk's [billing for B2B](/docs/guides/billing/for-b2b) lets you create subscription plans and manage payments for organizations. You can gate features behind specific plans, ensuring organizations only access functionality they've subscribed to. Billing integrates directly with roles and permissions, so when you create custom permissions tied to features, those permissions only work if the organization's active plan includes that feature. This makes it easy to build tiered pricing models where higher-tier plans unlock additional capabilities.
+
 ## Next steps
 
 Now that you understand what Organizations are and how they work, here's how to implement them: