Guides > How Team and roles work

In Slipstream, Teams are roles, and roles are Teams. We have a couple of reasons for this.

First, if your organization already has teams, we encourage you to first make some teams based on your existing structure. This is useful for administrative tasks like kicking off a certification Flow for all the members in a certain team, or getting the team's approval in cross-team processes.

However, we highly recommend that you also create teams for each role within your team. If you can describe it as wearing a hat, then we highly recommend making that an additional team in Slipstream. This is useful for anyone who wants to help wear that hat in the future, whether it's permanent (onboarding a new hire) or temporary (someone filling in over an extended medical leave).

This is exactly what Slipstream is designed for, to reveal and document the hidden roles and processes in your organization. If you happen to find roles that are duplicated across the organization, this is a great opportunity to see whether any processes can be streamlined. With Slipstream, tribal knowledge and key person risk will be a thing of the past. Keep in mind that you will need to be an Administrator or Owner in order to add or remove teams, but anyone can view all the teams in your organization.