Private Preview
Join Waitlist →

Import and export pattern templates

Move pattern templates between workspaces or teams using synthetic examples and careful review.

Updated 31 May 20265 min readAuthor: Redactorr Support Team · [email protected]Last reviewed: May 2026

Outcome

You can import, export, and review pattern templates without leaking real internal identifiers.

Your progress

Mark each step as you complete it. This is saved only in this browser.

0 / 3 steps complete

Before you start

Use synthetic examples in templates wherever possible.
Confirm you are authorised to share the template.
Test imported patterns on fake data before real documents.

Visual frame

Review asset

Pattern template import/export storyboard

Synthetic pattern template frame only. It uses fake examples and avoids encouraging live internal identifiers inside templates.

ExamplesSynthetic
ImportCheck settings
TestFake data first

Synthetic frame

Template export

Remove live identifiers before sharing.

Pattern nameSupplier ID sample
ExampleACME-TEST-001
Live identifierRemoved
A template export should not carry real internal records.

Import and export pattern templates workflow frame

Instructional frame for this operational guide. Replace with product screenshots only after the current screen state is approved.

FindReview before export
DecideImport into the target workspace
VerifyTest with fake data first

Guided steps

Follow the task, then check the result.

Review before export

Check pattern names, descriptions, examples, and notes for live internal IDs or secrets before exporting.

Success check: The exported template contains only safe examples.

Import into the target workspace

Import the template where it is needed, then check owner, category, and enabled state before using it.

Success check: The imported template is visible with the intended settings.

Test with fake data first

Run the imported pattern against synthetic examples and edge cases before applying it to private documents.

Success check: The pattern behaves correctly on fake data.

Branch questions

Completion check

Template examples are synthetic or already redacted.
Imported settings were checked.
Fake-data tests passed before production use.

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/pattern-template-import-export
Selected issue: A template fails to import with a clear error.
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

Import and export pattern templates

Move pattern templates between workspaces or teams using synthetic examples and careful review.

Use this guide when the pattern import and export 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 import, export, and review pattern templates without leaking real internal identifiers.

Before You Start

  • Use synthetic examples in templates wherever possible.
  • Confirm you are authorised to share the template.
  • Test imported patterns on fake data before real documents.

1. Review before export

Check pattern names, descriptions, examples, and notes for live internal IDs or secrets before exporting.

Check before you continue: The exported template contains only safe examples.

2. Import into the target workspace

Import the template where it is needed, then check owner, category, and enabled state before using it.

Check before you continue: The imported template is visible with the intended settings.

3. Test with fake data first

Run the imported pattern against synthetic examples and edge cases before applying it to private documents.

Check before you continue: The pattern behaves correctly on fake data.

Completion Check

  • Template examples are synthetic or already redacted.
  • Imported settings were checked.
  • Fake-data tests passed before production use.

Safe Examples

  • ACME-TEST-001 as a fake internal ID.
  • A template export with owner names masked.

If You Need Support

Contact support when:

  • A template fails to import with a clear error.
  • Imported settings differ from the exported template.

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.

Support can start here
  • Article slug
  • Selected issue
  • Screen name
  • Action name
Redactorr support case

Source: Article playbook: pattern-template-import-export
Route: /knowledge-base/pattern-template-import-export
Selected issue: A template fails to import with a clear error.

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.

Safe 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.
  • Article slug
  • Selected issue
Consent boundary

Private material belongs behind an explicit consent step, not in the initial case.

6 default exclusions

Before you copy0/4 ready
Open safe support guide