stronger statement for custom verifiers

torresmateo · torresmateo · commit 4c7df349357a · 2025-08-12T10:04:20.000-03:00
diff --git a/pages/home/auth-providers/asana.mdx b/pages/home/auth-providers/asana.mdx
@@ -29,7 +29,7 @@ If you choose to use Arcade's Asana auth, you don't need to configure anything.
 ## Use Your Own Asana App Credentials
 
 <Note>
-  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). This enables your app to verify the user's identity when they authorize a tool.
+  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). Without this, your end-users will not be able to use your app or agent in production.
 </Note>
 
 In a production environment, you will most likely want to use your own Asana app credentials. This way, your users will see your application's name requesting permission.
diff --git a/pages/home/auth-providers/atlassian.mdx b/pages/home/auth-providers/atlassian.mdx
@@ -22,7 +22,7 @@ This auth provider is used by:
 ## Configuring Atlassian auth
 
 <Note>
-  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). This enables your app to verify the user's identity when they authorize a tool.
+  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). Without this, your end-users will not be able to use your app or agent in production.
 </Note>
 
 In a production environment, you will most likely want to use your own Atlassian app credentials. This way, your users will see your application's name requesting permission.
diff --git a/pages/home/auth-providers/discord.mdx b/pages/home/auth-providers/discord.mdx
@@ -22,7 +22,7 @@ This auth provider is used by:
 ## Configuring Discord auth
 
 <Note>
-  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). This enables your app to verify the user's identity when they authorize a tool.
+  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). Without this, your end-users will not be able to use your app or agent in production.
 </Note>
 
 In a production environment, you will most likely want to use your own Discord app credentials. This way, your users will see your application's name requesting permission.
diff --git a/pages/home/auth-providers/dropbox.mdx b/pages/home/auth-providers/dropbox.mdx
@@ -22,7 +22,7 @@ This auth provider is used by:
 ## Configuring Dropbox auth
 
 <Note>
-  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). This enables your app to verify the user's identity when they authorize a tool.
+  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). Without this, your end-users will not be able to use your app or agent in production.
 </Note>
 
 In a production environment, you will most likely want to use your own Dropbox app credentials. This way, your users will see your application's name requesting permission.
diff --git a/pages/home/auth-providers/github.mdx b/pages/home/auth-providers/github.mdx
@@ -22,7 +22,7 @@ This auth provider is used by:
 ## Configuring GitHub auth
 
 <Note>
-  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). This enables your app to verify the user's identity when they authorize a tool.
+  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). Without this, your end-users will not be able to use your app or agent in production.
 </Note>
 
 In a production environment, you will most likely want to use your own GitHub app credentials. This way, your users will see your application's name requesting permission.
diff --git a/pages/home/auth-providers/google.mdx b/pages/home/auth-providers/google.mdx
@@ -23,7 +23,7 @@ This auth provider is used by:
 ## Configuring Google auth
 
 <Note>
-  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). This enables your app to verify the user's identity when they authorize a tool.
+  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). Without this, your end-users will not be able to use your app or agent in production.
 </Note>
 
 In a production environment, you will most likely want to use your own Google app credentials. This way, your users will see your application's name requesting permission.
diff --git a/pages/home/auth-providers/hubspot.mdx b/pages/home/auth-providers/hubspot.mdx
@@ -28,7 +28,7 @@ If you choose to use Arcade's Hubspot auth, you don't need to configure anything
 ## Use Your Own Hubspot App Credentials
 
 <Note>
-  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). This enables your app to verify the user's identity when they authorize a tool.
+  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). Without this, your end-users will not be able to use your app or agent in production.
 </Note>
 
 In a production environment, you will most likely want to use your own Hubspot app credentials. This way, your users will see your application's name requesting permission.
diff --git a/pages/home/auth-providers/linear.mdx b/pages/home/auth-providers/linear.mdx
@@ -16,7 +16,7 @@ This auth provider is used by:
 ## Configuring Linear auth
 
 <Note>
-  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). This enables your app to verify the user's identity when they authorize a tool.
+  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). Without this, your end-users will not be able to use your app or agent in production.
 </Note>
 
 In a production environment, you will most likely want to use your own Linear app credentials. This way, your users will see your application's name requesting permission.
diff --git a/pages/home/auth-providers/linkedin.mdx b/pages/home/auth-providers/linkedin.mdx
@@ -16,7 +16,7 @@ This auth provider is used by:
 ## Configuring LinkedIn auth
 
 <Note>
-  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). This enables your app to verify the user's identity when they authorize a tool.
+  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). Without this, your end-users will not be able to use your app or agent in production.
 </Note>
 
 In a production environment, you will most likely want to use your own LinkedIn app credentials. This way, your users will see your application's name requesting permission.
diff --git a/pages/home/auth-providers/microsoft.mdx b/pages/home/auth-providers/microsoft.mdx
@@ -22,7 +22,7 @@ This auth provider is used by:
 ## Configuring Microsoft auth
 
 <Note>
-  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). This enables your app to verify the user's identity when they authorize a tool.
+  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). Without this, your end-users will not be able to use your app or agent in production.
 </Note>
 
 In a production environment, you will most likely want to use your own Microsoft app credentials. This way, your users will see your application's name requesting permission.
diff --git a/pages/home/auth-providers/notion.mdx b/pages/home/auth-providers/notion.mdx
@@ -16,7 +16,7 @@ This auth provider is used by:
 ## Configuring Notion auth
 
 <Note>
-  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). This enables your app to verify the user's identity when they authorize a tool.
+  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). Without this, your end-users will not be able to use your app or agent in production.
 </Note>
 
 In a production environment, you will most likely want to use your own Notion app credentials. This way, your users will see your application's name requesting permission.
diff --git a/pages/home/auth-providers/reddit.mdx b/pages/home/auth-providers/reddit.mdx
@@ -22,7 +22,7 @@ This auth provider is used by:
 ## Configuring Reddit auth
 
 <Note>
-  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). This enables your app to verify the user's identity when they authorize a tool.
+  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). Without this, your end-users will not be able to use your app or agent in production.
 </Note>
 
 In a production environment, you will most likely want to use your own Reddit app credentials. This way, your users will see your application's name requesting permission.
diff --git a/pages/home/auth-providers/salesforce.mdx b/pages/home/auth-providers/salesforce.mdx
@@ -22,7 +22,7 @@ This auth provider is used by:
 ## Create a Salesforce app
 
 <Note>
-  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). This enables your app to verify the user's identity when they authorize a tool.
+  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). Without this, your end-users will not be able to use your app or agent in production.
 </Note>
 
 Salesforce has two types of apps: **Connected App** and **Lightning App**. For this guide, we'll create a **Connected App**. Make sure to follow the instructions below while you [create your Connected App](https://help.salesforce.com/s/articleView?id=xcloud.connected_app_create.htm&type=5).
diff --git a/pages/home/auth-providers/slack.mdx b/pages/home/auth-providers/slack.mdx
@@ -22,7 +22,7 @@ This auth provider is used by:
 ## Configuring Slack auth
 
 <Note>
-  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). This enables your app to verify the user's identity when they authorize a tool.
+  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). Without this, your end-users will not be able to use your app or agent in production.
 </Note>
 
 In a production environment, you will most likely want to use your own Slack app credentials. This way, your users will see your application's name requesting permission.
diff --git a/pages/home/auth-providers/spotify.mdx b/pages/home/auth-providers/spotify.mdx
@@ -22,7 +22,7 @@ This auth provider is used by:
 ## Configuring Spotify auth
 
 <Note>
-  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). This enables your app to verify the user's identity when they authorize a tool.
+  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). Without this, your end-users will not be able to use your app or agent in production.
 </Note>
 
 In a production environment, you will most likely want to use your own Spotify app credentials. This way, your users will see your application's name requesting permission.
diff --git a/pages/home/auth-providers/twitch.mdx b/pages/home/auth-providers/twitch.mdx
@@ -22,7 +22,7 @@ This auth provider is used by:
 ## Configuring Twitch auth
 
 <Note>
-  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). This enables your app to verify the user's identity when they authorize a tool.
+  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). Without this, your end-users will not be able to use your app or agent in production.
 </Note>
 
 In a production environment, you will most likely want to use your own Twitch app credentials. This way, your users will see your application's name requesting permission.
diff --git a/pages/home/auth-providers/x.mdx b/pages/home/auth-providers/x.mdx
@@ -23,7 +23,7 @@ This auth provider is used by:
 ## Configuring X auth
 
 <Note>
-  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). This enables your app to verify the user's identity when they authorize a tool.
+  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). Without this, your end-users will not be able to use your app or agent in production.
 </Note>
 
 In a production environment, you will most likely want to use your own X app credentials. This way, your users will see your application's name requesting permission.
diff --git a/pages/home/auth-providers/zendesk.mdx b/pages/home/auth-providers/zendesk.mdx
@@ -23,7 +23,7 @@ This auth provider is used by:
 ## Create a Zendesk app
 
 <Note>
-  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). This enables your app to verify the user's identity when they authorize a tool.
+  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). Without this, your end-users will not be able to use your app or agent in production.
 </Note>
 
 ### Additional guides
diff --git a/pages/home/auth-providers/zoom.mdx b/pages/home/auth-providers/zoom.mdx
@@ -22,7 +22,7 @@ This auth provider is used by:
 ## Configuring Zoom auth
 
 <Note>
-  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). This enables your app to verify the user's identity when they authorize a tool.
+  When using your own app credentials, make sure you configure your project to use a [custom user verifier](/home/auth/secure-auth-production#build-a-custom-user-verifier). Without this, your end-users will not be able to use your app or agent in production.
 </Note>
 
 In a production environment, you will most likely want to use your own Zoom app credentials. This way, your users will see your application's name requesting permission.
