From f0a999bccd7d2dcbbc0e6798c752f7510d4b12e0 Mon Sep 17 00:00:00 2001 From: Rajat Singh <17253992+rajatcing@users.noreply.github.com> Date: Tue, 14 Jul 2026 16:16:13 +0200 Subject: [PATCH] docs: clarify human PAT limitation and link issue #10915 (#12412) ## Which Problems Are Solved There is currently a knowledge gap in the documentation where users are unclear on if or why human accounts cannot have Personal Access Tokens (PATs), which has led to confusion in community channels like Discord and GitHub. ## How the Problems Are Solved Clarified that human PATs are currently not supported in the Personal Access Token documentation and added a direct link to GitHub Issue #10915 so users can track and upvote this capability. ## Additional Changes None ## Additional Context None --------- Signed-off-by: Rajat Singh Co-authored-by: Rajat Singh --- .../integrate/service-accounts/personal-access-token.mdx | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/apps/docs/content/guides/integrate/service-accounts/personal-access-token.mdx b/apps/docs/content/guides/integrate/service-accounts/personal-access-token.mdx index 40040e46b..c2cb91811 100644 --- a/apps/docs/content/guides/integrate/service-accounts/personal-access-token.mdx +++ b/apps/docs/content/guides/integrate/service-accounts/personal-access-token.mdx @@ -5,7 +5,10 @@ sidebar_label: Personal access token authentication --- A Personal Access Token (PAT) is a ready-to-use token that can be used as an _Authorization_ header. -At the moment ZITADEL only allows PATs for service accounts. + + +Human PATs are currently not supported. PATs are available for service accounts only. + It is an alternative to the [private key JWT](./private-key-jwt) and [client credentials](./client-credentials). Read more about the different [authentication methods for service accounts](./authenticate-service-accounts).