Build Team Stage

The Build Team stage enables community members to assemble teams of experts, implementers, and colleagues around the ideas. Administrators can configure the number of team members to be added to the stage, and choose to permit or restrict vote retraction based on program needs.

---

Build Team Stage Setup

Build Team Stage setup is divided into 4 tabs - Info, Settings, Automation & Permissions. Let's see them in detail.

1. Info

Info section contains basic details about the stage as follows:

Stage Function - Select Build Team stage from drop down. Once selected and saved, this section will be greyed out and cannot be changed to other stage

Stage Name - Create a custom name/label for the stage. Note: Character limit is 40.

Stage Key - It is a unique identified for the specific stage required for API call data retrieval. Once saved, the key cannot be changed.

Description - Describe stage functionality or how you would like to use this stage. This description will be mouseover text on the stages stack on the right navigation of the community homepage

Stage Color - Select a color for the stage from the 10 available default options.

Reported Ideas As - Set the stage as Selected, Implemented or blank to apply the respective label to all ideas within that stage. Help article on Selected & Implemented Ideas ( To be linked)

Enable Stage - Select this checkbox to activate the stage, enabling ideas to be moved into it.

Stage Change Notification - Select this checkbox to activate the stage change notification. Enabling it will send a stage change email notification to the members who have opted for it.

---

2. Settings

Settings section contains stage specific settings as follows:

Starting Team Positions: Community administrators can define team positions either by assigning a specific team role or by assigning a position to an individual member. By default, four team positions are available that can be added using the +Add button or removed using the Recycle bin icon besides the position.

Automatically Assign Idea Submitter as a Team Member: When enabled, it assigns the idea author/submitter, as a member of the team automatically.

Idea Submitter Can Assign/Unassign Team Members: Idea Submitter can restrict any member joining the idea team. They have the privilege to choose their team by assigning / unassigning team members.

Team Member Can Assign/Unassign Team Members: If a member is on the idea team they have the privilege to assign/unassign other team members from the idea.

Team Member Can Add/Remove Positions: Team members can add or remove any number of positions to from a team on the ideas.

Starting Team Positions May Not be removed: When enabled starting team position set by community administrator cannot be removed by team members irrespective of the above setting. When disabled, team members can remove the default position set by an administrator if required.

Allow Joining Teams: When enabled, members will be able to join the idea team by themselves.

Comment Tab Enabled: When this feature is enabled, the comments tab is organized into two distinct sections: a "Community" section and a section associated with the Build stage. Community members can share and discuss ideas in the Community section, while members of the build team use the second section to record their stage-specific feedback and collaboration.

 

---

3. Automation

Use this section to configure automation for the Build team stage. When automation is enabled, once an idea has all its positions filled, it will automatically advance to the next stage in the workflow.

---

4. Permissions

The Permissions section in the Build Team stage defines who can join the idea team in that stage and who can view the current idea team and open positions on the idea detail page. A community administrator can configure these permissions for all community members, for a specific group, or for a specific Team Member role (Only if a team role has been specified & filled in any build team stage in the same funnel).

---

Team Building using Team Roles

Team building can be designed using the Team roles functionality from the community Settings section. The Community Administrator can assign specific team roles to the positions to fill. Team roles can be created under Campaign Management >> Team Roles.

Setting up these roles will help members to build the Idea team.

Help article on Team Roles

---

Stage Functionality on Homepage

Member Interface:

For Ideas moved to the Build Team Stage, members can either Join Team using 'Fill this role' option and message each other from the Idea Details Page - depending on the settings enabled /disabled by the Administrator while setting up the stage.

The members allowed to participate in the Build stage will see a dropdown in Comments tab with the stage name. The members can add in a comment which will be only accessible and visible to members who can participate in the stage.

Members who have New Comments Notification enabled will receive email notification for the build stage with the Stage name mentioned in the notification.



Participants who are not permitted to view or participate will not see the progress bar, the number of team members who joined or the build team details.

Moderator/Admin Interface:

For ideas that have progressed to the Build Team stage, administrators and moderators can perform several team management actions. They can join the team themselves, assign or remove members, add or remove positions, update role definitions, and promote a user to serve as the idea owner.

Whenever a member is added to an idea team, that individual automatically receives an email notification informing them of their new team assignment.

Role of Team Members

Two Heads are Better than One: Team-Based Idea Submission lets multiple community members be attached to an idea and work towards the successful completion of the idea.
 
Team members collaborate with the idea submitter to ensure the idea is successfully developed and completed. To support this collaboration, team members are allowed to edit and refine the idea. Community members who are not part of the team cannot edit the idea; however, they can communicate with the team by sending messages to team members.