Employees, Locations, & Users
The Application User Service is used to get/post user profiles where each user is assigned a unique User ID and password for logging in to Enterprise Manager, Net-Chef, or the Teamworx Manager Console. It links users to specific locations, hierarchies, customers and markets, and assigns each user to a user group, which determines which screens and tasks the user will be able to access in the applications.
The Employee Service combines what used to be three Crunchtime Data Pump (CDP) imports into one API call with multiple arrays. The Employee Service is used to create or retrieve an employee in Crunchtime. Employee records can be used when creating labor schedules, exporting payroll data, and maintaining employee data in 3rd party systems.
/save Employee Usage tips:
- The required fields highlighted in the developer hub represent the standard Crunchtime minimum system requirements. Customers can determine additional minimum system requirements by updating the Employee Maintenance Configuration module within Enterprise Manager. If an attribute is flagged as required within this module, that will be upheld as part of the /save API requirements for new employee creation
- The minimum required fields are only required when creating new employees; they are not required to update existing employees. Only the "employeeNumber" is required to make updates.
- Always use the employeeLocations and employeePositions arrays when defining an employee's Location(s) and Position(s).
The Hierarchy Service is used to group locations together for reporting purposes. For example, if the company is a national restaurant chain divided into six regions, setting up the hierarchy configuration allows each regional manager to view revenue, cost and consumption data (reports) only for the stores in his or her region. To associate a user, such as the regional manager, to a specific hierarchy, reference the Application User Service.
The Location Service allows you to review and configure general information about each location (restaurant, venue etc.) such as the address and phone number, as well as detailed preference settings regarding the location’s post settings, associated concepts, codes used to align Crunchtime with other systems, labor details and more.
Updated 7 days ago