OAuth client division scoping not restricting token access in multi-tenant BPO setup

What’s the correct way to scope an OAuth client to specific divisions for multi-tenant BPO access? We’re sending the division_id in the POST /api/v2/oauth/clients request, but the resulting token still grants access to all divisions. The JSON payload includes the correct division IDs, yet the token validation shows no restrictions. We’ve tried different scopes, but the issue persists. Any ideas on what we’re missing?