Skip to content

Commit 50c021d

Browse files
Update clickup.mdx
Co-authored-by: Mateo Torres <mateo@arcade.dev>
1 parent 2e03828 commit 50c021d

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

pages/home/auth-providers/clickup.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,9 @@ This auth provider is used by:
1414
- Or, your [custom tools](#using-clickup-auth-in-custom-tools) that need to call ClickUp APIs
1515

1616
## Configuring ClickUp auth
17-
17+
<Note>
18+
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.
19+
</Note>
1820
In a production environment, you will most likely want to use your own ClickUp app credentials. This way, your users will see your application's name requesting permission.
1921

2022
You can use your own ClickUp credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.

0 commit comments

Comments
 (0)