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 or 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 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:

  • 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:

Whereas 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.

Hence, if you believe your customer has various groups, or are unsure where organization information lives, we highly recommend using our Groups endpoint to account for these differences.

Did this answer your question?