@D > Your idea seems like a workable alternative, but still you seem to be > re-inventing the auth group system which is what I was trying to > avoid.
Web2py's auth system simply didn't work for me, therefore, I came up with the 'function' table as an alternative. I am building this app for a psychologist who wants to be able to enable and disable functions the easiest way. The way I solved the problem, he is presented with a form in which he just checks or un-checks check boxes when he wants to provide users with functionality. @Anthony > Annet, is this a publicly available website/service? Not yet, it's still experimental, and requires a lot of re-work every now and than. As soon as it's publicly available I'll let you know. However, it's a site targeting Dutch users, so I am not sure it's useful for none Dutch speakers. As far as a single database is concerned, I am not an expert when it comes to database administration and performance and scalability issues (that's next on my to 'learn list', but at the moment a single database allows me to for instance to present users with a 'global' event list based on companies' 'local' event lists or to enable users to globally query timetables for 'local' classes. Furthermore, I don't know if a single database on a database server performs less well than multiple database on the same database server. Kind regards, Annet.
