From 6e8ffe180603aa7ba52981da8ac290d9ffac45d1 Mon Sep 17 00:00:00 2001 From: Chiranjeet Mishra Date: Fri, 16 Oct 2026 12:38:14 +0000 Subject: [PATCH] docs: clarify scope of JWT assistant restrictions allowedAssistantIds and allowTransientAssistant limit call creation, not reads. --- fern/customization/jwt-authentication.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/fern/customization/jwt-authentication.mdx b/fern/customization/jwt-authentication.mdx index 4c1fe0d25..49867fe1f 100644 --- a/fern/customization/jwt-authentication.mdx +++ b/fern/customization/jwt-authentication.mdx @@ -95,6 +95,7 @@ const token = generateJWT(payload, key, options); - **Payload**: The payload includes the `orgId` representing the organization ID and the `token` object with the scope of the token. - **Key**: The private key is used to sign the token, ensuring its authenticity. - **Options**: The `expiresIn` option specifies that the token will expire in 1 hour. +- **Restrictions**: `allowedAssistantIds` and `allowTransientAssistant` control which assistants a call can be created with. They do not limit which calls the token can read. - **Token Generation**: The `generateJWT` function (a placeholder for the actual JWT generation method) creates the token using the provided payload, key, and options. ## Usage (Making an Authenticated API Request)