Implications of Project Roles for Project Management in Toolbox 7.1
PRINTThe introduction of Project Roles in Toolbox 7.1 has important implications to which all Toolbox Administrators should pay special attention, primarily that Roles and Turf are unique to each Project. Importantly, any Project that is defined as “All People” will have neither Turf nor Roles preserved during the upgrade process.
Pervious versions of Toolbox had only two types of individuals to whom users with Turf-editing rights could make assignments, Organizers and Organizing Committee. These Turf assignments were valid across any Project in the database that had overlapping Project definitions vis-a-vis employers. This meant that when you had a “parent” Project and a “child” Project made up of a subset of the “parent” Project, Turf definitions in the child Project would show up in the larger Project.
Let’s take an example of a hospital organizing campaign. There are two Projects, the “Mercy Hospital - All BU” Project composed of Service, Tech, Professional Bargaining Units (i.e., the “parent Project”, and a smaller Project call “Mercy Hospital - Tech BU” Project that is composed of only the Tech BU (i.e., a “child” Project”. You first create Turf assignments in the Tech Project by assigning Organizer Al Swearengen EKG, EEG, & Rad Tech job classes. You then open the “All BU” Project to make Turf assignments and you’ll find that Al Swearengen already has been assigned EKG, EEG, and Rad Techs.
In Toolbox 7.1 Roles and Turf are completely unique to each Project. This means that Turf assignments and Roles in one Project will not show up in any other Project where Project Definitions overlap. Using the same example as above, when you create the “Mercy Hospital - All BU” Project after Assigning Turf in the “Mercy Hospital Tech BU” Project you will not see any of those assignments carried over to the “All BU” Project from the “Tech BU” Project. (Caveat: Out-of-Project Roles show up on the Roles tab in the Person Module but cannot be edited.)