Redact CSV and TSV files
Review delimited files without losing track of columns, headers, and rows that carry sensitive values.
Outcome
You can review a CSV or TSV by columns and rows, then verify that the exported structure still matches the file you need to share.
Your progress
Mark each step as you complete it. This is saved only in this browser.
0 / 3 steps complete
Before you start
Visual frame
Review asset
CSV and TSV redaction storyboard
Synthetic table frame only. It uses fake rows and does not imply spreadsheet formulas or hidden sheets are covered by plain CSV handling.
Synthetic frame
CSV / TSV input
Check rows, columns, and delimiter.
Redact CSV and TSV files workflow frame
Instructional frame for this operational guide. Replace with product screenshots only after the current screen state is approved.
Guided steps
Follow the task, then check the result.
Check headers and delimiters
Confirm that headers, separators, and row counts look sensible before making redaction decisions.
Review high-risk columns first
Start with columns likely to contain people, IDs, financial details, health details, locations, or secrets. Then review notes and free-text columns.
Open the exported file
Open the export in a spreadsheet or plain-text viewer and confirm the delimiter, rows, and redacted values survived the round trip.
Branch questions
Can you see the file upload and table-style review surface described in this guide?
Did the result match the completion check?
Completion check
Support boundary
Support can use by default
- Article slug and selected workflow step.
- Screen or action name.
- Browser, viewport, workspace type, and file type category when relevant.
- Synthetic sample shape or already-redacted sample only after review.
- Intent ID
- Article slug
- App route
Requires your consent
- User-written description
- Email address
- Explicit attachment
- Redacted sample
- Support bundle previewed to the user
Not collected by default
- Raw original document text
- Full local file paths
- Pasted private content
- Unmasked screenshots
- Replay capture
Safe support summary
Copy a scrubbed handoff.
Redactorr KB support summary Article: /knowledge-base/csv-tsv-redaction Selected issue: Columns shift or merge unexpectedly. Playbook progress: 0/3 steps marked complete Safe context to include: - Article slug and selected workflow step. - Screen or action name. - Browser, viewport, workspace type, and file type category when relevant. - Synthetic sample shape or already-redacted sample only after review. - Intent ID - Article slug - App route Requires explicit consent: - User-written description - Email address - Explicit attachment - Redacted sample - Support bundle previewed to the user Do not include by default: - Raw original document text - Full local file paths - Pasted private content - Unmasked screenshots - Replay capture User note: - Describe the step and symptom without pasting raw document text, secrets, files, or restoration material.
Article details
Redact CSV and TSV files
Review delimited files without losing track of columns, headers, and rows that carry sensitive values.
Use this guide when the file upload and table-style review surface is available in your workspace. If you cannot see the screen or control described here, use the safe support path instead of guessing.
Outcome
You can review a CSV or TSV by columns and rows, then verify that the exported structure still matches the file you need to share.
Before You Start
- Know whether the file is comma-separated or tab-separated.
- Keep an original local copy before editing or exporting.
- Identify the high-risk columns before starting review.
1. Check headers and delimiters
Confirm that headers, separators, and row counts look sensible before making redaction decisions.
Check before you continue: Columns line up with the source file and no obvious delimiter problem is visible.
2. Review high-risk columns first
Start with columns likely to contain people, IDs, financial details, health details, locations, or secrets. Then review notes and free-text columns.
Check before you continue: High-risk columns have been reviewed before export.
3. Open the exported file
Open the export in a spreadsheet or plain-text viewer and confirm the delimiter, rows, and redacted values survived the round trip.
Check before you continue: The exported CSV or TSV keeps its structure and reviewed redactions.
Completion Check
- Headers and delimiters were checked.
- High-risk columns were reviewed.
- The exported file opens correctly before sharing.
Safe Examples
- A fake customer list with example.test addresses.
- A synthetic CSV with fake IDs and no live customer rows.
If You Need Support
Contact support when:
- Columns shift or merge unexpectedly.
- The export changes the delimiter or row structure.
Include only support-safe context:
- Article slug and selected workflow step.
- Screen or action name.
- Browser, viewport, workspace type, and file type category when relevant.
- Synthetic sample shape or already-redacted sample only after review.
Still stuck?
Copy a safe article handoff.
Start support with the article, the issue, and safe context. Raw document text, files, restoration material, and unredacted screenshots stay out unless you explicitly choose otherwise.
- Article slug
- Selected issue
- Screen name
- Action name
Redactorr support case Source: Article playbook: csv-tsv-redaction Route: /knowledge-base/csv-tsv-redaction Selected issue: Columns shift or merge unexpectedly. Safe context: - Article slug and selected workflow step. - Screen or action name. - Browser, viewport, workspace type, and file type category when relevant. - Synthetic sample shape or already-redacted sample only after review. - Article slug - Selected issue - Screen name or article section - Action name Only include with explicit consent: - User-written description - Email address - Explicit attachment - Redacted sample - Support bundle previewed to the user Do not include by default: - Raw original document text - Full local file paths - Pasted private content - Unmasked screenshots - Replay capture - Hidden diagnostic uploads User note: - Describe what you tried and what happened. Do not paste raw document text, secrets, files, restoration material, or unredacted screenshots.
Support case builder
One case format, wherever you start.
This is the same support case shape used by diagnostics and article handoffs.
- Article slug and selected workflow step.
- Screen or action name.
- Browser, viewport, workspace type, and file type category when relevant.
- Synthetic sample shape or already-redacted sample only after review.
- Article slug
- Selected issue
Private material belongs behind an explicit consent step, not in the initial case.
6 default exclusions