---
title: "Access Tokens (JWT)"
slug: "jwt-access-token"
updated: 2026-01-30T11:29:54Z
published: 2026-01-30T11:29:54Z
canonical: "help.csgi.com/jwt-access-token"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.csgi.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Access Tokens (JWT)

Access tokens are used internally by Bill Explainer to **securely validate access to the Explainer experience**.

They ensure that each customer sees **only their own personalized billing information** and that access is time-bound and protected.

---

## What access tokens do

Access tokens help Bill Explainer:

- Verify the identity and context of a request
- Protect customer billing data
- Ensure secure delivery of personalized content
- Support scalable and reliable access control

These tokens are part of the platform’s underlying security model.

---

## How access tokens are used

Access tokens are:

- Generated and validated automatically
- Used as part of secure access flows
- Managed by the platform, not by end users

They are not exposed to customers and typically require no action from client administrators.

---

## What client administrators need to know

For most deployments:

- No configuration or maintenance is required
- Access tokens are handled as part of the standard Bill Explainer setup
- Any exceptions or special requirements are addressed during onboarding

This information is provided for **transparency and awareness**, not for day-to-day management.

---

## Related topics

- [**Tokenized Access Links**](/cx/docs/tokenized-access-link)
- [**Initial setup and configuration**](/cx/docs/initial-setup-and-configuration)