Skip to main content

Employee

A person in your workforce: who they are, which team and organization they belong to, and whether their account is active. Employees are what journey plans are assigned to, what geofences apply to, and what GPS tracking is recorded against.

Stored in the EMPLOYEE layer.


Fields​

FieldRequiredWhat it is
employee_full_nameYesFull name of the employee
employee_emailYesMust be a valid email and unique in the tenant
employee_phoneInternational format, unique in the tenant
employee_dobDate of birth
employee_usernameLogin name. This is also what other records reference - a plan assignee or a geofence assignment. A customer owner (customer_assignee) is referenced by employee_guid instead
employee_team_idYesThe team the employee belongs to
employee_organization_idYesThe organization the employee belongs to
employee_reporting_managerUsername of the manager this employee reports to
employee_roleReportingManager or Worker
employee_grade_idGrade of the employee
employee_vehicle_idVehicle assigned to the employee
employee_imagePhotograph of the employee
employee_codeAssigned by the platform, not sent on create
employee_guidAssigned by the platform. This is the id the enable and disable calls take
employee_statusLifecycle state, set by the platform: 1 new, 2 inactive, 3 active, 4 disabled

Values and formats​

The same field comes back in two shapes. Endpoints that read a record raw - create, and GET .../detail - return the stored codes. Search endpoints resolve references to their display label, and hand you the raw value in a __keyfield twin:

FieldCreate / detailSearch
employee_status"3""Active"
employee_role"Worker", "ReportingManager""Team Member", "Team Manager"
employee_team_id"2""SovereignSolutions", plus employee_team_id__keyfield: "2"
employee_organization_id"1""demo"

Match on the code, not the label: labels are tenant configuration and change without notice. Where a __keyfield twin exists, that is the value to store.


Used by​