Yes, Permit.io supports environment-scoped member roles through its Authorization for Authorization (AuthZ for AuthZ) feature (1) . Members in Permit.io are the people who work alongside you within the Permit app and are governed by Permit's own access control system (2) . The platform uses a hierarchical structure: Workspace → Projects → Environments (1) (3) . Each environment is a silo of policy and data, usually representing a specific deployment like dev, prod, or staging (1) . The Application Plane components allow you to manage members and their access through various methods including UIs, GitOps workflows, and APIs (3) . While the specific mechanics of assigning environment-scoped roles to members aren't detailed in the available sources, the platform's architecture supports this through its meta-authorization capabilities (1) . You can manage members and their permissions through the Permit dashboard or API. For detailed guidance on configuring environment-specific member permissions, I'd recommend reaching out to support at help@permit.io or checking the workspace settings in your Permit dashboard where member management options are available.

To learn more, see the sources I considered: [[1] Concepts / Glossary](https://docs.permit.io/overview/glossary) [[2] Sync Users](https://docs.permit.io/how-to/sync-users) [[3] Modeling and Implementation Components](https://docs.permit.io/how-to/SDLC/modeling-implementation-components)