Guide: Bamboo
How Do Core Concepts Map to Tenzo?
Key: ✅ Supported 🚸 Work in Progress ❌ Not Supported
 |
|
|---|---|
| Location | ✅ Location |
| Employee | ✅ Employees |
| Employee leave date | ✅ Termination Date |
| Employee start date | ✅ Hire Date |
| Shift (actual) | ❌ Not Supported |
| Shift (planned) | ❌ Not Supported |
| Hours | ❌ Not Supported |
| Salaried workers | ❌ Not Supported |
| Role | ❌ Not Supported |
| House Part | ❌ Not Supported |
| Overheads | ❌ Not Supported |
| Holiday | ❌ Not Supported |
| Breaks | ❌ Not Supported |
| Overtime | ❌ Not Supported |
Bamboo supplies your employee records only. It tells Tenzo who works at each location, not when they worked or what they were paid, so it does not produce hours or labour cost on its own. To report on labour you also need a scheduling or time-and-attendance integration connected alongside it.
Data Ingestion
| Real-time optionally available? | ❌ |
| Default polling frequency | Daily, overnight |
| Data retrieved on each poll | The full employee list, including former employees |
| Historical data | All employee records held in Bamboo when the integration is first connected |
How Do I Compare Bamboo Data to Data in Tenzo?
Compare your Bamboo employee list against the employees Tenzo holds for the same location. The names and leave dates should match, and each employee should appear against the location recorded on their Bamboo record.
Two differences are expected by design. Employees are grouped by the location on their Bamboo record, so anyone whose record has no location set will not appear in Tenzo. Start dates are not part of the employee feed we receive, so Tenzo shows an employee's leave date but not the date they joined.