Browse Source
The manage flag in collection JSON was gated on atype == Manager, a raw comparison that now excludes Custom (4). A Custom member holding an explicit per-collection manage assignment (or full read/write access) would have lost the manage capability in /sync and the collection details endpoints - before this PR they were stored as Manager and matched. Compare by access level (>= Manager, which Manager and Custom share) instead, restoring the exact pre-PR behavior for migrated members. Admins/Owners are unaffected: they are caught by the earlier has_full_access / >= Admin arms.pull/7397/head
2 changed files with 7 additions and 6 deletions
Loading…
Reference in new issue