# Co-Browse privacy and security filters

Set which website fields and page elements are obscured or excluded from the operator's Co-Browse view.

*Release 3.3 · admin, developer, visitor*

**Settings › General Settings › Co-Browse**

## What it is

Co-Browse filters control which parts of a visitor's website page reach the operator's shared view. Matching input fields can show a fixed mask, while matching page elements can be excluded. Other options help the operator view load resources and follow pages that use a custom scrolling area.

## Who uses it and why

- Administrators agree which page content must be obscured or excluded and ask Powerfront to configure it.
- Developers identify the relevant fields and page elements, then verify the result on the website.
- Visitors continue using the original page while the operator receives the filtered view.

## Where to find it

Powerfront manages these options in **Settings › General Settings › Co-Browse**. Ask Powerfront to change the filters or resource-handling options for you.

## How it works

**Password Filters** matches configured input IDs or names. Matching non-empty values are replaced with a fixed mask in the supported page-sharing and input-update paths. The operator does not receive the original value through those masked paths.

**Security Filters** matches page elements using CSS selectors and excludes matching content from the shared page. **Animation Filters** reduces attribute updates on selected elements. It is a display-compatibility option, not a substitute for excluding sensitive content.

The visitor continues to see their own page. These options change what INSIDE shares with the operator, rather than removing the content from the website itself.

## Configure it

1. Identify the fields and page areas that need protection, including content that appears after a click or form update.
2. Give Powerfront one input ID or name per line for **Password Filters**, and one specific CSS selector per line for **Security Filters**.
3. Ask Powerfront to configure **Animation Filters** or **Page Scroll Element Selector** where a page repeatedly changes or scrolls inside a separate container.
4. Verify the operator view during initial loading, typing, navigation and dynamic page changes. Repeat this check when the website changes its forms or layout.

Powerfront can also change **Bypass Proxy** when page resources need different handling.

### Settings

| Setting | Where | Applies to | Default | Who can change it | What it does |
|---|---|---|---|---|---|
| Password Filters | Settings › General Settings › Co-Browse | website | Not set | Powerfront, on request | Obscures matching input values. Supply one input ID or name per line. When not set, this filter masks no input values. |
| Security Filters | Settings › General Settings › Co-Browse | website | Not set | Powerfront, on request | Excludes matched page elements from the shared view. Supply one specific CSS selector per line. When not set, this filter excludes no elements. |
| Animation Filters | Settings › General Settings › Co-Browse | website | Not set | Powerfront, on request | Ignores attribute updates on matched elements to reduce unwanted changes in the shared view. When not set, this filter suppresses no updates. |
| Page Scroll Element Selector | Settings › General Settings › Co-Browse | website | Window | Powerfront, on request | Selects the page element to scroll when the website uses a custom scrolling area. Blank uses the window. |
| Bypass Proxy | Settings › General Settings › Co-Browse | website | Off | Powerfront, on request | Bypasses the resource proxy when reconstructing the visitor page for the operator. |

## Limits and good to know

- Do not assume a password or payment field is automatically masked. The masking described here depends on the configured field matches.
- A field whose ID or name changes may stop matching **Password Filters**.
- Invalid CSS selector lines are ignored. The remaining valid lines continue to be used, but the invalid line does not protect its intended content.
- Blank filter lists provide no configured exclusions of their respective kinds.
- Resource loading, animations and custom scrolling can affect how closely the operator view matches the visitor's page.

## Depends on and works with

### This feature uses

- **Requires** [Co-Browse with website visitors](RTC-030.md): Filters apply to accepted Co-Browse page sharing.

### Used by

- **Configures** [Co-Browse with website visitors](RTC-030.md): Masking and exclusion rules determine the page content shared with the operator.
- **Configures** [Co-Browse viewing and Control Mode](RTC-031.md): Page filters, resources and the scroll selector affect the shared view.

## FAQ and troubleshooting

### Why can the operator still see a sensitive field?

Ask Powerfront to check the field's current ID or name against **Password Filters**, or the page element against **Security Filters**. Verify both initial loading and later updates.

### Does Animation Filters hide sensitive content?

No. It suppresses selected updates. Use the appropriate masking or exclusion configuration for sensitive content.

### Why did a filter stop working after our website changed?

The field identity or page structure may have changed. Give Powerfront the updated field IDs, names or selectors and verify the shared view again.

### Why do images, styling or scrolling differ in the shared view?

Ask Powerfront to review resource handling and **Page Scroll Element Selector** for the affected page. Changing masking rules alone does not fix resource or scrolling problems.