- Ya
- 2 Septemba 2026, 23:29 UTC
- Mwandishi
- Kamo
- Ahadi ya
- b72eae1
REPORTED: "I am also an admin and I don't see the new Sales Scripts tab under /settings/features/crm." Correct, and it was invisible to EVERY organization, not just this one. Root cause, traced rather than guessed. The tab gates on MANAGE_SALES_SCRIPTS. That right is deliberately absent from **************** — seeding it from an existing right would hand an organization's sales wording to whoever happened to hold whatever it was seeded from — so it is granted to NOBODY when it deploys. Gating solely on it hid the feature from precisely the person who would grant it, and there is no other way to grant it. The database agrees: org_role_rights holds zero rows for 300/301 and its highest right_type is still 299. This is a documented shape and I missed it. app/settings/account/page.tsx carries the same owner branch for Receivables, with a comment saying exactly this would happen. Now mirrored in four places that must agree — the CRM settings page, the settings menu, the settings landing cards, and (already pushed) SalesScriptController, since a tab that opened onto a 403 would be no better than a hidden one. NavGateContext gains isOrganizationOwner as a REQUIRED field, not optional: an omitted field would default to "not the owner" silently, which is the exact failure this exists to prevent. TypeScript then named all eleven construction sites rather than leaving me to find them. salesScriptsOwnerGate.test.ts pins the regression — an owner holding no rights at all must see both links. Note this fix is necessary but not sufficient on its own: SecurityService is still running a pre-shared-lib image, so RoleRightsSyncService has never seen rights 300/301 and no role can grant them yet. A rebuild is dispatched.