Frontier model A

Trial · access-principals-admin

← access-principals-admin
Outcome
PASS22m
Reward
100.0%
Checks passed
26 / 26
Runtime
21m 32s
Harness
Cursor CLI
Task version
v3.1.3

Checks

CheckResultCreditWeight
baseline: the app serves and its database is migratedPASS100%1%
baseline: a signed-in person's session is recognizedPASS100%1%
migration: the three people on the old Settings list are adminsPASS100%5%
principals API: an admin creates email and domain principals and lists themPASS100%7%
principals API: values are stored normalized, one principal per email or domainPASS100%5%
principals API: an admin updates a principalPASS100%5%
principals API: an admin removes a principalPASS100%4%
principals API: invalid writes get a 400 and change nothingPASS100%6%
principals API: admins always hold every permissionPASS100%5%
principals API: only admins may use itPASS100%5%
access me: reports the caller's own principal, or nullPASS100%5%
resolution: an email principal overrides its domain'sPASS100%5%
resolution: role changes take effect on the next requestPASS100%5%
resolution: the old hardcoded list no longer grants SettingsPASS100%5%
settings APIs: company setup admits only adminsPASS100%5%
settings APIs: the integrations list and credential reads admit only adminsPASS100%5%
settings APIs: integration setup writes admit only adminsPASS100%5%
settings APIs: OAuth starts and callbacks admit only adminsPASS100%4%
settings APIs: the retention upload and diff admit only adminsPASS100%4%
settings pages: only admins can open themPASS100%5%
ui: Settings lists every principal on its Access pagePASS100%3%
ui: a principal added on the Access page starts with all companies, dashboards (view) and featuresPASS100%4%
ui: the header shows the Settings gear only to adminsPASS100%3%
preserve: dashboards and catalogs stay open to everyone signed inPASS100%0%
preserve: signed-out requests are turned away as beforePASS100%0%
preserve: an existing admin's Settings APIs answer as beforePASS100%0%