Open Closed

Disable Multi Tenancy #10673


User avatar
0
Pooja@hotmail.com.au created

Hello,

If I want to create an application for B2C and set "options.IsEnabled = false", will it remove UI for SaaS, Tenant & Edition? Also, will it remove from WebApi and DB?

Once I deliver the project to the client, the client will have full access to the DB & Host side, and I don't want them to enable it somehow.

If there is any other recommendation to remove the Saas module, please feel free to share, such as removing Saas module completely?

Thanks, Pooja

Markdown supported.
Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

2 Answer(s)
  • User Avatar
    0
    AI-Bot created
    Support Team ABP Agent
    • Configure<AbpMultiTenancyOptions>(o => o.IsEnabled = false) only disables ABP’s multi-tenancy behavior at runtime (tenant resolution, multi-tenancy checks/filters, etc.). It does not automatically uninstall modules, and it does not remove:

      • SaaS/Tenant/Edition UI pages & menus (those come from the SaaS module and/or your menu configuration),
      • Web API endpoints provided by those modules,
      • DB tables created by those modules (already created tables remain unless you remove the module and regenerate migrations).
    • If your goal is “B2C, and the customer must not be able to turn it into SaaS later”, the recommendation is to remove the SaaS module completely from the solution:

      1. Remove SaaS module NuGet packages (and any SaaS-related module dependencies) from your .csproj files.
      2. Remove SaaS module DependsOn(...) entries from your module classes (Web/HttpApi/EntityFrameworkCore/etc.).
      3. Remove SaaS EF Core model configuration from your DbContext (builder.ConfigureSaas();) if it exists.
      4. Remove SaaS menu contributions (SaaS menu group, Tenant/Edition items) if you added any custom ones.
      5. Create a new EF Core migration after removing the module so the migration will drop the SaaS tables (or, if you prefer, you can manually remove them, but migrations are the safer/trackable way).
      6. Rebuild/run: the UI and endpoints won’t exist because the module is not in the app anymore, and DB schema will be updated by migrations.
    • Also note: if the client has host admin + direct DB access, they can always change data in any table (including permissions/features/settings). The only robust way to prevent SaaS capabilities from being enabled is not shipping the SaaS module/code at all (steps above). Disabling multi-tenancy via IsEnabled=false doesn’t provide that guarantee.

    (Links checked)

    • https://abp.io/docs/latest/framework/architecture/multi-tenancy/
    • https://abp.io/support/questions/1795

    This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    Pooja@hotmail.com.au created

    AI suggestion to remove Saas is perfect and suitable for our project

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
Boost Your Development
ABP Live Training
Packages
See Trainings
Mastering ABP Framework Book
The Official Guide
Mastering
ABP Framework
Learn More
Mastering ABP Framework Book
Made with ❤️ on ABP v10.8.0-preview. Updated on September 16, 2026, 14:50
1
ABP Assistant
🔐 You need to be logged in to use the chatbot. Please log in first.