Multi Tenant App

[jappi00]

Hello together,

I have to accomplish the following task and I want to get some feedback from you.

So I have to write a saas / multi tenant app. I have worked previously a little bit with filament and I love this piece of software so much! So I want to use it.

I have looked into the package https://tenancyforlaravel.com/ and I think it solves many of my problems. But I currently struggel to implement the whole topic.

I have to solve to topics:

1. Admin and Maintain Interface for the saas Topics. (Like: creating new tenants and so on)
2. The App itself. (I also want to use filament for this)

So there are multiple topics and questions in the moment.

1. How can I split the whole filament admin panels in two? What is considered best practice?
   (I have already tried to add a middleware for that but had some problems with that.
2. Is this achievable with filament?
3. Is there anything already done in this direction?

Thank you very much!

Greetings,
Jan-Phillip

[danharrin]

Why did you want to split the admin in 2? You should probably just hide/show resources and pages using permissions, right?

It is achievable, I've seen people use that package before by adding the middleware to the config/filament.php file

[thapaPrabhat]

Unfortunately no.
Instead i switched to spatie multitenancy package,
i think if you are using single db its better to write your own logic - which will help to simply things and also configurable to your need.

[maxroby]

Same @thapaPrabhat and @ayann issue here, @danharrin no way to get also central app working with stancl/tenancy?

[ayann]

@thapaPrabhat @maxroby I found a solution. It wasn't documented, the filament configuration should look like this :

    'middleware' => [
        'auth' => [
            Authenticate::class,
        ],
        'base' => [
            EncryptCookies::class,
            AddQueuedCookiesToResponse::class,
            StartSession::class,
            AuthenticateSession::class,
            ShareErrorsFromSession::class,
            VerifyCsrfToken::class,
            SubstituteBindings::class,
            DispatchServingFilamentEvent::class,
            MirrorConfigToSubpackages::class,
            InitializeTenancyByDomain::class,
            'universal',
        ],
    ],

Add the universal middleware

[maxroby]

Thanks @ayann , very useful! I think it should be documented.

[jmendozaf]

With this configuration, I'm able to get the Filament admin panel to work for all tenants as if they were the central domain. Even if the tenant or domain doesn't exist, it always logs in as if it were the central domain. That's not the expected behavior.
The frontend routes for the tenants do work, and I get an error saying the tenant doesn't exist if that's the case.
I think the problem lies in trying to have the Filament admin for both the central domain and the tenants. If I omit the universal middleware in config/filament.php, I get a message saying the tenant cannot be associated with the domain, as already mentioned.

What am I missing here?

[jmendozaf]

With this configuration, I'm able to get the Filament admin panel to work for all tenants as if they were the central domain. Even if the tenant or domain doesn't exist, it always logs in as if it were the central domain. That's not the expected behavior.
The frontend routes for the tenants do work, and I get an error saying the tenant doesn't exist if that's the case.
I think the problem lies in trying to have the Filament admin for both the central domain and the tenants. If I omit the universal middleware in config/filament.php, I get a message saying the tenant cannot be associated with the domain, as already mentioned.

What am I missing here?

[ytorbyk]

Hi @jappi00 @ayann @maxroby
Were you able to get working tenancyforlaravel.com with the Filament admin? If you yes, can you please, share what configuration you are using there?
Thanks!

[luckykenlin]

Hi @jappi00 @ayann @maxroby @jmendozaf
I still struggle with this integration. any help would be appreciate

[Arpityadav]

Hi! Did you figure it out? Appreciate the help.

[luckykenlin]

Hi @jappi00 @ayann @maxroby @jmendozaf
I still struggle with this integration. any help would be appreciate

[Arpityadav]

Hey! If you find a way to make it work, let me know

[coolsam726]

I have successfully setup Filament to work with tenancyforlaravel.com, but I am using Filament 3.x and Livewire 3.x. I have a central admin panel, a tenant's admin panel and a tenant's portal panel as separate filament panels. Let me know if you are interested in the configuration.

[jmendozaf]

Great. Can you share some workaround? Are you using different databases or schemas?

[jappi00]

FYI: maybe this helps: https://gist.github.com/nathandaly/44a83df5e3ea735eae91652c7a4894c9

[luckykenlin]

@coolsam726 Are you using separate databases? Can you share your configuration? thanks

[coolsam726]

Sorry for the delay.
Yes, I am using PostgreSQL so I preferred to use the option of using a single Database but different schemas, one schema per tenant. I am also using identification by subdomain.
For ease of reference, I have decided to share my repo publicly as a starter code for anyone interested. Here is the link.
https://github.com/savannabits/filament-tenancy-starter

Pay attention to the following:

1. I have three Filament Panel Providers:

• AdminPanelProvider is the Admin panel for the central admin
• TenantAdminPanelProvider is the admin panel for each tenant
• TenantPortalPanelProvider is the customer facing portal for each tenant.

2. For AdminPanelProvider, I am using the universal middleware as part of the middleware. Most importantly, I am also setting the Panel's domains as any of the Central Domains. This will identify the panel as a Central Panel.

3. For the Tenant Panels, I am using the universal, InitializeTenancyBySubdomain and PreventAccessFromCentralDomains middleware.

4. Check the TenancyServiceProvider and see that under prepareLivewireForTenancy() method I am setting a custom Livewire updateRoute which includes the universal and InitializeTenancyBySubdomain middleware in addition to the web middleware.

I don't believe I have left out any important info, but if you have any questions do let me know. Happy Coding!

[jappi00]

What do you mean by different schemas?

[jmendozaf]

One database, different pg schema for tenant

[jappi00]

Ah I wasn't aware what the schema system in Postgres really is.

[coolsam726]

I find it neater as opposed to spinning up an entire DB for each tenant. Either way, this will still work even if you were to use different pgsql or mysql databases for each tenant.