All Collections
Best Practice Guides
Using Groups and Teams in Merge
Using Groups and Teams in Merge

The difference between Merge's Groups and Teams Common Models

Jemma Baus avatar
Written by Jemma Baus
Updated over a week ago

If you take a look at our docs you might notice that our Groups and Teams Common Models are very similar, they both have the same purpose of gathering organization information on an employee. However, as we were developing our /teams endpoint, we noticed that most integrations have more than one type of group, department, or division. That is why we created our Groups Common Model - to account for the various groupings of people in an HRIS system.

The Group object is used to represent any subset of employees, such as Department, Paygroup, Division, or Team.

  • If your customer has multiple types of groupings (for example Division, Cost Center, and Department) then all those groups will be created and you will be able to distinguish each by the type field

  • If an employee is in multiple Groups (fore example Finance Department in the West Coast Division), then Merge will create an ID for both of those Groups:

The Team object is used to represent a subdivision of the company, usually a department.

  • Each employee will be grouped into only one specific Team.

*As of April 20th, 2023 we no longer support the Team common model. We recommend using Groups as it includes the same capabilities as Teams and is more comprehensive.

Did this answer your question?