From 355f0396ece780331679c8232f6ec30d604a2403 Mon Sep 17 00:00:00 2001 From: Barry Grenon Date: Tue, 22 Oct 2024 23:07:51 -0300 Subject: [PATCH] Update content/docs/guides/neon-authorize.md Co-authored-by: Daniel <10074684+danieltprice@users.noreply.github.com> --- content/docs/guides/neon-authorize.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/guides/neon-authorize.md b/content/docs/guides/neon-authorize.md index fa4c2b5b87..29b6b37074 100644 --- a/content/docs/guides/neon-authorize.md +++ b/content/docs/guides/neon-authorize.md @@ -24,7 +24,7 @@ enableTableOfContents: true ## Authentication and authorization -When implementing user authentication in your application, third-party authentication providers like **Clerk**, **Auth0**, and others simplify the process of managing user identities, passwords, and security tokens. Once a user's identity is confirmed, the next step is **authorization** — controlling who can do what in your app based on their user type or role — for example, admins versus regular users. With Neon Authorize, you can handle authorization right in Postgres, in addition to, or to replace entirely, security at other layers. +When implementing user authentication in your application, third-party authentication providers like **Clerk**, **Auth0**, and others simplify the process of managing user identities, passwords, and security tokens. Once a user's identity is confirmed, the next step is **authorization** — controlling who can do what in your app based on their user type or role — for example, admins versus regular users. With Neon Authorize, you can manage authorization directly within Postgres, either alongside or as a complete replacement for security at other layers. ## How Neon Authorize works