I'm trying to find a way to use the RBS module for a new application and haven't been able to figure out a way to meet the applications requirements. The application will be used to track multiple projects. New projects may be added to the application at run time. All projects will share the same permissions. Users need the ability to have different roles and permissions within each project and I need to be able to determine their permissions for a specific project at run time, not just the over all application.  Attached is a diagram of what I'm trying to accomplish. Any suggestions?

-Larry

Greg,

Thank you for the detailed post My need is slightly different in that I have a requirement for the user to be able to change projects (roles) as needed during the life of the application but I can see from your example how to get there wihout having to modify the RBS code.

-Larry

Larry,



Actually, I have the same need (it seems like). My users can change projects any time they want. The SetCurrentProject does the heavy lifting both when they login and if they change their project while running the application. I have a UI that shows all projects they are assigned to. Here they can either set that project as their "working" project (the one that will be in context) or as their default (so they can manage which project they are logged into when they login).



Also, because the permissions are set when the user logs in, they can actually open multiple instances, logged into different projects (not sure that's a good idea...but they can do it).



In any case, I hope that gets you thinking!



Have a great weekend all!