- Shipped
- August 21, 2026 at 1:58 PM UTC
- Author
- Kamo
- Commit
- 16e8393
sameCollection demanded an exact assoc_object_id match in both directions, which made every binder in My Docs refuse every document My Docs was showing it. The grid does not filter that way: ImagingController.listDocuments skips the object-id test entirely when the request oid is empty, and /doc/manager always mounts the empty scope — while POST /api/docs/new stores the member id on the document and only /doc/manager uploads store "". So the binder was rejecting rows its own grid had just listed. The Selected Docs binder turned that from a rarely-hit edge into the whole feature: "3 of 3 newly selected document(s) could not be added". An unscoped binder now takes anything in its collection, matching the list it sits next to. The relaxation is one-directional — a binder scoped to a real object id still demands an exact match, because a DocManager mounted on one lists only that record's documents. Nothing is granted: assocType still gates, the per-party vault/loan refusal is untouched, and every document still resolves through ImageService, which enforces org and clearance. The scratch response now carries the count it could not add, because a binder silently holding fewer documents than the member checked reads as broken.