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!
What about making a related table to SFSUsers which holds information on Branch and Customer. Relate it one-to-one to SFSUsers primary key. Make a form in your application to maintain these data, then you are clear of future SF updates.
/Teddy
That may work, even though still I would need to modify the security form, so when Customer X creates users, my related table would be updated with the Customer ID and Branch ID info, or at least just the Customer ID.