Administering Teams
One of the main activities that a product or library manager has is to administer the local team associated with the product or library.
 |
If the context team created in a product or library includes a shared team or is exclusively made up of a shared team, the shared team is managed from the organization context and is not managed by the product or library manager.
|
When a product or library that uses a local team is first created, a base set of roles for the local team is established from the context template that is used in the creation. For more information about these roles and the access control rules that are set for the roles that are in the out-of-the-box templates, see Out-of-the-box Context Access Control Policies.
To administer a product or library local team, perform the following activities:
• Establish the roles that you want used in the team. You can add, remove, or create new roles.
The base set of roles that are established through the out-of-the-box templates is the minimal set of roles that you should have for a team. (See Out-of-the-box Context Participation) Before removing any of these roles, consider the consequences of the removal. For example in a product team, you should not remove the Product Manager role because this role defines who can administer the product.
The roles you can add are roles inherited from your organization. For additional information about these roles, see Templates.
You can also create roles specifically for your product or library local team. In addition to creating a new role through the Team page, you must define the access control rules for the role by using the Policy Administration utility. As part of this activity, create the rules against the system group that is created for the team role. This group has the same name as the role that you create.
|
|
Any new roles that you create are not available for life cycle, workflow, or team templates.
|
• Add users to the team by adding the users in the specific roles.
You can add users by selecting individual users or by selecting the user-defined groups or organizations that are available. For example, if the organization administrator has created groups for the organization context, you can select one or more of these groups to be a member of a role.
|
|
When the organization context is created, the site administrator has the option of restricting user access. By default, users are restricted so that they see only users or user-defined groups that belong to the organization. Selecting the Restricted Directory Search checkbox when the organization context is created provides the ability to search for all users or user-defined groups. If this checkbox was not selected when the organization was created, the site or organization administrator can update the organization context to select it. Only site administrators can search for other organization participants regardless of the checkbox selection.
|
• Change task assignments for members of a team.
As the membership of a team changes or members change responsibilities, you can manage the ownership of the tasks assigned to team members.
From Products 
or Libraries 
, click the Team link to access the Members table. From this table, you can administer a product or library local team. For more information about teams, see Teams.
or Libraries , click the Team link to access the Members table. From this table, you can administer a product or library local team. For more information about teams, see Teams.Click the Assignments link to access a table of assignments with the following views: All, Open, Overdue, Assigned to Me, Completed, and Uncompleted. From this table you can manage the tasks assigned to your team.