đź§© Creating and Editing Teams
System Administrators in ValueStreamer can create new teams, manage existing ones, and build complex cascade structures. This article explains the process—with and without the Teamboard Templates add-on.
🔍 Content
-
Create a team without a template
-
Create a team with a template (add-on active)
-
Edit an existing team
-
Build a cascade structure
-
Tips & Best Practices
-
FAQ
âś… Create a team (standard, without template)
-
Click the ⚙️ gear icon in the top right.
-
In the left menu, open Team Management.
-
Click Add Team at the top.
-
Enter the following team data:
-
Team name
-
Short code
-
Optional: Parent team
-
Optional: Mark as "Private"
-
-
Choose one of the following options at the bottom:
-
Create team
-
Create another team
-
Add sub-team
-
Switch to team board
-
âś… Create a team with a teamboard template (add-on active)
-
Follow the same steps as above.
-
After clicking Add Team, you’ll see the Teamboard Templates selection.
-
Choose a template.
-
Enter the team data as above.
-
Click Create Team to set it up with the chosen template.
✏️ Edit an existing team
-
Open the team structure in Team Management.
-
Click the desired team.
-
Select Edit Team Profile.
-
Edit tabs as needed:
-
Profile: Name, short code, parent team, time zone
-
Members: Add users, change roles
-
KPIs: Assign available metrics
-
Lists: Assign core or tenant-specific lists
-
Views: Select boards, KPI overviews, etc.
-
đź§± Build a cascade structure
-
Create the top-level team (e.g., plant, site).
-
Use Add Sub-Team from the dropdown.
-
Assign each new team to its parent team.
-
KPI values cascade automatically through the hierarchy.
ℹ️ Notes
-
Only admins can create or edit teams.
-
Cascading allows inheritance of KPIs, lists, and views.
-
Teamboard template selection is only available at creation, not later.
-
The Teamboard Templates add-on must be activated separately.
✨ Tips & Best Practices
✔️ Use meaningful short codes (e.g., S_Production
).
✔️ Plan team structures hierarchically for easier cascade and permissions.
✔️ Use templates for consistent boards during rollouts.
✔️ Only create necessary teams—less is more.
✔️ Keep naming conventions consistent (e.g., Region_TeamFunction
).
✔️ Create a separate “Test_…” cascade to trial KPIs before live use.
âť“ FAQ
What’s the difference between a team and a sub-team?
→ A sub-team belongs to a parent team in the hierarchy and is part of a cascade.
Can I link a team to a template later?
→ No, templates can only be chosen during creation.
Can I restructure teams later?
→ Yes, you can reassign, rename, and change the parent team.
What happens with private teams?
→ Content is visible only to assigned members.