Skip to content

docs: clarify scope of JWT assistant restrictions #1338

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stephenvapiai merged 1 commit into from
Oct 16, 2026
Merged

docs: clarify scope of JWT assistant restrictions #1338

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions fern/customization/jwt-authentication.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Expand Down
Loading