What is a JWT (JSON Web Token)? A guide for PMs
A JWT (JSON Web Token) is a compact token that carries signed statements about a user, called claims. It has three encoded parts separated by dots: a header, a payload (user ID, role, expiry time) and a signature. A server that receives the token checks the signature to confirm nobody altered it, without having to look up a session store.
Definition written by Alex Dionisio, Senior Product Manager. Updated November 13, 2026.
Why it matters for a PM
Many products use JWTs to keep users signed in or to authenticate calls between services. That design leads to concrete product choices: how long a token stays valid, how to sign someone out remotely, and what happens when a user's permissions change while they are still logged in. A PM who understands these constraints raises the right questions before an incident raises them instead.
Example
In a team management app, an admin removes a former employee's access. Because that person's token is valid for an hour, they could still act during that window. The team shortens the access token lifetime to a few minutes and adds a revocation list for refresh tokens.
Key points
- The payload is only Base64-encoded: anyone can read it, so it must never hold secrets.
- The signature guarantees the token's integrity, not its confidentiality.
- A short-lived access token paired with a longer refresh token is a common compromise.
- Revoking a JWT before it expires needs an extra mechanism, because the server does not track every token it issued.
Common mistakes
- Putting personal or sensitive data in the payload on the assumption that it is encrypted.
- Issuing tokens valid for days with no way to revoke them.
- Trusting the roles written in the token for critical actions without checking them again.
Go further with Module
The courses and lessons that cover this concept:
Guide on this topic
- MCP vs API: the difference
When to expose an API, an MCP server or both, and what it changes for your product.