Tyring to design a membership system for multiple company accounts, each with multiple users (as opposed to just unique users ala default ASP.NET Membership provider).
Seems like a very common scenario, but can find NO guidance. How is this usually implemented? ARGH!!
Company Account A [CompanyID]; User 1 [UserID]; User 2 [UserID];...
Company Account B [CompanyID]; User 3 [UserID]; User 4 [UserID];...
Can I use ASP.NET 2.0 Membership Provider (as is or modified?), or do I need to roll my own from scratch?
Planning SaaS application in ASP.NET 4.x Web Forms, C#, SQL Server 2008/12, shared DB + shared schema. Customers will sign-up for Accounts (auto-provisioned), then setup their own users manually (or approve sign-ups).
I believe I understand the DB aspect (CompanyID + UserID), just not the Membership provider. I plan to use email address as UserName (always unique), which will then identify which Company user belongs to, so no messing around with URLs needed.
Any guidance greatly appreciated!