abp-multi-tenancy

Multi-tenant data isolation in ABP is implemented by having entities implement IMultiTenant and relying on CurrentTenant for automatic data filtering by TenantId. This ensures users only access data belonging to their resolved tenant context.

CurrentTenant.Change() executes runtime tenant switching in ABP, allowing host operations or tenant-specific tasks to temporarily override the active tenant context. This enables cross-tenant data operations without permanently altering the global tenant resolution.

Cross-tenant data access in ABP is achieved using DataFilter.Disable(IMultiTenant) to temporarily bypass automatic tenant filtering. This allows host-level queries to retrieve data across all tenants before re-enabling the filter.

IMultiTenant is an interface in ABP that annotates entities for tenant-aware tagging and automatic TenantId handling. It marks domain entities so the framework can automatically apply data isolation filters based on the current tenant context.

Yes, ABP multi-tenancy applies across both host and tenant contexts, supporting entity tenant tagging and tenant resolution order. Host users can switch to specific tenant contexts using CurrentTenant.Change() for targeted operations.