Supported in the standard track
- Geo-verified check-in and check-out
- Employee app for daily use
- Portal for customer administration
- Timesheets, approval and CSV export
- Basic messages, tasks and absence where the modules are activated
Back to technical overviewSupported and not supported
Technical transparency
Supported and not supported
Clear boundaries build trust.
This page defines what TapInn supports today, what is under development, and what should not be expected without an explicit agreement or further product work.
Not something to assume without checking
- A full public API platform
- Webhooks as a standard product
- Custom enterprise integrations without an agreement
- That every surface always has complete parity at the same time
- That features under development count as shipped
Details
Explained in practice.
Parity across surfaces
The goal is high parity, but it is important to be honest that some features mature on one surface before they are fully even everywhere.
Under development
Some work happens internally before it is ready for customers. It does not count as shipped until it is actually available in the product and covered in the release notes.
Agreed solutions
Customer-specific export and integration setups can be the right call, but they should be described as agreed solutions, not as a generic standard product.
Next
Related pages.
Contact
Need a concrete answer?
If you are evaluating TapInn or need clarification on workflow, privacy or technical frameworks, you can contact us directly.