Summary by CodeRabbit

• Bug Fixes
  • Standardized tenant scoping by making organization fields server-managed (read-only) across multiple models, with consistent nullable foreign-key behavior where applicable.
  • Updated admin views to keep organization read-only for organization rate limits.
• Tests
  • Added coverage to ensure API/DRF serializers do not accept organization from client input and validate payloads correctly for organization-scoped models.

Walkthrough

organization ForeignKey fields across 14+ Django apps and DefaultOrganizationMixin are marked editable=False to prevent client/form editing. An anchor migration in account_v2 is introduced, and each affected app adds a chained AlterField migration. A new test verifies that AdapterInstanceSerializer exposes organization as read-only.

Changes

Server-managed organization FK enforcement

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Client sends create request\nno organization in payload] --> B[DRF ModelSerializer.is_valid]
    B --> C{organization\neditable?}
    C -- "Before fix\n(editable=True)" --> D[DRF builds UniqueTogetherValidator\nrequiring organization field]
    D --> E["400: organization\nThis field is required"]
    C -- "After fix\n(editable=False)" --> F[DRF marks organization read_only\nDrops UniqueTogetherValidator]
    F --> G[Validation passes]
    G --> H[serializer.save calls model.save]
    H --> I[DefaultOrganizationMixin.save\nsets organization from UserContext]
    I --> J[Record persisted with\ncorrect tenant scoping]

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[Client sends create request\nno organization in payload] --> B[DRF ModelSerializer.is_valid]
    B --> C{organization\neditable?}
    C -- "Before fix\n(editable=True)" --> D[DRF builds UniqueTogetherValidator\nrequiring organization field]
    D --> E["400: organization\nThis field is required"]
    C -- "After fix\n(editable=False)" --> F[DRF marks organization read_only\nDrops UniqueTogetherValidator]
    F --> G[Validation passes]
    G --> H[serializer.save calls model.save]
    H --> I[DefaultOrganizationMixin.save\nsets organization from UserContext]
    I --> J[Record persisted with\ncorrect tenant scoping]

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
backend/adapter_processor_v2/tests/test_org_editable.py:33-46
**Regression test doesn't cover all migrated models**

Eight models received `AlterField` migrations in this PR but are absent from `ORG_SCOPED_MODELS`: `dashboard_metrics.EventMetricsDaily/Hourly/Monthly`, `platform_api.PlatformApiKey`, `prompt_studio_core_v2.CustomTool`, `prompt_studio_registry_v2.PromptStudioRegistry`, `tenant_account_v2.OrganizationMember`, and `usage_v2.Usage`. Since they all inherit from `DefaultOrganizationMixin` the invariant holds today, but if a future developer overrides `organization` on one of these models without `editable=False`, the regression guard won't catch it. Adding the missing entries to the parametrize list would close that gap.

_{Reviews (2): Last reviewed commit: "Merge branch 'main' into fix/org-editabl..." | Re-trigger Greptile}

Unstract test results

Per-group results

Critical paths

⚠️ Critical paths not yet covered

• auth-login — User can log in and obtain a session cookie. (entry: POST /api/v1/auth/login; declared coverage: no groups declared)
• adapter-register-llm — Register and validate an LLM adapter. (entry: POST /api/v1/adapter/; declared coverage: no groups declared)
• workflow-create-execute — Create a workflow, configure source+destination, execute, poll, fetch result. (entry: POST /api/v1/workflow/{id}/execute/; declared coverage: e2e-workflow)
• api-deployment-run — Deploy a workflow as an API, POST a document, receive structured JSON. (entry: POST /deployment/api/{org}/{name}/; declared coverage: e2e-api-deployment)
• prompt-studio-fetch-response — Prompt Studio: create project, add prompt, run single-pass, get response. (entry: POST /api/v1/prompt-studio/prompt-studio-tool/{id}/fetch_response/; declared coverage: e2e-prompt-studio)
• pipeline-etl-execute — Run an ETL pipeline from source connector to destination. (entry: POST /api/v1/pipeline/{id}/execute/; declared coverage: no groups declared)
• usage-token-tracking — Per-execution token usage is recorded and retrievable. (entry: GET /api/v1/usage/get_token_usage/; declared coverage: no groups declared)
• workflow-execution-fan-out — Multi-file workflow execution fans out to file-processing workers and rejoins. (entry: internal: backend → rabbitmq → workers/file_processing; declared coverage: no groups declared)
• callback-result-delivery — Async results are posted back via the callback worker. (entry: internal: workers/callback → backend /internal endpoints; declared coverage: no groups declared)

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud