Sounds like you're heading down an unmaintable path there Each organisation can have it's own data, but for this to be served from one app that data must be defined within a common schema and feature/function set. If this is the case then it should be stored in a single relational database.
I'm currently developing a portal type website where organisations can register and add/manage their own articles/blogs/publications/ campaigns/events/vacancies etc. and many users can belong to an organisation. Other users can view and intereact with an organisations content without being able to manage it. This is fairly basic relational database logic and is simply managed by having a User and an Organisation model. A piece of content belongs to an Organisation and you know if another user is allowed to edit that content by checking if they belong to the same organisation. You can take this further by adding a UserGroup model which will allow certain users to manage Organisation level settings, but only allow other users to manage content. Taking this even further you add an OrganisationGroup model so you can have many different types of organisation and what features they can access in the application. HTH Paul. Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
