How Do I Create a New Team?

Use Teams to organize users, assign permissions, and prioritize feedback for your testing projects.

This article applies to Legacy, Team, and Enterprise editions.

Teams are a fundamental part of managing your testing projects in Centercode. They allow you to group users based on roles, access levels, or other criteria, ensuring efficient user administration and feedback analysis.

Key Terms

• Teams: Organize participants into groups to define their permissions, activities, and access.
• Copy Access: Save time by duplicating permissions from an existing team and customizing them.
• Team Impact: Adjust feedback weights to prioritize or de-prioritize input from specific teams (e.g., prioritize VIP client feedback or minimize less critical groups).

Create a Team

From the Community homepage:

1. Expand the Community menu.
2. Navigate to Community management > Teams.
3. Click the Create a community team button

From the Project homepage:

1. Expand the Management drop-down.
2. Navigate to Users > Teams.
3. Click the Create a project team button.
4. Enter the Team Name and an optional Description.
5. Select a User role to broadly define the team's purpose.
6. Select Copy Access from an Existing Team if applicable
   💡 Ted Tip:  Choose a similar team to duplicate permissions then edit the copied permissions to match the new team’s needs.
7. Optionally include a Target users number to show how many users are needed to fill the team.
8. Select a Feedback impact factor (team impact is detailed below).
9. Select Apply cross-project label if needed (learn more here).
10. Click the Submit button at the bottom of the page.

You have successfully created a new team.

Team Impact

The Feedback impact factor drop-down allows you to adjust the weight of feedback submitted by members of a specific team, ensuring their input is prioritized or de-prioritized in your project.

• Increase the importance: Feedback from this team will have a higher impact on the overall score (e.g., prioritize VIP client feedback).
• Decrease the importance: Feedback from this team will have less influence (e.g., de-prioritize general testers).

Notes and Best Practices

• Community vs. Project Teams:
  • The community and each project have their own teams.
  • User roles (team types) are different in projects vs. the community.
    
    • Community user roles: Administrator, Project creator, Member
    • Project user roles: Project manager, Support, Observer, Participant, Applicant
• Copy, Don’t Create from Scratch:
  Copying access from an existing team ensures users have at least some level of access. This will also be quicker compared to setting all access from scratch.
• Monitor and Adjust Impact:
  Review team weights to ensure your testing priorities align with your project’s needs.