| || |
Understanding TDAdmin role ??
Just wanted to know the clear understanding of TDadminrole. I need to set up the Test process in my company using TD.
So how exactly I start giving diff permissions(dev, pm, viewers, qa, tdadmin) to users.
Do I need to know the all the list of projects and members in each project ? Then for eg. for creating user with qa role do I need to get a approval (or a cc mail) from PM ?
Because any user may approach me asking viewer role today and tomorrow he might ask for some other role.
So I just wanted to know the ideal process for validating projects, users, and thier requirements for the roles.
thanks in advance
Re: Understanding TDAdmin role ??
The TD Admin role should only be provided to people who require full access to the project customization features. This is typically not given out to many people.
Everyone else should be assigned another role. The easiest way to get started is to use the pre-defined groups. If you find that those particular settings are not adequate for your environment, create custom groups instead.
You'll need to establish your own procedures for ensuring that a user should be granted access to TestDirector. Their are no built-in features in TestDirector to administer that process. Once you know that a user should have access, someone with the TD Admin role can then grant them the proper access.
Hope this helps,