URL filtering controls access to web pages and resources by checking their addresses against rules. The system allows or blocks a request based on the rules that apply. These may cover specific addresses, website categories, or known risks.
Companies use URL filtering to block malicious sites and set browsing limits. It can also help teams restrict access to particular business pages. An employee who needs a store account for payment reconciliation may have no reason to open its product management pages.
Why Can One Shared Account Need Different Page Access?
A business account can contain several jobs. Finance checks settlements, support handles orders, and operations maintains products. Each person needs access to the store, but their work takes them to different pages.
Consider a fictional store portal with these addresses:
https://portal.example.com/settlements/https://portal.example.com/products/
Both use the same domain. Their paths point to different parts of the application. A filter that supports path matching could distinguish settlement pages from product pages. A rule that only allows the domain would not make that distinction.
This need can exist with just one account. With multi-accounting, the same question also applies across client stores or brands. The number of accounts changes the workload, but each assignment still needs a clear browsing scope.
Use the platform's staff permissions where available. URL rules can add limits within a managed browsing environment.
How Does URL Filtering Work?
A URL filter checks requests within the traffic or browser environment it manages. The process usually follows four steps:
- A user requests a page. They enter an address, follow a link, or load a resource through a website.
- The system finds the applicable rules. These may depend on the user, group, device, or browser profile.
- The filter checks the address. It looks for a matching rule and may consult category or risk information.
- The system applies a decision. It allows or blocks the request. Some products also support warnings or logging.
A custom list can name individual addresses or supported patterns. Category filtering groups sites by topic or purpose. Reputation checks use a provider's assessment of the destination. That differs from a visitor's IP reputation, which concerns activity associated with the source address.
Filters can run in a managed browser, on a device, or through a proxy or web gateway. Their location affects what they can inspect. A network gateway generally needs TLS inspection to read an HTTPS path. A browser can apply rules to an address it already knows.
The supported URL matching format matters too. Domain patterns, paths, query parameters, and rule priority can behave differently between products. A pattern copied from another tool may match too much, too little, or nothing.
Allowlist vs. Blocklist: Two Ways to Set the Browsing Scope
An allowlist mode starts with a narrow scope. It permits listed destinations and blocks the rest. This can suit a task with a small, known set of pages.
For the finance example, the allowed scope might include settlement reports and related order details. It must also support the route into those pages. A login service or redirect may use a different address. Missing that dependency can stop an otherwise permitted task.
A blocklist mode takes the other approach. It blocks specified destinations while leaving other access subject to the remaining policies. This can be easier to maintain when someone needs broad access but must stay out of particular areas.
Neither mode decides which pages belong in a person's job. That decision comes first. The list then expresses it through the matching options the product supports.
Check how conflicting rules are resolved. Adding an address to an allowlist does not have the same effect in every system. A more specific block or another policy may still prevent access.
Applying URL Rules to the Right Members and Browser Profiles
A rule needs more than an address. It also needs a defined scope:
- Pages: Which addresses should it match?
- People: Which members should it affect?
- Environments: Where should the rule run?
Suppose finance needs the settlement area while operations needs the product area. Applying the finance restriction to everyone could interrupt product updates. Applying it to the wrong profile could leave the intended work environment unrestricted.
The management tool must be able to identify the member and apply the policy to the relevant environment. Sharing a website password alone does not create that distinction.
In MoreLogin, URL access restrictions let administrators choose an access mode, applicable members or roles, and browser profiles. Saved or updated rules require the affected profiles to restart before they take effect.
Check the result through the member's access. They should reach the pages needed for their task while restricted addresses remain blocked. An administrator's successful test may reflect different permissions.
What URL Filtering Can and Cannot Control
URL filtering sets limits on reachable addresses. A page can still contain several kinds of information and action.
| Control | Question It Answers |
|---|---|
| URL Access Rule | Can the Member Open This Page? |
| Content or Element Restriction | Which Parts of the Page Are Visible? |
| Action Permission or Restriction | Can the Member Edit, Delete, Copy, or Download? |
For example, a contractor may need a social account's publishing page. If that page also contains deletion controls, allowing it does not express which buttons the contractor may use. A separate action rule or platform permission is needed.
MoreLogin's guidance on role-based access control for shared accounts covers how URL rules fit alongside content and action controls. Those controls serve different parts of the assignment. Hiding a button does not revoke the underlying server permission.
Several practical limits deserve attention:
- Classification can be wrong or incomplete. A useful site may be misclassified. A new malicious page may not yet have a risk record.
- Paths can change. A moved report or new login route can break an existing rule. Some applications also run several actions through one page or shared endpoint.
- Coverage has boundaries. A browser policy does not automatically govern other browsers, native apps, or separate API clients.
Applications still need authorization checks for the requested resource and action. URL restrictions cannot replace those checks.
DNS filtering works at another point. It evaluates domain lookups, so it cannot distinguish two HTTP paths from the domain query alone. Browser isolation changes where web content runs. These controls can work together, but allowing a URL does not prove the page or its downloads are safe.
URL Filtering FAQ
Does URL filtering work on HTTPS websites?
Yes. The available detail depends on where the filter runs and what it can see. A gateway may need TLS inspection for path rules. A managed browser can use the destination address directly.
Why does an allowed website still fail to load?
The page may depend on another domain, login redirect, or blocked resource. Record the failing address and check which rule applied. If the filter allowed the request, investigate the connection, account permissions, or application response separately.
Does blocking a URL remove someone's account permissions?
No. It restricts access through the system enforcing that rule. It does not automatically remove platform membership or end an existing login elsewhere. When an assignment ends, review those access routes separately.
Is URL filtering the same as DNS filtering?
No. DNS filtering evaluates domain resolution. URL filtering evaluates web addresses and can distinguish paths when the implementation supports it. The useful choice depends on the access rule and where it must apply.

EN
