Assemble supports an unlimited level and number of teams, which you may refer to as hierarchy locations. You can configure Assemble to reflect the structure of the organisation using the Teams setting.
In addition to their role profile, you need to place each user in a team for that role, within your organisation. This determines who can manage them and, if they are a supervisor, who they can manage. Therefore, it's important to make sure that you configure teams in a logical manner that reflects your organisation's structure.
Managers can always manage the users in the team you place them in, along with all teams below their team. For example, if your organisation has regions, by placing a regional manager at the region level, they can automatically manage users in any further teams that are directly connected to and are below their team.
Below is an example team structure a national organisation may have.
In this scenario, a manager in the Lobbying team can manage all of the users within the regions, constituencies, parish teams and wards under them.
Add teams
By default, Assemble has two levels of teams already configured, with the top team inheriting the name of your organisation. Below that, there's a team called Volunteers, which you can rename.
To add a new team below another one:
Point to the row of the parent team.
Click More actions then select Add sub-team.
To add a team at the same level, select Add same level team.
Hierarchy item name
Enter the name of the team. Make sure that your teams are easily identifiable in a list, without the help of the hierarchy. In the example above, entering Region 1 (Lobbying) would help distinguish it from Region 1 (Retail).
Description
Enter a further description of the team. This is optional.
Location
If the team you're setting up is a physical location such as a shop or office, you can find its address and assign it to the team. Whenever you publish an event or opportunity to a team, the location pre-loads.
📌 Note: Please add the team first then edit it to add the location.
Icon
When adding a team, you can use the built-in icons to help you visualise the team location. Having an established naming and icon system ensures that there's consistency, especially where you have hundreds of teams.
External reference
Store an external reference ID for the team. This is used for syncing your system with an external system through the API, for example. This field is optional.
Edit teams
To edit the team, point to the row for that team then click Edit. Once you've made your changes, click Update.
Delete a team
It isn't possible to delete a team. However, you can mark them as hidden so that you can't have any volunteers in it or recruit anyone to it. You can only mark a parent team as hidden if all its children are hidden also. To hide a team, point to the team's row and click Hide.
Hiding a team that still has volunteers in it results in a prompt for you to say what action you want to take with these volunteers. You can either begin the leaving process for all volunteers in the team or transfer them all to a different team. If some are leaving and some transferring, complete one of those options within the user record screens first.
You can't hide a team where there are published opportunities linked to it. In this scenario, either take the opportunity offline or change the team of the opportunity first.