Skip to content
Help Center
Submit a request Sign in

Configure sensitive-data masking rules

Data masking replaces matching text in supported rendered content. It can reduce accidental exposure of recognizable identifiers while preserving the underlying record for authorized operational needs.

Applies to: Supportbench Core. Location: Settings → Cases → Data Masking. Editing and previewing require Administer data masking.

Before you begin

  • You need editing access to Data Masking and permission to inspect the controlled content used for verification.
  • Choose the sensitive pattern and intended rendered audiences. Use fictional test values, never real credentials or private customer identifiers.
  • Review the saved result and a controlled example in the consuming workflow. Configuration, customer access and actual delivery or processing are separate checks.

Configure and verify

  1. Open Settings → Cases → Data Masking and choose New data mask or open an existing rule.
  2. Enter Name, choose Type and the appropriate Preset or Pattern/Replacement. This rule has no Description or parent-hierarchy field.
  3. Review Customer portal / Internal notes, Divisions/Roles, Active and attachment-metadata behavior. At least one supported content audience must be selected.
  4. Use Sample text, Attachment name or Attachment path with Preview with matching and nonmatching synthetic examples. If using AI regex assistance, review and test the draft before Use Draft; a suggestion is not proof of safe matching.
  5. Choose Save Changes and reopen the rule. Inspect a controlled rendered record under each intended audience and an excluded scope where applicable.
  6. Check filenames separately from file contents. Masking transforms supported display output; it is not deletion or irreversible redaction of stored source data.

Settings reference

Rule

SettingWhat it controlsHow to choose
NameRule name up to 200 characters.Describe the data pattern and purpose.
TypeIndustry default, regular expression or exact text.Prefer a built-in pattern when it accurately matches your use case.
PresetSupported presets include Phone Number, Social Insurance Number, Social Security Number, Credit Card and Email Address.Test realistic synthetic examples and false positives.
Pattern / ReplacementCustom match and replacement values, each up to 200 characters.Use a clear neutral replacement without repeating sensitive data.
Attachment metadata / ActiveApplies the supported metadata masking and enables the rule.Check filenames separately from attachment contents.

Scope and test

SettingWhat it controlsHow to choose
Customer portal / Internal notesAt least one content audience must be selected.Choose the surfaces that should receive masking.
Divisions / RolesOptional scope; empty selections mean all applicable divisions or roles.Check an included and excluded viewer.
Sample text / Attachment name / Attachment path / PreviewSynthetic inputs for a rule test; does not save the rule or log the samples.Use fictional examples, not real secrets or personal identifiers.
AuditShows rule maintenance details.Review when the rule was last changed.

AI Regex Assist

SettingWhat it controlsHow to choose
Sensitive data to detectDescribes the intended pattern to the drafting assistant.Describe the structure without including real sensitive values.
Matching / Non-matching examplesExamples that should and should not be masked.Use fictional values to expose likely false positives.
Draft Regex / Use DraftGenerates a candidate pattern and applies the selected draft to the rule editor.Review the pattern, test it in preview and save only after matching and nonmatching cases behave correctly.

Behavior to know

  • Masking is a display transformation, not deletion or irreversible redaction of the stored source.
  • New rules start with Phone, Active, public and internal scope, and attachment metadata off.
  • Regular expressions use case-insensitive and multiline matching with a two-second timeout. Keep patterns bounded and test them.
  • Preview checks matching and replacement only. It does not evaluate Customer portal / Internal notes, Divisions or Roles; verify applicability through the saved rendered surface with the intended viewers.

Recommended use

  • Give the rule a Name that identifies the pattern and operational purpose. This form has no Description field.
  • Test expected matches and nearby nonmatches with synthetic data before activating a rule; overly broad masking can make an agent’s evidence unreadable.
  • Verify the saved rule on the actual supported rendered surface and viewer scope. Keep attachment metadata tests separate from file-content handling and retain the distinction between display masking and stored source data.

Worked example: test an Email mask without using customer addresses

  1. Create an illustrative Email addresses in case text rule. Choose Industry Default, then choose Email Address under Preset. Review the supplied replacement [redacted email]. Use only synthetic values; do not paste a real customer address or credential into the test.
  2. In Sample text, enter Contact: alex.smith+sb@example.test and choose Preview. The address should be replaced with [redacted email]. Then test Contact: alex at example dot test, which should not match this preset. Inspect the actual result and match count; Preview does not save the rule or test its viewer scope.
  3. Choose Customer portal / Internal notes and the intended Division/Role scope deliberately. Empty Division or Role selections mean all applicable scope. For a restricted pilot, select the actual intended scope and identify an excluded test viewer before saving.
  4. Choose Save Changes, reopen the rule and inspect a controlled record on the supported rendered surface with an included viewer. If the rule deliberately excludes another viewer or content audience, test that path separately; the rule tester alone has not verified viewer authorization or scope.
  5. If attachment metadata masking is needed, test synthetic Attachment name and Attachment path separately through Preview and verify the displayed metadata after saving. Do not assume the contents of an attached file were changed.
  6. If the address remains visible or ordinary text disappears, inspect Type, Pattern/Replacement, Active and saved scope. Correct and retest the specific rule. Masking changes supported display output; it does not erase the source or justify making sensitive records accessible.

Troubleshooting

ProblemWhat to check
Expected text remains visibleCheck the matching rule, Active value, Customer portal / Internal notes audience, Division/role scope and whether the surface supports the transformation.
Ordinary text is hidden unexpectedlyTest similar nonmatching samples and narrow the pattern before relying on it.
A regex test fails or times outKeep the pattern bounded and review the displayed validation. The documented regex execution limit still applies.
An attachment’s contents remain readableMetadata masking does not imply the contents of every attached file are rewritten.
AI suggested a patternReview and test it, then explicitly apply/save through the supported route. Do not treat the suggestion as a validated result.
  • Organization → Configure agent roles and division access
  • Organization → Configure divisions

Was this article helpful?