If I understand the scenario, you simply want all teams to be using the same version of Rulestream but don't want to mix their applications on the same set of Rules/Projects/Component DB - i.e. have a separate set of these DBs for each team.
I don't see why it should not be possible - all you need to ensure is that those DBs are at the same version as the Rulestream client.
I also don't see why you shouldn't have all the applications (for different teams) in the same DB - this is useful if you see a member of a team wanting to launch an application that is used by another team without having to log out of Rulestream and changing profile (a profile is tied to a set of Rules/Projects/Component DBs.
On the hand, if you know that members of a team don't usually open applications developed by other team, then keeping them separate sounds like a clean setup. This setup would also remove naming constraints for part families - same partfamily names can be used if they are on different DBs (vs. if you have all teams using the same DB, you will run into issues if you use same partfamily names in certain situations).
Dharmesh Sanghavi
