ZOVANTA SOFTWARE / KNOWLEDGEBASE

Inspected package workflow • see settings reference for version and requirements

Beta Access Pro — configure applications and review testers

Beta.2 remains a Premium development preview. It configures one board program: name, description, acceptance terms and up to ten questions. Five initial questions/default terms were added with a one-time backfill that preserves owner edits and earlier accepted terms. Saving a custom question list replaces the default list; clearing a field intentionally after migration should stay cleared.

Start with applications closed, review your text and category/group permissions, then choose whether NEW submissions are manually reviewed or automatically accepted. As staff, approve/reject an application or remove a participant through the provided controls. Applicants see their own status/message; private answers are not a public list.

Adoption of the existing beta category, beta-testers group and memberships is non-destructive and recorded by a snapshot/receipt. Reinstall should not reapply defaults over later settings. Renaming the category should not break a saved category ID. Do not delete the core beta surface merely because the addon loads: the recorded core_removal_ready=false gate still applies.

The legacy access model permits registered members to read the category and approved testers to post; accepting someone does not automatically create tester-only reading privacy. Set actual category/group access deliberately. Source and fixture checks do not certify a live provider/activation or production migration. Keep the preview status in your deployment decision.

We suggest Panelica for managing your hosting environment.