Usecase evaluation
Hi, I’m exploring Zitadel and its multi-tenancy features, and I’d like to confirm if my use case aligns well with Zitadel’s capabilities before building a proof of concept (PoC). Here’s what I aim to achieve:
1. Custom Signup and Login UI: I need fully customized user interfaces for signup and login processes.
2. Tenant-Specific Login Context: When a user logs in, they should automatically be logged into the tenant they most recently accessed.
3. Tenant Switching: In the frontend, users should be able to switch between tenants. Upon switching, they should only see data associated with the current tenant.
• All tenant data would reside in a single database, but the application should enforce tenant isolation, ideally using a server-side JWT token with a tenantId.
4. Mapping Users to Employees/Persons: Users should be able to map to multiple employee/person entities.
• Administrators from different tenants should invite or assign users to their respective tenants.
Would Zitadel be a good fit for this use case, and do you have any recommendations for implementing this workflow effectively?
1. Custom Signup and Login UI: I need fully customized user interfaces for signup and login processes.
2. Tenant-Specific Login Context: When a user logs in, they should automatically be logged into the tenant they most recently accessed.
3. Tenant Switching: In the frontend, users should be able to switch between tenants. Upon switching, they should only see data associated with the current tenant.
• All tenant data would reside in a single database, but the application should enforce tenant isolation, ideally using a server-side JWT token with a tenantId.
4. Mapping Users to Employees/Persons: Users should be able to map to multiple employee/person entities.
• Administrators from different tenants should invite or assign users to their respective tenants.
Would Zitadel be a good fit for this use case, and do you have any recommendations for implementing this workflow effectively?
