For this purpose the generic approach is to have an API Gateway layer i.e. a Microservice only which has to take care of following things -

1. Do the task of authentication and generate a JWT token for the user
2. Read the roles and responsibilities after decoding the token, every time a call is made by a user for authorization purpose
3. Once you get the role of user from here, you can create routes in API Gateway for each service to check like whether he can access that functionality or not, in your case let's say user's role is "warehouse Admin" and he is eligible to take care of product and related info, then he can access product service, for this you can do a role check at API Gateway layer only, when the request comes to access from routes related to product service (let's say its "/products" ). Hence you are maintaining the authenticity checks at API Gateway layer only.
4. Or in the otherwise case if you want to maintain an account service as well to take care of doing the authentication and authorization, then you have to direct the calls from API Gateway to account service and route the request to related backend services, once the response arrives from account service carrying the roles and permissions for the user.