Quick answer
Device restrictions, a player PIN and a category filter can govern different things. Test the intended restricted view instead of assuming that one hidden category protects the whole device.
Define the boundary
Decide whether the goal is restricting app installation, purchases, a player’s categories or use of a particular profile. A control that hides a category may not prevent opening another app or changing profiles. State the boundary before choosing settings.
Use the controls present in the actual build
Review the device’s native account/restriction features and the installed player’s documented options. Phone, TV and desktop interfaces differ. Do not borrow a remote long-press sequence or PIN menu from an unrelated player screenshot.
Test from the ordinary user route
Return to the normal home/profile view and check the restricted action. Reopen the app and verify whether the restriction persists. Test access without revealing the PIN in a shared capture, and keep recovery arrangements private.
Keep credentials off the shared screen
Account fields, QR codes, playlist URLs and device keys can remain visible during setup. Close those screens when finished and avoid saving secrets in a shared note or publicly readable profile label. Software controls do not replace ordinary account privacy.
Recheck after a change
A player update, reinstall or profile replacement can alter preferences. Preserve the working configuration where supported and test the same boundary again. This guide does not promise universal child-safety controls or certify the suitability of every catalogue item.