permissions / roles with projects and users

[teklocust]

i have downloaded and installed the permissions patch found here: http://www.sugarcrm.com/forums/showt...4&page=1&pp=10 and it works like a charm. setting roles and restricting users to those individual roles is terrific. however, it does not have certain features that seem nearly essential to project management. wondering if there is A) something i am totally overlooking, or B) anyone knows a work-around solution.

with the current model, if i create a role, assign users to that role, restrict the permissions within that role so that only those users can see each other's work, contacts, tasks, etc., but no one else can - it works great. HOWEVER what happens beyond that?

effectively, the role management is really more like "team" management. lets assume that i have 3 "teams" within my company. management, assistant management, and employees. within those teams, i have multiple kinds of managers (department 1, department 2, department 3), their respective assistant managers and workers. i obviously want management to have more control than assistants who have more control than workers. but what if i don't want my three managers to see each other's projects (tasks) or contacts?

i am wanting to know how to create project (task), assign users to that project and expect that each user on that project can see the data for that project and that project only. at the same time, retaining the global "roles" restricting the tabs and other content.

for example, if i had three teams of sales. each team would want their leads to be hidden from the other team, but would want those same leads shown to each other. (i can do this with role) - BUT within those three teams, i have various projects assigned to only certain people. i want those people to be able to share the "global" lead pool, while also seeing leads specific for their own projects.

if i were able to assign multiple roles to each individual, this would almost be accomplished, but not quite.

ROLE 1 - team leader
- leader A
PROJECT 1
- worker A
- worker B
- worker C
PROJECT 2
- worker B
- worker D
- worker E
- leader B
PROJECT 3
- worker A
- worker F
- worker G
PROJECT 4
- worker B
- worker D
- worker E

in this example, leader A would be able to see everything in project 1 and 2. leader B, everything from projects 3 and 4. worker A would be able to see everything from project 1 and project 3, even though they are with different leaders. leader B would NOT be able to see worker A's info from project 1, even though worker A is assigned to him.

all at the same time, each one of these users could have information stored that would be confidential and seen by ONLY them, if they wish.


i hope that this is not too confusing or complicated. i tried to simplify it as much as possible.

please let me know feed back. thank you for your time and response!

[sromanski]

This won't help you but it's something all SugarCRM developers should be aware of:

ZDNet Article

Simon