Cleary stores user information in our database that comes via a 1 way sync from Namely API. We can sync this 3 times daily in 8 hour intervals. No information is posted back into Namely.
Use cases
- Basic profile information (name, title, reporting structure, etc)
- Content targeting (by city, job function, etc)
- Indicating which users are active or inactive (computed from start date / end date)
Key User Fields
A list of some of the key fields that Cleary system uses
| Cleary Field Name | Description |
| emloyee_id | Unique identifier for employee |
| manager_employee_id | Unique identifier for employee’s manager |
| last_name | Employee’s last name |
| first_name | Employee’s first name |
| preferred_name | Employee’s preferred first name |
| start_date | Employee’s start date |
| end_date | Employee’s end date |
| emails | List of email addresses associated with this employee |
| title | Employee’s job title |
| city | City employee is in |
| job_family | Employee’s job family |
| contingent | Flag indicating if employee is a contingent worker |
| exempt | Flag indicating if employee is an exempt worker |
| manager | Flag indicating if employee is a manager |
| birthday | Employee’s birthday |
| phone_mobile | [Optional] Employees phone number for display purposes on profile page. |