Skip to main content

View Alias Blocklist

The view alias blocklist protects names that should not be used by custom views.

What it is for​

Custom views can have friendly aliases. The blocklist prevents teams from accidentally using aliases that are confusing, reserved, or unsafe.

Use it for names such as:

  • admin
  • login
  • api
  • status
  • support
  • billing
  • names reserved for future pages or campaigns

When to add a blocked alias​

Add an alias when:

  • it could be confused with a built-in route
  • it belongs to another team or product
  • it is reserved for a future customer-facing page
  • it is too generic to safely assign to one view

Good blocklist habits​

  1. Keep the list short and intentional.
  2. Add a reason when your team process tracks one.
  3. Review the list before launching a new group of custom views.
  4. Prefer clear custom-view names instead of relying on the blocklist to prevent confusion.