- Ya
- 3 Septemba 2026, 22:01 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 3f2ac78
MANAGE_JOB_POSTINGS and VIEW_JOB_LISTINGS are inserted as NOT_SPECIFIED like every new right, so without a seed the /hr/careers tab and the member Careers tab would ship invisible to every organization on the platform — including to the one person who could grant them. Both reproduce MANAGE_TRAINING's group: whoever already authors HR content sees the feature on the deploy that introduces it. VIEW_JOB_LISTINGS seeds from the same narrow group, and that is deliberate rather than an oversight. The internal board is meant for the whole staff, but there is no "everybody" to seed from, and a deploy that granted a new right to every member of every organization would be making a decision that is not a deploy's to make. It lands with HR, who widen it through a security role. What the seed guarantees is that somebody can see the feature exists. A scheduler holding only VIEW_SCHEDULES gets neither. They could reach Attendance and never any authoring surface, and careers is authoring — seeding wider than the old gate is handing out access, not preserving it.