[Anthill-pro] Troubles with users doing builds

[Curtis Yanko]

My guess is that out-of-the-box that is the only role that has 
comprehensive permission's across the board.

Thus far, I have defined a User role and then gone through the resources 
to ensure a User can access most everything. I use LDAP (Active Directory) 
for Authentication and have it create my new user with this role along 
with capturing name and email info. I then also create two more roles for 
each project that I take on, one for team members <proj>_user and another 
for a release coordinator role <proj>_rc. I use these roles on Project (to 
filter the list presented) and on workflows (so only a release coordinator 
can trigger a "QA Deploy" workflow (which gets it's on stamp and roles up 
change logs.

This way a developer can be on multiple teams yet have different levels of 
authority on each one (projects may also map to a specific release but I 
have to confess I am struggle with how to support a team using a 
overlapping releases pattern and may need to make adjustments).

Anyone else come up with a creative solution in this area?

- Curtis Yanko
UnitedHealth Group IT
Mail Route: CT028-06SA
Internet email: curt_yanko at uhc.com
Office 860.702.9059
Cell 860.729.8171


This e-mail, including attachments, may include confidential and/or 
proprietary information, and may be used only by the person or entity to 
which it is addressed. If the reader of this e-mail is not the intended 
recipient or his or her authorized agent, the reader is hereby notified 
that any dissemination, distribution or copying of this e-mail is 
prohibited. If you have received this e-mail in error, please notify the 
sender by replying to this message and delete this e-mail immediately.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20070725/5bdff8de/attachment.htm