## Problem Statement All Organization data/functionality across GitLab should be [isolated](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/organization/isolation/). This means the data/features must not cross Organization boundaries. For example: an issue in a Project within `Organization A` cannot be related to an issue in a Project in `Organization B`. This epic refers to **enforcing** the isolation previously established, eg. once all tables have a sharding key, we will prevent newly-inserted data from crossing an Organization boundary. ## Exit criteria * Organization Isolation is enforced for all workloads behind a feature flag (eg. to roll out to specific customers on a new cell) * Newly-inserted data cannot cross an Organization boundary * All existing sharding key columns on all Cell-local tables have been validated to confirm they can be safely assumed to be sharding keys ## DRI @rutgerwessels <!--STATUS NOTE START--> <!--STATUS NOTE END-->