✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Greptile Overview

Greptile Summary

This PR systematically removes all namespace-related code from the backend codebase, transitioning to a sub-org architecture. The changes span database migrations, schemas, type definitions, and service layers.

Key Changes:

• Created idempotent database migration to drop scopeNamespaceId column from Membership table, namespaceId from Role and AdditionalPrivilege tables, and the entire Namespace table
• Removed AccessScope.Namespace enum value and associated type definitions from AccessScopeData
• Cleaned up all namespace-scoped query logic from DAL methods across membership-user, membership-identity, membership-group, and permission services
• Removed namespace factory implementations and registrations from all service layers (roles, additional-privileges, memberships, identity)
• Updated check constraint on Membership table to only allow project and organization scopes

Assessment:
The cleanup is thorough and consistent across the codebase. The migration is properly idempotent with existence checks before dropping columns/tables. No namespace references remain in the changed files.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The PR performs a clean, systematic removal of namespace functionality with proper idempotent migrations, consistent updates across all affected layers, and no breaking changes to external APIs (only internal type changes). The migration safely handles cases where columns may already be dropped, making it safe for re-execution.
• No files require special attention

Important Files Changed

_{Last reviewed commit: 6a2f9cb}