Beta cohorts and staged feature rollout
Explain why controlled beta testers may receive different previews while keeping plan entitlements, organization permissions, data protections, and Control Vault authorization authoritative.
Before you begin
- An active invitation-based beta account.
- An assigned cohort when a preview is cohort-limited.
- The required Keeper or Pro entitlement and organization permission.
Interface walkthrough
These annotated interface maps describe the current PMA controls. They do not replace a real record review in your workspace.
Identifies the testing group used for launch operations without changing the organization plan.
Shows the current rollout stage determined by the protected feature-flag service.
Explains staged availability without suggesting that browser changes can unlock the feature.
Step-by-step workflow
Confirm your beta and plan status
A cohort controls testing access only. The organization still needs the feature entitlement and the user still needs the operational permission.
Use the preview normally
Record feedback through Help & Support and include the preview name, route, expected result, and observed result.
Expect staged changes
A preview may move from internal to selected cohorts, percentage rollout, all beta users, and fully released—or be disabled if unsafe.
Do not work around unavailable features
Changing local storage, URLs, cached files, or API requests cannot safely grant access and may create rejected actions.
Expected result
The tester understands the reason for staged availability and can provide useful feedback without confusing cohort access with a paid plan, role, or permanent release promise.
Safety boundaries
- A feature flag can narrow availability but cannot grant a missing plan entitlement.
- A cohort cannot grant organization access, platform roles, or Control Vault access.
- Server and database checks remain authoritative.
- Percentage assignment is deterministic and does not depend on repeated refreshing.
- Essential husbandry workflows must not be disabled solely by an experimental rollout.
Troubleshooting
Another tester sees a feature I do not
The preview may be cohort- or percentage-limited. Confirm your beta status and report a problem only when your invitation or instructions explicitly include that feature.
A preview disappeared
PMA may pause a rollout for safety or reliability. Existing data remains subject to the feature’s documented retention behavior.
The interface appears but the action is denied
Refresh the session. The server may have newer plan, permission, cohort, or rollout information than the cached interface.