Skip to main content
When an admin user signs in to the Lobyco Admin Portal and does not see the expected sections or data, the token usually explains why. A role or a store claim is missing or wrong. This page is how to read the token. The admin user, or an administrator sitting with them, does it in the browser.
A token signs in as the user until it expires. Paste it only into a decoder you trust, and never share it.

​
The procedure

1

​
Capture the token

  • Open the browser’s developer tools, with F12 or Ctrl+Shift+I.
  • Open the Network tab and refresh the page.
  • Find a request to an API endpoint whose headers include Authorization: Bearer.
  • Copy the value after Bearer, the long string.
2

​
Decode it

  • Go to jwt.ms or another JWT decoder you trust.
  • Paste the token.
  • The decoder shows the payload, with every claim.
3

​
Check the claims

Confirm that the claims exist and carry the expected values. That is a roles entry for each section the user should see, and store_ids or chain_ids with the right ids.

​
Failure and edge cases

If the claims are not what you expect:
  • A claim is missing. The assignment did not reach the user, or the user signed in before it was made. Revisit the configuration steps, then sign out and in again.
  • A claim is there but the values are wrong. Compare the ids with the ones in Lobyco’s store master data, and send the corrected list.
Last modified on October 19, 2026