How about using a more generic concept of 'site'? That way it could apply to multi-company, multi-project, multi-location, multi-group etc...
On Apr 29, 8:30 pm, villas <villa...@gmail.com> wrote: > Hi All, > > I would like to use a single web2py app for many companies using a > single DB. For simplicity, I would prefer to use just one set of > tables too. > > My planned strategy is: > 1. Define a 'company' table to have the basic company info. > 2. Add a company_id field to all other tables to keep data separate. > 3. Set a 'global' company_id variable when users access the app (I > could for example set this according to the sub-domain used). > > I am concerned about auth. I know that I can add the company_id field > to auth_users, but what about groups? Is there any way of making > them work? > > Are there any other considerations. Maybe someone might have a few > tips? > > Thanks, D
