Base solution for your next web application
Ends in:
01 DAYS
01 HRS
01 MIN
01 SEC

Activities of "pnocera"

Hi,

I just purchased ASP.NET Zero, which I consider a nice effort for its patterns and practices implementation. I've been thinking a lot wether I'll use it or not for my project. There's one thing which will probably make me take another way, but is quite fundamental to my sense, and it's in the title :)

I would rather create a tenant for each user as soon as he registers. Then any user could reference another user and give him a role in his tenant which would provide access to some resources ( features or permissions, which btw I would gather in a single parent/child entity ). This would allow a single access, a single account for one given email. The user logs-in, then chooses which tenant he is interacting with. The permissions would be defined by the subscription of the tenant whithin which context the user is acting, and the role he's been provided in this tenant.

The high level db schema would be something ike that :

I know it's a big impact. I'd probably would have to fork the boilerplate. Or restart from scratch with a nodejs backend...

What guys do you think ?

Showing 1 to 1 of 1 entries