Skip to content

Commit

Permalink
Update docs/authentication/social-connections/oauth.mdx
Browse files Browse the repository at this point in the history 
Co-authored-by: Alexis Aguilar <[email protected]>
  • Loading branch information
@victoriaxyz @alexisintech
victoriaxyz and alexisintech authored Nov 13, 2024
1 parent a5573d5 commit a627b40
Showing 1 changed file with 0 additions and 1 deletion.
1 change: 0 additions & 1 deletion docs/authentication/social-connections/oauth.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -130,7 +130,6 @@ For each social provider, you can disable the option to sign up and sign in to y

For example, say your application wants to read a user's GitHub repository data but doesn't want to allow the user to authenticate with their GitHub account. The user can sign up with their email and password, or whatever authentication method you choose, and then afterwards, connect their GitHub account to your application through their user profile. The easiest way to enable this for your users is by using the [`<UserProfile />`](/docs/components/user/user-profile) component. If you prefer to build a custom user interface, see how to [build a social connection flow using Clerk's API](/docs/custom-flows/oauth-connections).

After sign-up, connections can be made through the [`<UserProfile/>`](/docs/components/user/user-profile) component, or with a [custom flow](/docs/custom-flows/oauth-connections).

To configure the option for users to sign up and sign in with a social provider:

Expand Down

0 comments on commit a627b40

Please sign in to comment.