Carry the per-member-type home-screen defaults

FeatureSecurityService
Shipped
August 28, 2026 at 7:51 PM UTC
Author
Kamo
Commit
7774595

Read on POST/PUT /security-models and PUT /master-model, and emitted from /applied-model's settings so the shell can decide where a member lands on "/". A separate applyHomeScreenDefaults call rather than three more positional arguments on a service method that already takes fifteen. Absent keys are left alone rather than reset, so a client that posts a security model without knowing about this field cannot silently hand every member of the model their launchpad back — or take it away. /applied-model normalizes on the way out as well as in. REQUIRES_CHILD_ORG_ OWNERSHIP withholds a home screen, so a null column on a row written before this shipped, or anything unrecognised, reads as the launchpad. The client's own fallback is the same value, so the two cannot disagree.

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