I am working on a project which will be used by many Customers and these may have many branch offices, I am working on having one SQL2005 database for everybody, but of course the end users will only be able to see data from their Customer ID and Branch Office ID.

When login to the application I need to capture the Customer ID and Branch Office ID in the Login form, but how to filter the RBS data per Customer ID and Branch Office ID, so when the managers of one office creates an user and assign roles will only be able to do so for their records?

What would be the best approach to handle this with SF RBS?

Thanks!

Humm, very interesting, so you won't do the maintenance of structure yourself, it will be a responsibility of an update to be run from the customer application using DDT.

If I go this way and modify the SFSUsers table, will this be break by any future SF update?