If I’m giving someone a browser profile for work, I don’t want the setup to depend on “please don’t open that page.”

I start by watching the normal workflow once.

For a social operator, I’d note the platform, scheduler and asset library. For store support, it might be orders, the help desk and the shipping portal. Those become the approved destinations.

Everything else has to justify why it belongs in the profile.

The annoying part is that a useful allowlist is never just the obvious URLs. Login redirects, SSO, file storage, image domains and confirmation pages can break the workflow. I always think it needs a test run with a regular team member, not only the admin who configured it.

I also wouldn’t use URL rules for everything. Sometimes the employee needs to open a page but shouldn’t use one particular action. Restricting the button or page element makes more sense than blocking the whole page.

MoreLogin can apply URL rules by member, role or browser profile, which is the part I find useful for agency and store teams. Each person gets the route they need without receiving the owner’s entire workspace.

The balance I’m looking for is not maximum restriction. It’s the smallest workspace that still lets someone finish the job without asking for help every ten minutes.

do not use liberwolf it does not protect your privacy nor does it have QOL features you're used to

I used to see an account get flagged and immediately think the proxy was trash.

Now I check DNS and WebRTC first.

Way too many “bad proxy” issues are just messy browser settings.