Add master model, default role templates, and applied-model resolver

Featurekamo-shared-library
Shipped
19 Aprili 2026, 19:25 UTC
Author
Kamo
Commit
7d620f9

Introduces the data layer for the new branch-type security model flow: - Organization gains nullable branchTypeID and masterModelID columns. - New RoleRightTemplateSettingType enum with 5 values (FORCE_GRANTED, GRANTED, NOT_SPECIFIED, FORCE_NUKE, NUKE) for template-layer settings. - New DefaultRoleType enum (ADMINISTRATOR, TEAM_MEMBER, MEMBER, DEFAULT) for the 4 role templates attached to each ChildOrgSecurityModel. - New entities **************** and **************** plus their repos, service, and DTOs. - AppliedModelResolverService resolves the model that governs a given org (branchType-inherited or master) and exposes force-rule lookups. - ChildOrgTemplateSeedingService seeds new child orgs' 3 system roles with GRANTED/NUKE values from the applied model's templates; force values stay in the template and are enforced at runtime. End-user OrgRoleRight continues to use the 3-value RoleRightSettingType — force values are strictly a template-layer concept.

All changes

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei