- Shipped
- November 13, 2026 at 12:30 AM UTC
- Author
- Kamo
- Commit
- 5cf9dc2
SecurityService now keeps a member's security level in step with their type and refuses anything else; the screens never offer what it would refuse: - Roles & Permissions: a team member is offered Team Member and up; a member's level is fixed at Member (the select only opens for one held out of step, to bring it back). A level held out of step still shows, never offered. One line under the control says the rule in the organization's own titles. - Profile: beside Make Team Member / Make Member, one line says what the change does to the access level. - Add Member / Add Team Member: only the levels the type allows; the helper says the rule. The SI hire form no longer offers Member (an SI is a team member). - app/lib/members/accessLevels: the rule's mirror (accessLevelAllowed, accessLevelAfterTypeChange, accessLevelOptions, accessLevelNamesFor), tested. Dictionary keys landed first (kamo-translation-dictionary 17c88cc6e).
