The extension can still be removed
A normal installation can be removed. Check the effective installation mode in chrome://policy, the exact extension ID, policy scope and any errors. The required mode is force_installed, not normal_installed. A generated plan has no effect until separately deployed.
Do not rely on unpacked builds for a family setup. FeedHush’s public extension and managed runtime are not available yet.
Another browser still opens
This belongs to the device app-control layer. Chrome policies cannot close Safari, Edge or Firefox. Review the child account, app-control feature, app exceptions and new installations. A web-filtering product may support several browsers without blocking those apps.
If the tool only limits time, check what happens during an allowed period. If it cannot enforce the intended restriction, the setup remains incomplete.
An allowed site is blocked everywhere
Check which tool displayed the block. Review device website rules, DNS or network rules, schedules and the app’s own status separately. A global domain block can also affect your approved browser.
Keep the original rules recorded. Resolve a specific conflict with the vendor’s guidance; do not bypass web filtering wholesale or choose an “Ignore” rule to conceal the problem.
Settings saved, but nothing changed
Saving in the parent workspace records desired settings. The current child runtimes do not complete delivery and enforcement, and no social-site filtering is available. This is an unfinished product path, not a reason to weaken your device controls.
Likewise, a request approval currently records a decision only. It does not add time or unlock an app.
The device is offline or its status is old
Do not assume an offline device received a rule change or revocation. Confirm its connection and current client status before relying on a change. The intended runtime requires verified, unexpired settings and explicit recovery when they cannot be trusted; end-to-end behavior is still awaiting verification.
Collect useful information safely
Record OS and browser versions, the affected layer, policy names and error text, and the steps that failed. Remove account identifiers, enrollment tokens, pairing codes, credentials and page content. Direct FeedHush support is not available yet; use the responsible vendor’s linked help for its settings.