ShotGrid API and Permission Group Interoperability

Entity Access Control via API

ShotGrid manages data access through a group-based permission system where read, write, and delete rights are assigned per entity. When integrating external tools via the API, the system must reconcile permissions assigned to the authenticated user's primary group with any inherited or override permissions applied to specific entities.

There is uncertainty regarding the precedence logic when a user belongs to multiple groups with conflicting permission levels for the same entity, specifically when an override is applied at the individual entity level versus a broad group-level restriction.

• How does the ShotGrid API resolve conflicts between inherited group permissions and entity-specific overrides?
• Does the API prioritize the most restrictive permission or the most permissive when multiple group memberships overlap?