request_tenant wouldn't fulfill all your requirements, it should work in conjuntion with permissions.
On Thursday, December 1, 2011, Vinicius Assef wrote: > I've looked for it and I'm using them. > > My doubt is about multi-tenancy, but I think it won't help me in this > case, because I have users with full access, who don't can count on > filtered accesses. > > -- > Vinicius Assef. > > > On Thu, Dec 1, 2011 at 12:44 PM, Nik Go <nikolai...@gmail.com<javascript:;>> > wrote: > > look for roles, groups and memberships in the book > > > > On Thursday, December 1, 2011, Vinicius Assef wrote: > >> > >> I think I'll use web2py multi-tenancy, but I have some doubts: > >> > >> I have different user profiles in my app: > >> a) customer: can view/edit only it's own data. > >> b) seller: can view/edit its own data and his customers' data, too. > >> c) back-office: can view/edit all sellers' data and any customer's > >> data, but not financial data. > >> d) financial-user: can view/edit anybody's financial data. > >> e) super-user: can view/edit anything, anytime. This is the allmighty > >> person. > >> > >> > >> If I use the multi-tenancy feature, how can I implement profiles c, d > and > >> e? > >> As I read in the book, multi-tenancy web2py implements is just > >> filtering data by request_tenant.default field. > >> > >> -- > >> Vinicius Assef. > > >
