<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Label this issue](https://contributors.gitlab.com/manage-issue?action=label&projectId=278964&issueIid=593056) </details> <!--IssueSummary end--> ## Overview Remediation steps identified following audit of Organizations compatibility. ## Related Issues * https://gitlab.com/gitlab-com/gl-infra/tenant-scale/organizations/organizations-feature-parity/-/work_items/11+ ## Description [Organizations: LFS Assessment](https://gitlab.com/gitlab-com/gl-infra/tenant-scale/organizations/organizations-feature-parity/-/work_items/11#note_3136123148) Git LFS 2.0 support has been identified as requiring investigation for potential data scoping and isolation gaps in the context of Organizations feature parity. ## Action Items * `lfs_objects` global deduplication has cross-org concerns. * Org context is not meaningfully set is LFS controllers: `set_current_organization` callback IS inherited from `ApplicationController` but resolves to the default/fallback organization (not the project's actual org) because LFS requests lack the params needed for proper org resolution.