task-l.1
This commit is contained in:
@@ -365,6 +365,19 @@ Future:
|
||||
- define whether mixed-role users see own, team, or organization scope by default
|
||||
- keep exports aligned with the same scope policy once enforced
|
||||
|
||||
## After Task L.1
|
||||
|
||||
### Deprecated membership.businessRole for CRM authorization
|
||||
|
||||
Current:
|
||||
`memberships.businessRole` is now a compatibility fallback only. Primary CRM authorization moves to `crm_user_role_assignments`.
|
||||
|
||||
Future:
|
||||
|
||||
- remove CRM authorization dependence on `memberships.businessRole` entirely
|
||||
- update user-management flows to assign CRM roles through assignment rows instead of membership payloads
|
||||
- remove the deprecated column only after all CRM modules and admin flows have migrated
|
||||
|
||||
### Global project-party filter coverage
|
||||
|
||||
Task J adds a global `Project Party Role` filter in the dashboard UI, but the strongest enforcement today is in revenue analytics and export sections.
|
||||
|
||||
Reference in New Issue
Block a user