What does "beta" mean for an integration or feature?
Updated 2 weeks ago
Beta means the feature is built and working in production, but hasn't run across enough customer connections to be called generally available. You can use it: we enable it on request and support the rollout hands-on.
What beta covers
The API is available. The provider exposes what the operation needs, and we have documented the prerequisites, permissions and steps.
It works in production. We have validated the flow with a small group of customers.
Tenants can differ. Provider configuration varies by customer, so each new connection can surface edge cases we fix with you.
Details can change. Field names and shapes on a beta model can still change, so pin the fields you depend on.
Beta can apply to one provider product rather than the whole provider. For example, the timesheet write API is in beta for ADP Workforce Now specifically.
How to use a beta feature
Check the feature's status for your provider in Model availability.
Tell us before your customer connects, so we can share any setup details or permissions the provider needs.
Have your customer connect as usual.
We validate the feature against their tenant, often with a test employee, and confirm when it is ready to use.
When a beta feature becomes generally available
We promote a feature to generally available once it runs reliably across enough production connections.
To ask about a beta model or a gap, message your support channel or email [email protected].