[Bug]: Permission Inheritance Edge Cases and Conflict Resolution

[asterixix]

Describe the bug
The current permission system doesn't address critical edge cases that will arise in hierarchical organization structures, such as permission conflicts between multiple inheritance paths, circular permission dependencies, and permission propagation boundaries. These issues could lead to security vulnerabilities, unexpected access denials, or excessive privilege escalation.

Steps to Reproduce

1. Create a complex organization hierarchy with multiple inheritance paths (e.g., a user belongs to both a parent and child organization)
2. Set conflicting permissions at different levels of the hierarchy
3. Observe inconsistent or unexpected permission resolution
4. Attempt to create circular permission dependencies
5. Notice lack of clear boundaries for permission propagation

Expected behavior
The permission system should handle complex hierarchical scenarios with predictable results:

• Clear conflict resolution rules when permissions come from multiple sources
• Prevention of circular permission dependencies
• Well-defined boundaries for permission inheritance
• Proper handling of permission revocation across the hierarchy
• Transparent permission resolution visibility for administrators

Screenshots
N/A - Security architecture issue

Desktop (please complete the following information):

• N/A - System-wide security issue

Additional context
This security issue must be addressed before the Advanced Association Management MVP release to prevent potential security breaches or inconsistent access control. The solution should include:

• Explicit rules for permission precedence (e.g., deny overrides grant)
• Permission inheritance directionality controls
• Cycle detection in permission inheritance paths
• UI components to visualize effective permissions
• Comprehensive permission audit logging