Database design : multiple category of users login into same system In our new system we have three type of people 


Business owner
Assistant of business owner
Staff (a skilled employee)


I am having following entity 


[Business] - include detail about business owner
[Assistant] - detail about the assistant
[Staff] - detail about the staff


Business rules 


There will be only one business owner for a given business, means there can be only one login for business owner. He is like a super user for his business.
Business owner can be staff as well.
A single business can contains more then one staff and each staff have different kind of rights/permissions can be configured by business owner.
Only one assistant allowed per business and rights/permissions can be configured by business owner. 


What would be right way to go?

Any help/suggestion appreciated!!!
The standard way to model permissions for a system is through Role-Based Security.  The typical model looks something like this:



The way it works is you have three tangible things: Users, Allowable Actions (the access that is being controlled) and Roles.  Roles are groups of both users and allowable actions, therefore there are two intersection tables which record the people in each role and the actions that role permits.  Some people include additional information in the ROLE MEMBERSHIP and PERMISSION intersection tables, like when the record was created and by whom.  Some people keep that kind of audit log information in a separate table.

In this model every type of user is stored in your USER table.  The rules that you have stated for cardinality of users (one owner, one assistant) are frankly very brittle if you ask me.  I don't like to cast rules into my data model which are almost certainly going to change.  It seems unreasonable to me that a business will use your system if it doesn't allow a manager to delegate their responsibilities for when they are off duty, on vacation or away from the business.  Your cardinality rules should be enforced in application logic or with additional tables related to USER if you really feel they need to be in the data model somehow.