Admin panel application.

[BartMommens]

Hello all,

Currently i'm having trouble trying to figure out how to do the Admin panel for a Multi-tenancy (multi db) Saas Application.

So i'm using Laravel Fortify and Sanctum for all my tenants apps, but the downside of this package is that it's only able to use one guard being 'web' guard. All tenants have shared roles and permissions ( stored in Landlord database).

So currenly i'm thinking about creating a different laravel project to manage the landlord database. In this App i'll be using a CRUD for tenant roles / permissions. This App may on a separate domain with it's own users (landlord admins) and so on...

But i'm not sure if this is a good approach, to have a separate application to manage the landlord database. It will have a few 'shared' models between the projects such as roles and permissions, and should be able to use the same app key as the multi tenant application.

Is it a good approach to create a separate application or not at all? I think i would build a separate laravel package to keep the models synced. My biggest problem is actually that i'm afraid of doing something that isn't concerned as a good practice. And since most guides, tutorials and docs suggest running the Admin app inside the same project i'm facing a dilemma.

The biggest advange of the Separate admin application (my opinion) would be that i could run a copy of my multi tenant system on a separate server (for example a clients server's with his own tenants) and then i can just switch landlord database in the admin panel and manage those apps separatly.

What do you think of my idea? Maybe this topic can also help other users facing this dilemma 😊

Thanks for your feedback, any feedback is welcome.

Looking forward to your replies.

Best regards,
Bart

[shinanmhd]

Hi @BartMommens
I am faced with the same problem.
Could you please let me know what solution you implemented?
thank you

[BartMommens]

Hey @shinanmhd,

Currently I parked this 'problem'. Since the lack of time I just add and configure tenants with tinker. The only downside is that everything is done via command line. Over the months / year I've bundled most commands so it takes almost no effort.

Building a separate admin application would mean you need to keep 2 applications up to date, and since it would have a minimal usage it would be more work maintaining admin application than actually doing the work via tinker.

So far I don't regret the decision to focus on the main app. Tinker is a pretty handy tool.

Sorry I can't help you out further on this topic.

Kind regards,
Bart