The CCR Team Member

Areas of Impact

Meeting Notes

Technical Documentation

What is the problem?

All CCR team member are currently required to have an account in ConnectWise.

Why?

1. There are processes within the organization that depend on the assumption that all CCR Team Members have access to ConnectWise PSA application

2. CCR systems depend on every CCR Team Member being in the ConnectWise PSA Member table (regardless if they ever log into the application)

Why does it it important to remove this dependency?

ConnectWise Licensing costs. ConnectWise is not serving our businesses and functions they way it used to; as a result, we have purchased new tools to close manage gaps for different functions (Asana, HubSpot etc). Our tools costs are increasing and the value for many team members to be in ConnectWise are quickly diminishing.

What is the solution?

Move the Master CCR Team Member ID into our own data layer

Why?

1. We are moving to a holding company model which means we have different legal entities. Bamboo is not equipped to handle this in one instance so each time CCR creates a new legal entity a corresponding Bamboo instance is create. Therefore, Bamboo cannot be the keeper of the CCR Team Member master.

2. Furthermore, over the years, we have learned that as our business evolves our needs in tools also evolve. As a result, we are moving to data philosophies and models where we, CCR, owns the master of key entities and we focus on integration mapping to the current tool of choice to manage the details & workflows. This model allows us to maintain some leverability and cohesion both across business units and between functions within business units despite different tools. Additionally, we create can more smoothly transitions between tools with less disruptions to other parts of the organization.

How does this work?

People are created (and ultimately managed) in Bamboo during the recruiting process.

Once a person is hired, they are considered a CCR Team Member

At this time, a process runs in the background to update our CCR_Member table where their permanent unique identify is created (CCR_MemberID)

In order to optimize our applications & systems, we need fast access to basic information about the Team Member without referencing Bamboo directly.

Additional fields in this table include:

FullName

FirstName

LastName

Title

PrimaryEmail (should be @ccr.net)

PreferredEmail (whichever brand they are associated to)

At this time, an HR member will need to update the Bamboo Employee # (found

HERE⁠

). In the future, our system should process this update automatically.

What happens when there are changes to a Team Member’s First Name, Last Name, Title, Primary or Preferred Email? A background process will run to update the CCR data layer accordingly.

⁠

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.