Skip to main content

How to Create and Manage Teams

Create manual or dynamic Teams in the Admin Console to filter views by owner, assign templates, and enroll users in Activity Capture automatically.


Overview

Teams allow you to assign specific workflows and templates to different groups of users. First, you create a 'Team'. Then, you assign users to said 'Team'. By doing so, you can group the different job roles at your company within Weflow.


Use Cases for Teams

Below, you can find a quick overview of use cases for 'Teams' in Weflow:

Owner Filter

  • Non-hidden teams are displayed as part of the owner filter.

  • End-users can use teams to quickly select a group of users e.g. to a filter a view.

Templates

  • Admins can use both hidden and non-hidden teams to assign templates (e.g. notes, pipeline views, forecasts, ...).

Configurations

  • You can use hidden and non-hidden teams to assign users dynamically to e.g. Activity Capture.

  • That way, you don't need to constantly go back to Weflow's admin console and remove / assign parting or new users in your Salesforce organization to Weflow's activity capture.


Creating and managing Teams

Click here to access the 'Teams' section in the admin console.

Step 1: Click 'Add new Team'

Step 2: Select a team type

  • Manual selection: Admins need to manually add/remove users.

  • Dynamic Selection: Admins can use conditions based off user fields (as well as from profiles and roles) to automatically assign users to teams.

  • Checkbox (Hidden): Make team invisible in e.g. 'Owner' filter, meaning end-users cannot select this team to filter their pipeline views.

​Step 3: Enter a name & assign a manager

  • We recommend using names based on job roles such as 'Account Executive' or 'RevOps'.

  • However, you can choose any name you want.

  • Manager-assignment is relevant if you want to create a hierarchy in Weflow (outside of your Salesforce hierarchy). This feature is coming soon (Q3 2025).

​Step 4: Assign templates or configurations

  • Admins can now assign templates or use teams for configurations.

  • Users can select non-hidden teams to filter pipeline views.

Did this answer your question?