Skip to main content

​
Overview

Move Snippets Between Teams transfers snippets from one team to another within the same workspace, removing them from the source team. This is perfect for reorganizing your workspace, correcting misplaced snippets, or transferring ownership as team responsibilities change. Unlike copying, moving is a one-way transfer-the snippet is removed from its original location.

​
Why Move Between Teams?

Common scenarios:

​
Reorganization

Before:
  Frontend Team:
    📝 "API Helper Function" (belongs in backend)

After:
  Backend Team:
    📝 "API Helper Function" ✓ (moved)
Correct team placement for better organization.

​
Team Transitions

Development Team:
  📝 "Feature X Snippets" (feature complete)

→ Move to →

Production Team:
  📝 "Feature X Snippets" (production-ready)
Promote snippets as they move through workflow stages.

​
Responsibility Transfer

Consultant Team:
  📝 "Client Onboarding Process" (project ending)

→ Move to →

Internal Team:
  📝 "Client Onboarding Process" (permanent home)
Transfer ownership when roles change.

​
How It Works

​
Step-by-Step: Move Single Snippet

​
1. Select Snippet

Find the snippet in its current team.

​
2. Right-Click (RMB)

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

​
3. Select “Move to Team”

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

​
4. Choose Destination Team

Dialog shows:
  • List of all teams in current workspace
  • Excludes current team (can’t move to itself)
Select destination team.

​
5. Select Folder

Choose where in destination team:
  • Root (no folder)
  • Existing folder
  • Create new folder

​
6. Confirm Move

Click “Move” button. Result:
  • Snippet disappears from source team
  • Snippet appears in destination team
  • All metadata preserved

​
Move Multiple Snippets

Batch moves:

​
1. Select Multiple

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

​
2. Right-Click Selection

Context menu shows “Move X snippets to team”

​
3. Choose Destination

Select team and folder as above.

​
4. Bulk Move

All selected snippets moved together. Progress indicator for large batches.

​
What Happens During Move

​
Preserved

✅ Snippet Content:
  • Full text content
  • Syntax highlighting
  • Description
✅ Metadata:
  • Snippet name
  • Creation date
  • Last modified date
  • Creator attribution
✅ Attachments:
  • Audio files
  • Video embeds
  • File attachments
✅ Tags:
  • All existing tags
  • New tags created in destination if needed
✅ History:
  • Edit history/versions preserved
  • Full version control intact

​
Changed

🔄 Team Association:
  • Was: Source Team
  • Now: Destination Team
🔄 Folder Location:
  • Placed in selected destination folder
  • Folder structure doesn’t transfer (choose new location)

​
Not Preserved

❌ Team-Specific:
  • Favorites status (removed if favorited)
  • Shortcuts (cleared-must reassign)
  • Team-specific permissions

​
Move vs. Copy

FeatureMoveCopy
OriginalDeletedRemains
DestinationNew locationNew copy
Use CaseReorganizeShare/duplicate
ReversibleManual undoOriginal intact
Best ForOne correct locationMultiple locations
Use Move when:
  • Snippet belongs in different team
  • Cleaning up organization
  • Transferring ownership
Use Copy when:
  • Need snippet in multiple teams
  • Want to adapt for different contexts
  • Keeping original as backup

​
Use Cases

​
Misplaced Snippets

Scenario: Snippet created in wrong team. 
1. Created in "Marketing Team" by mistake
2. Should be in "Engineering Team"
3. Right-click → Move to Team → Engineering
4. Problem solved

​
Project Lifecycle

Scenario: Snippets progress through stages. 
Development → Testing → Production

As features are completed:
1. Move snippets from Development to Testing
2. After testing, move to Production
3. Clear progression, organized workspace

​
Team Restructuring

Scenario: Company reorganizes teams. 
Old Structure:
  Web Team: Frontend + Backend snippets

New Structure:
  Frontend Team
  Backend Team

Action:
1. Move backend snippets from Web → Backend Team
2. Move frontend snippets from Web → Frontend Team
3. Archive or delete Web Team

​
Ownership Transfer

Scenario: Team member leaving, snippets need new home. 
Sarah's Personal Team:
  📝 Customer Support Scripts

Sarah leaving company:
1. Move scripts to Customer Support Team
2. Team continues using them
3. Knowledge retained

​
Best Practices

Think Before Moving: Moving is destructive to source. Consider copying if you’re unsure.
Communicate with Team: If moving shared snippets, notify team members who might be using them.
Batch Similar Moves: Move related snippets together. Easier to track and undo if needed.
Update Documentation: If team wikis reference moved snippets, update links.
Favorite Before Moving: If snippet was favorited, re-favorite after moving (favorites don’t transfer).

​
Permissions Required

​
To Move Snippets

Source Team:
  • Must have Edit or Admin permissions
  • View-only members can’t move snippets
Destination Team:
  • Must be a member
  • Must have Edit or Admin permissions
Your Permission:
  • Must own the snippet OR
  • Be team admin
Can’t move someone else’s snippet unless you’re admin.

​
Undo a Move

Moving is not automatically reversible, but you can undo manually:

​
Immediate Undo

If you just moved and realize it was a mistake:
  1. Don’t close dialog (if still open)
  2. Some versions have “Undo” button
  3. Click to reverse move

​
Manual Undo

If dialog is closed:
  1. Go to destination team
  2. Find the moved snippet
  3. Right-click → Move to Team
  4. Move back to original team
  5. Place in original folder
Note: Shortcuts and favorites will need to be reconfigured.

​
Bulk Operations

​
Moving Entire Folders

While you can’t move folders directly, you can move all snippets in a folder:
  1. Open folder in source team
  2. Select all snippets
  3. Right-click → Move to Team
  4. All snippets moved together
  5. Manually recreate folder structure in destination if needed

​
Moving by Tag

Move all snippets with a specific tag:
  1. Filter by tag in source team
  2. Select all visible snippets
  3. Move together to destination team

​
Troubleshooting

​
Can’t Move Snippet

If “Move to Team” is grayed out or fails:
  1. Permission Issue: You may not have edit rights in source or destination
  2. Read-Only Team: Source or destination team may be read-only
  3. Archived Team: Can’t move to/from archived teams
  4. Not a Member: You must be a member of destination team

​
Snippet Disappeared

If snippet is missing after move:
  1. Switch to Destination Team: It moved successfully, you’re viewing source team
  2. Use Workspace Search: Search for snippet name across all teams

​
Shortcuts Stopped Working

After moving snippet, shortcuts don’t work:
  • Expected: Shortcuts are team-specific and don’t transfer
  • Solution: Reassign shortcut in destination team

​
What’s Next

Copy Snippets Between Teams

Learn when to copy instead of move

Copy Snippets to Workspace

Copy snippets across different workspaces

Switching Between Teams

Navigate between teams after moving snippets