At its core swimlanes are the lanes that nodes are assigned to in order to make and give structure to a diagram. What this means is that, a swimlane is populated by a resource such person, institution, object, or other entity that is in control of the nodes below in it's column such as a meeting or a report, these can extend to others as well if more swimlanes are needed to satisfy the outcome of the node assigned to it.
Each swimlane is divided into three primary sections: name, title, and label:
First we have a name, the "Name" is the only part of the swimlane that is required from the user. With naming you are want to add a specificity to a swimlane such as "East Atlanta Warehouse #3" for a physical building or something like "Willrow Hood" for being a co-worker. This allows you to quickly scan your swimlanes and place your nodes where you need them with ease.
Next, we have Title; titles help you differentiate between larger teams and establish a hierarchy when it comes to swimlanes with many of the same role and even name. You might have 26 developers and three of them with the last name Smith. With the title section you can specify their specific function such as "Agent Smith #1, #2,..etc" or you can specify who is the in a senior position such as "VP of Agents" or "Scranton Regional Manager"
Lastly, let's look at labels. Labels can be a place "Warehouse", a job "Developers", or a group "The Avengers". Roles are assigned to clarify a base for the swimlane and are usually the most broad when it comes to defining a swimlane.
The choice is up to you, many different industries have opposing or different practices and TeamFlow gives you the tools to sort out your teams as effortlessly as possible.