Creating a second context to restrict pages to certain users is kind of overkill. It's usually easier to just do that with User Group and Resource Group permissions.

If the pages are in the front end, the context of the permission rule should be 'web' and users won't be able to access them until they log in.

Remember that when you make permission-related changes, things won't work normally until the user logs out and back in again. They also won't work normally if you're logged in to the Manager in the same browser (even in a different window). Always test from another browser where you're not logged in to the Manager.

Also, be sure to add yourself to any User Groups involved or you'll end up hiding the resources from yourself.

Permissions can be tricky in MODX, but are super comprehensive once you sort it out. Have you used the documentation at https://docs.modx.com/revolution/2.x/administering-your-site/security ?

I realize the docs are a little obscure. Probably one of the best/easiest to follow tutorial/documentation is at Bob's Guides though: https://bobsguides.com/modx-security-permissions.html

Look through all that, fiddle with it and come back if you find yourself stumped. More information about how you've set up EVERYTHING that you see in these guides will be helpful to us. It appears one of the crucial elements is missing (could be anything), plus you have the added complexity of a different context.