Apply template force rules and DEFAULT fallback to member rights resolution

Featurekamo-shared-library
Shipped
April 19, 2026 at 7:35 PM UTC
Author
Kamo
Commit
d446cf7

**************** now overlays the applied model's 4 default-role templates on top of the existing cascade (org roles → department → job title → member): - Role-type-specific FORCE_GRANTED/FORCE_NUKE wins over all cascade levels. The template is chosen by member type: team-member owners use ADMINISTRATOR, team-members use TEAM_MEMBER, plain members use MEMBER. - DEFAULT template FORCE values win over cascade when the role-type template has no force rule for that right (per Q7 precedence). - DEFAULT non-force values (GRANTED/NUKE) act as last-line-of-defense for rights that resolved to NOT_SPECIFIED after the full cascade. AppliedModelResolverService is injected as @Autowired(required=false) so existing unit-test wirings that only construct the two constructor-mandatory repositories continue to work, degrading to the legacy no-force-rules path.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing