Add OAuthConsent and useOAuthConsent docs

[wobsoriano]

🔎 Previews:

• https://clerk.com/docs/pr/rob-oauth-consent-docs/nextjs/reference/components/authentication/oauth-consent
• https://clerk.com/docs/pr/rob-oauth-consent-docs/nextjs/reference/hooks/use-oauth-consent
• https://clerk.com/docs/pr/rob-oauth-consent-docs/reference/components/overview
• https://clerk.com/docs/pr/rob-oauth-consent-docs/reference/objects/clerk
• https://clerk.com/docs/pr/rob-oauth-consent-docs/reference/types/oauth-application
• https://clerk.com/docs/pr/rob-oauth-consent-docs/reference/types/oauth-consent-info
• https://clerk.com/docs/pr/rob-oauth-consent-docs/reference/types/oauth-consent-scope

What does this solve? What changed?

We will now allow C1s to configure a custom OAuth consent page where they can use a custom hook, or the new drop-in <OAuthConsent /> component

Deadline

• No rush

Other resources

• JS PR to add typedoc changes: docs(repo): Add additional typedoc outputs javascript#8483.
• Auto generated Typedoc PR: [ci] Update Typedoc (7a5892f) - Core 3 #3348

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
clerk-docs	Ready	Preview	May 8, 2026 10:54pm

[SarahSoutoul]

@wobsoriano have submitted a docs review with some minor changes:

• Replaced instances of "signed-in users" with "authenticated users".
• Rephrased some of the <OAuthConsent /> component intro to make it a bit more smooth.
• Changed some of the props descriptions for the <OAuthConsent /> component to align with rest of the docs.

Let me know what you think, and left some comments too!

[alexisintech]

this is perfect! I tested with typedoc generation, and everything is working.

my only qualm is putting OAuthApplication in the objects dropdown. we've talked about this distinction before: what are we considering the main Clerk objects? and then everything else gets thrown into /types
in my opinion, I don't consider this a main Clerk object. well yes, it exists on the Clerk object, I don't see this as a frequently used object necessary for building a typical app, while all the other "main" Clerk objects are pretty much non-negotiable when building an app. so imo, I'd move this one to /types

[SarahSoutoul]

this is perfect! I tested with typedoc generation, and everything is working.

my only qualm is putting OAuthApplication in the objects dropdown. we've talked about this distinction before: what are we considering the main Clerk objects? and then everything else gets thrown into /types in my opinion, I don't consider this a main Clerk object. well yes, it exists on the Clerk object, I don't see this as a frequently used object necessary for building a typical app, while all the other "main" Clerk objects are pretty much non-negotiable when building an app. so imo, I'd move this one to /types

Yeah I was in the same boat yesterday debating whether it should be in /objects or /types. Let's move it to types then - that explanation makes sense and justifies it. @wobsoriano I'll do it!

[SarahSoutoul]

Make OAuthApplication a type

@wobsoriano @alexisintech just pushed a commit to make OAuthApplication a type rather than an object. Let me know thoughts!

[alexisintech]

so it does exist on the clerk object, so it's fine to keep it here. i just meant that it doesn't need be in /objects and under objects in the manifest!

[alexisintech]

also, towards the bottom there's a section called "Components"
it will need a section for mountOAuthConsent and unmountOAuthconsent like the other components listed there!

[SarahSoutoul]

Changes here: Add OAuthApplication back to Clerk object overview @alexisintech

[alexisintech]

could you please add all the relevant links added to the PR description here? any JS repo PR's that were related to releasing this future, and the PR's that were related to typedoc changes
we need as much context provided in the PR description as possible 🫶 (more details on this process here)

[SarahSoutoul]

could you please add all the relevant links added to the PR description here? any JS repo PR's that were related to releasing this future, and the PR's that were related to typedoc changes we need as much context provided in the PR description as possible 🫶 (more details on this process here)

@wobsoriano have added the Typedoc PRs related to this but I'll let you add the JS repo PR'S related to releasing this feature.

[SarahSoutoul]

Okay @wobsoriano @alexisintech this is ready for a final review!