Custom Mapping Configuration on

Domain Matching Rules

Mon, 01 Jan 0001 00:00:00 +0000

Exact Match Rules (config does NOT start with `*`)

Config: `example.com`

Hostname (from URL)	Matches?	Reason
`example.com`	✅	Exact
`www.example.com`	✅	`www.` stripped → `example.com`
`example.com/about`	✅	Path ignored; hostname = `example.com`
`example.com/login?next=/`	✅	Query ignored; hostname = `example.com`
`hr.example.com`	❌	Only `www.` is stripped; `hr.` is not
`sub.example.com`	❌	Subdomain not stripped
`app.hr.example.com`	❌	Multi-level subdomain, no match
`notexample.com`	❌	Different hostname
`example.com.evil.com`	❌	Normalized to `example.com.evil.com`

Config: `www.example.com`

Hostname	Matches?	Reason
`example.com`	✅	Config strips `www.` → `example.com`
`www.example.com`	✅	Both strip `www.`
`hr.example.com`	❌	`hr.example.com !== example.com`
`www.hr.example.com`	❌	Strips to `hr.example.com !== example.com`

Config: `hr.example.com`

Hostname	Matches?	Reason
`hr.example.com`	✅	Exact
`www.hr.example.com`	✅	`www.` stripped → `hr.example.com`
`example.com`	❌	Parent domain, not matched
`other.example.com`	❌	Sibling subdomain
`app.hr.example.com`	❌	Child subdomain; only `www.` is stripped

Wildcard Rules (config starts with `*`)

Both *example.com and *.example.com normalize to base example.com.

Sibling Match Criteria

Mon, 01 Jan 0001 00:00:00 +0000

Overview

Sibling matching is configured through siblingMatchCriteria on a mapping entry. It is a context filter: your primary mapping still finds candidate elements, and siblingMatchCriteria decides whether each candidate should be unprotected based on what appears near it.

Use it when:

The same target element pattern appears in multiple places on a page
Only one section should be unprotected
A nearby label or marker identifies the correct context

How to Think About It

Treat it as an “anchor” check:

Table Column Unprotection

Mon, 01 Jan 0001 00:00:00 +0000

Overview

The Table Column Unprotection feature allows you to target entire table columns using columnMatchCriteria on a mapping entry. Rather than creating selector-based rules that match individual cells row by row, you define a single column mapping that identifies the column by its header label and automatically unprotects all qualifying data cells beneath it.

This is ideal for:

Protecting sensitive columns in data tables (email, phone, SSN, etc.)
Avoiding repetitive selector rules when the same column appears across multiple page layouts
Working with component-based tables (e.g., Salesforce Lightning) where cell markup is complex and nested

How It Works: From Configuration to Unprotection

When a mapping entry includes columnMatchCriteria, the unprotection process follows these steps:

Custom Mapping Configuration on

Domain Matching Rules

Exact Match Rules (config does NOT start with *)

Config: example.com

Config: www.example.com

Config: hr.example.com

Wildcard Rules (config starts with *)

Sibling Match Criteria

Overview

How to Think About It

Table Column Unprotection

Overview

How It Works: From Configuration to Unprotection

Exact Match Rules (config does NOT start with `*`)

Config: `example.com`

Config: `www.example.com`

Config: `hr.example.com`

Wildcard Rules (config starts with `*`)