The Jet Admin Token Based Auth integration lets your app authenticate users by validating a token issued by your own backend or identity system, driven by the same roles and permissions you already manage in Jet. Whether a parent system embeds the app for an already-logged-in user, or an automated process needs its own access, the whole sign-in flow runs off a token you control.

That covers what teams build with token-based auth first: embedding a Jet app inside another product so a user never sees a second login, and giving automated systems or partners a controlled way in. Because Jet reads fields out of the token itself, a person's role can be set by whatever system issued it, without a separate account to manage.

Key benefits

• No second login. Embed the app in another system and pass an already-authenticated session straight through.
• Works with any backend. Validate a token from whatever system already issues them, without adopting a specific protocol.
• Roles from the token. Set a user's permissions from fields already encoded in the token payload.
• Built for automation. Authenticate a service or partner system, not just a person.
• Session control. Sessions expire or revoke in step with the token that created them.

How to connect Jet Admin with Token Based Auth

1. In Jet Admin, open your app's authentication settings and choose Token Based Auth.
2. Configure how your backend signs and issues tokens, and share the verification key or secret with Jet.
3. Map the fields in your token payload to user attributes and roles inside your app.
4. Test by generating a token and confirming it signs a user in with the correct role.
5. Wire your parent system or backend to issue the token whenever a user should enter the app.