Early Access and Private Testing
Some Hatz features, models, integrations, and product surfaces are released gradually. You may see a feature mentioned in documentation before it is enabled for your organization.
Why a feature may not appear
A feature may be unavailable because it is in private testing, controlled rollout, security review, tenant-level configuration, package-based availability, or temporary product evaluation. Availability can also vary by organization policy, user role, integration provider, and product surface.
How to request access
To request access, email [email protected] or contact your Hatz account team. Include the feature name, your organization, the tenant or workspace where you want to use it, your use case, and whether you are willing to provide product feedback during testing. Also specify the requested scope: one user, a specific tenant, your MSP admin organization, or your MSP plus all managed end-customer tenants.
How requests are reviewed
Access is approved case by case. Hatz may prioritize partners with active usage, larger customer bases, clear production use cases, or a strong ability to provide feedback during the testing period. Requesting access does not guarantee approval or a specific timeline.
What to expect during early access
Features may change, be limited, or become temporarily unavailable during testing.
Some early-access features may require additional security, billing, product, or implementation review.
Hatz may ask for feedback, examples, or operational details before expanding access.
Private-testing access for one tenant or user does not necessarily enable the feature across your entire organization.