The essens of a JWT is to provide Authentication, who is making the request. Who is stated in the subject field of the JWT.
When it comes to Roles and Authorisation, this is not stated by the specification at https://www.rfc-editor.org/rfc/rfc7519.html. But since the JWT can contain any information, you could add a custom claims. It's common to use JWT fields scopes for specifying authorisation and roles for specifying roles and group belongings.
It may be that your authenticator has some built in proprietary way of managing this, or you extend it with a custom plugin or filter that manages your access based on JWT content. It depends a bit on how you want these roles to be used. Should they be propagated as custom headers to downstream services that manages it locally, or do you want to control access already on an API Gateway level based on the users role?