What good looks like
A named team with a clear purpose, active members, supervisor/ownership context, and no unintended access change.
Have these details ready
- The team's operational purpose
- Employees who should be members
- The supervisor or accountable manager
Run the workflow
-
Check existing teams
Review current names, members, and responsibilities. Avoid duplicate teams that differ only by abbreviation.
-
Create the team
Enter a durable name and description tied to function, location, trade, or service line rather than a temporary project nickname.
-
Add members
Use Add Member to select active employees who actually work in this group. Confirm each person's primary manager and location remain accurate.
-
Review operational impact
Check how the team will be used in scheduling, filters, reporting, approvals, workflow assignment, and any permission model.
-
Save and validate
Create Team or Save Team, reopen it, verify membership, then test a team-filtered schedule/report or assignment.
Check your work
Do not call the workflow complete until these statements are true.
- The team has a unique purpose and owner
- Only intended active employees are members
- A team-based filter or assignment returns expected people
If something does not look right
One employee belongs to several groups
Use supported membership while keeping primary management and scheduling responsibility clear.
Removing a member affects open work
Reassign active tasks, approvals, schedules, and workflows before changing membership.