Skip to main content

​
Overview

Copy Snippets Between Teams duplicates snippets from one team to another within the same workspace, keeping the original intact. This is ideal when multiple teams need the same snippet, when creating variations for different contexts, or when sharing resources across departments. Unlike moving, copying preserves the original-you end up with two independent copies.

​
Why Copy Between Teams?

Common scenarios:

​
Shared Resources

Engineering Team:
  📝 "API Documentation Template"

→ Copy to →

Product Team:
  📝 "API Documentation Template" (same content)

Both teams use the same template independently.

​
Adapted Variations

Frontend Team:
  📝 "Component Testing Guide"

→ Copy to →

Backend Team:
  📝 "Component Testing Guide" (adapt for backend testing)

Similar process, customized per team.

​
Cross-Functional Workflows

Sales Team:
  📝 "Product Demo Script"

→ Copy to →

Customer Success Team:
  📝 "Product Demo Script" (for onboarding demos)

Same content, different use cases.

​
How It Works

​
Step-by-Step: Copy Single Snippet

​
1. Select Snippet

Find snippet in its current team.

​
2. Right-Click (RMB)

Right-click or Ctrl+Click (Mac) on snippet.

​
3. Select “Copy to Team”

Context menu:
  • Copy to Workspace
  • Copy to Team ← Select this
  • Move to Team
  • Delete
  • …other options

​
4. Choose Destination Team

Dialog shows teams in current workspace. Can include current team (to duplicate within same team).

​
5. Select Folder

Choose destination folder:
  • Root level
  • Existing folder
  • Create new folder

​
6. Confirm Copy

Click “Copy” button. Result:
  • Original snippet unchanged in source team
  • New copy appears in destination team
  • Both snippets are independent

​
Copy Multiple Snippets

Batch copy operations:

​
1. Select Multiple

  • Cmd/Ctrl + Click for individual snippets
  • Shift + Click for range selection

​
2. Right-Click Selection

Menu shows “Copy X snippets to team”

​
3. Choose Destination

Select a team.

​
What Gets Copied

​
Included

✅ Content:
  • Full text content
  • Syntax highlighting settings
  • Description
✅ Metadata:
  • Snippet name
  • Creation date (original)
  • Creator (you become creator of copy)
✅ Attachments:
  • Audio files
  • Video embeds
  • File attachments
✅ Tags:
  • All tags copied
  • Tags created in destination if not present

​
Not Copied

❌ Team-Specific:
  • Favorites status (must re-favorite)
  • Shortcuts (must reassign)
  • View count/analytics
  • Edit history (starts fresh)

​
After Copying

​
Two Independent Snippets

Source Team:
  📝 "Original Snippet"

Destination Team:
  📝 "Original Snippet" (copy)
Key Point: Changes to one don’t affect the other.

​
Edit Separately

Source Team - Original:
  📝 "API Template"
  // General-purpose version

Destination Team - Adapted:
  📝 "API Template"
  // Customized for this team's needs
Both can evolve independently.

​
No Sync

There’s no automatic synchronization:
  • Update source → destination unchanged
  • Update destination → source unchanged
To sync manually, copy again (creates duplicate) or manually merge changes.

​
Use Cases

​
Standard Operating Procedures

Scenario: Every team needs the same process document. 
Operations Team creates:
  📝 "Incident Response Procedure"

Copy to:
  - Engineering Team
  - Product Team
  - Customer Success Team
  - Marketing Team

All teams have the procedure, can add team-specific notes.

​
Template Distribution

Scenario: Create templates for multiple teams to customize. 
Templates Team:
  📝 "Meeting Notes Template"
  📝 "Project Brief Template"
  📝 "Bug Report Template"

Copy to:
  - Engineering Team (customize for engineering)
  - Design Team (customize for design)
  - Product Team (customize for product)

​
Knowledge Sharing

Scenario: One team develops expertise, shares with others. 
Frontend Team perfected:
  📝 "React Performance Optimization Guide"

Copy to:
  - Mobile Team (applies to React Native)
  - Backend Team (reference for understanding frontend)

Knowledge spreads, original remains for frontend.

​
Onboarding

Scenario: New team formed, needs copies of established resources. 
From Existing Teams, copy essentials to New Team:
  - Company style guide
  - Communication templates
  - Common workflows
  - Tool configurations

New team has foundation, can customize as needed.

​
Copy vs. Move vs. Workspace Copy

FeatureCopy (Team)Move (Team)Copy (Workspace)
ScopeSame workspaceSame workspaceDifferent workspaces
SourceUnchangedDeletedUnchanged
ResultDuplicateRelocatedCross-workspace duplicate
Use CaseShare within orgReorganizeShare across orgs
Choose based on your needs.

​
Best Practices

Copy Standard Resources: Templates, guides, and SOPs should be copied to all relevant teams.
Customize After Copying: Don’t just copy blindly. Adapt copied snippets for each team’s specific needs.
Mark as Copy: Consider adding “(Copy)” or “(TeamName version)” to name so it’s clear it’s derived.
Periodic Sync: If teams need to stay in sync, schedule quarterly reviews to merge updates.
Use Shared Team for Originals: Create a “Shared Resources” team with master copies. Other teams copy from there.

​
Advanced Patterns

​
Master Copy Pattern

Structure:
  📁 Shared Resources Team (master copies)
    📝 Template A
    📝 Template B
    📝 Template C

  📁 Team 1 (copies, customized)
  📁 Team 2 (copies, customized)
  📁 Team 3 (copies, customized)

Workflow:
1. Update master in Shared Resources
2. Periodically re-copy to teams
3. Teams merge updates with their customizations

​
Version Control

Naming Convention:
  Source Team:
    📝 "API Template v1.2"

  Destination Team:
    📝 "API Template v1.2 (Marketing version)"

When source updates to v1.3:
  Copy again, teams know to update

​
Copy with Attribution

Add note to copied snippets: 
# Snippet Title

**Copied from:** Engineering Team, 2025-10-12
**Original Creator:** Sarah Johnson
**Adapted for:** Marketing Team

---

[Content here]
Maintains attribution and context.

​
Permissions

​
Required Permissions

Source Team:
  • Must have read access (Viewer, Editor, or Admin)
Destination Team:
  • Must be a member
  • Must have Editor or Admin role (to create snippets)
Snippet Ownership:
  • Anyone with read access can copy
  • Don’t need to be snippet creator

​
Access Control

Copied snippet inherits destination team’s permissions:
  • If destination is private → copy is private
  • If destination is public → copy is public

​
Troubleshooting

​
Can’t See Destination Team

If team doesn’t appear in copy dialog:
  1. Not a Member: Join the team first
  2. No Create Permission: You don’t have editor/admin role in destination
  3. Archived Team: Can’t copy to archived teams

​
Duplicates Created

If you accidentally copy same snippet multiple times:
  • Each copy operation creates a new snippet
  • No automatic duplicate detection
  • Manually delete extras
Prevention: Check destination team before copying.

​
Tags Not Appearing

If tags don’t show up after copy:
  1. Tags should be created automatically in destination
  2. May take a moment to sync
  3. Refresh page or restart app

​
What’s Next

Move Snippets Between Teams

Learn when to move instead of copy

Copy Snippets to Workspace

Copy snippets across different workspaces

Creating Teams

Set up multiple teams to organize your snippets