Skip to main content

​
Overview

Snippets AI’s workspace architecture uses a three-level hierarchy: Workspace → Teams → Snippets. Switching between teams lets you access different snippet collections within the same workspace, making it easy to context-switch between projects, departments, or use cases. This guide shows you how to efficiently switch between teams and understand which team’s snippets you’re currently viewing.

​
Understanding the Architecture

​
The Hierarchy

🏢 Workspace (Your Company/Organization)
  ├─ 👥 Team 1 (e.g., Frontend)
  │   └─ 📝 Snippet collection
  ├─ 👥 Team 2 (e.g., Backend)
  │   └─ 📝 Snippet collection
  └─ 👥 Team 3 (e.g., Prompt Engineering)
      └─ 📝 Snippet collection
Key Points:
  • You’re always in one workspace at a time
  • Each workspace has multiple teams
  • Each team has its own snippets
  • You can be a member of multiple teams

​
How It Works

​
Team Dropdown (Primary)

In the Sidebar:
  1. Look at top of sidebar
  2. See current team name with dropdown arrow
  3. Click team name
  4. Dropdown shows all your teams in this workspace
  5. Click desired team
  6. Snippet library updates to show that team’s snippets

​
What Changes When You Switch

​
Visible Snippets

Current Team Only:
  • Snippet library shows only current team’s snippets
  • Folders and tags from current team
  • Search within team
Not Affected:
  • Quick Access (shows all teams’ snippets)
  • Global Favorites (shows favorites from all teams)
  • Workspace Search (searches all teams by default)

​
Context Indicators

Current Team Shown:
  • Team name in sidebar header
  • Breadcrumbs at top of app
  • Team badge on snippets (in search results)

​
Snippet Expansion Shortcuts

Important: Snippet expansion shortcuts (like /hello) are team-specific. Example: 
Team: Frontend
  Snippet: "React Component" → Shortcut: /rc

Team: Backend
  Snippet: "API Route" → Shortcut: /rc (different snippet)
When you’re in Frontend team, typing /rc expands Frontend’s React Component. When you switch to Backend team, typing /rc expands Backend’s API Route. Workaround for Global Shortcuts:
  • Use unique shortcut names across teams
  • Or use Quick Access instead (searches all teams)

​
Common Team Structures

​
By Department

🏢 Company Workspace
  ├─ 👥 Frontend Team
  ├─ 👥 Backend Team
  ├─ 👥 DevOps Team
  ├─ 👥 Product Team
  └─ 👥 Marketing Team
Switch when: Moving between different functional areas of work.

​
By Project

🏢 Agency Workspace
  ├─ 👥 Client A Project
  ├─ 👥 Client B Project
  ├─ 👥 Client C Project
  └─ 👥 Internal Projects
Switch when: Moving between client projects or internal work.

​
By Environment

🏢 Engineering Workspace
  ├─ 👥 Production Snippets
  ├─ 👥 Staging Snippets
  └─ 👥 Development Snippets
Switch when: Moving between different deployment environments.

​
By Purpose

🏢 AI Development Workspace
  ├─ 👥 ChatGPT Prompts
  ├─ 👥 Claude Prompts
  ├─ 👥 Code Snippets
  └─ 👥 Documentation Templates
Switch when: Switching between different types of work.

​
Team Switching Workflows

​
Context Switching During Development

Scenario: Full-stack developer 
Morning:
1. Switch to "Frontend Team"
2. Use React snippets via Quick Access
3. Insert component templates

Afternoon:
4. Switch to "Backend Team"
5. Use API route snippets
6. Insert database queries

Evening:
7. Switch to "DevOps Team"
8. Use deployment scripts
9. Insert CI/CD configs

​
Project-Based Work

Scenario: Agency developer 
Monday-Wednesday:
- Switch to "Client A Team"
- All snippets are Client A specific
- Use custom templates for this client

Thursday-Friday:
- Switch to "Client B Team"
- Different snippets, different context
- Use Client B branding and templates

​
Learning & Production

Scenario: AI Engineer 
Exploration:
- Switch to "Experimental Prompts Team"
- Try new prompt engineering techniques
- Test and iterate

Production:
- Switch to "Production Prompts Team"
- Use tested, approved prompts
- Maintain quality standards

​
Team Permissions

​
What You Can Do

Depends on your role in the team: Team Admin:
  • View, create, edit, delete any snippet
  • Manage team members
  • Configure team settings
  • Delete team
Team Editor:
  • View all snippets
  • Create new snippets
  • Edit own snippets
  • Cannot delete team or manage members
Team Viewer:
  • View snippets only
  • Cannot create or edit
  • Read-only access

​
Switching to Teams You’re Not In

If you see a team in Workspace Overview but can’t switch to it:
  • You’re not a member of that team
  • Ask team admin to add you
  • Or join team (if self-service joining is enabled)

​
Best Practices

Use Keyboard Shortcuts: Master Cmd/Ctrl + T for fast team switching. Much faster than clicking.
Keep Team Count Manageable: Being in 10+ teams gets overwhelming. Join only teams you actively use.
Name Teams Clearly: Use descriptive names so you know which team to switch to without guessing.
Default to Most-Used Team: Set your primary team as default. Switch only when needed.
Use Quick Access for Cross-Team: Don’t switch teams just to grab one snippet. Use Quick Access instead.

​
Troubleshooting

​
Can’t Find a Team

If a team is missing:
  1. Check Workspace: Are you in the right workspace? (See Switch Accounts)
  2. Team Membership: Were you removed from the team? Check with admin.
  3. Team Deleted: Team may have been deleted by admin.

​
Wrong Team After Restart

If Snippets AI opens to wrong team:
  1. Set Default Team: Settings → Teams → Set Default Team
  2. Last Active: Or enable “Remember last active team” in settings

​
Snippet Missing After Switch

If snippet disappears when you switch teams:
  • Snippet belongs to previous team, not current team
  • Switch back to original team to find it
  • Or use Workspace Search (searches all teams)

​
What’s Next

Creating Teams

Learn how to create new teams in your workspace

Switching Between Accounts

Learn how to switch between different workspaces and accounts

Quick Access Overview

Use Quick Access to search across all teams without switching