Creating Teams - Snippets AI

Overview

Teams are the organizational layer within Snippets AI workspaces that allow you to segment snippets by department, project, or any logical grouping. Each workspace can contain multiple teams, and each team has its own collection of snippets, folders, and members. Understanding the workspace → team → snippets hierarchy is key to scaling Snippets AI across your organization.

The Hierarchy

Snippets AI uses a three-level hierarchy:

🏢 Workspace (Company/Organization)
  └─ 👥 Team (Department/Project)
      └─ 📝 Snippet (Individual snippets)

Example:

🏢 Acme Corp Workspace
  ├─ 👥 Legal Team
  │   └─ 📝 NDA Template, Contract Clauses...
  ├─ 👥 Frontend Team
  │   └─ 📝 React Components, CSS Utils...
  ├─ 👥 Backend Team
  │   └─ 📝 API Routes, DB Queries...
  └─ 👥 Prompt Engineering Team
      └─ 📝 ChatGPT Prompts, Claude Prompts...

Why Use Teams?

Teams provide critical benefits:

Isolation: Keep team snippets separate and focused
Permissions: Control who can access which snippets
Organization: Scale to hundreds of team members without chaos
Context: Switch between team contexts easily
Collaboration: Team members only see relevant snippets

How It Works

Step-by-Step: Creating a Team

1. Open Workspace Settings

In the Snippets AI app:

Click on your workspace name at the top
Select “Workspace Settings” from dropdown
Navigate to the “Teams” section

2. Click “Create New Team”

Look for the ”+ New Team” button or “Create Team” option.

3. Name Your Team

Choose a clear, descriptive name: Good Team Names:

✅ Frontend Development
✅ Customer Support
✅ Sales Outreach
✅ AI Prompt Engineering
✅ Legal & Compliance

Avoid:

❌ Team 1
❌ Misc
❌ Unnamed Team

4. Add Description (Optional)

Provide context for team members:

Frontend Development Team

This team contains all React components, CSS utilities,
and frontend-related snippets. All frontend engineers
should have access.

5. Set Team Settings

Configure team options:

Visibility: Private (team members only) or Internal (all workspace members can view)
Default Permissions: Can members create/edit snippets or only view?

6. Add Team Members

Invite workspace members to the team:

Search for members by name or email
Select their role:
- Admin: Full control over team
- Editor: Can create/edit snippets
- Viewer: Can view snippets only
Click “Add”

7. Create the Team

Click “Create Team” to finalize. The team appears in the team switcher, and you can start adding snippets.

Team Roles & Permissions

Team Admin

Create, edit, delete any snippet
Manage team members
Change team settings
Delete the team

Team Editor

Create new snippets
Edit own snippets
View all team snippets
Cannot manage team settings

Team Viewer

View all team snippets
Use snippets via Quick Access
Cannot create or edit snippets
Read-only access

Switching Between Teams

Once you have multiple teams, you can switch between them:

In Main App

Click team name in sidebar
Dropdown shows all your teams
Select a team to switch
Snippet library updates to show that team’s snippets

Common Team Structures

By Department

🏢 Company Workspace
  ├─ 👥 Engineering
  ├─ 👥 Product
  ├─ 👥 Design
  ├─ 👥 Marketing
  ├─ 👥 Sales
  └─ 👥 Customer Support

Best for: Traditional company structures, clear departmental boundaries.

By Project

🏢 Agency Workspace
  ├─ 👥 Client A - Website Redesign
  ├─ 👥 Client B - Mobile App
  ├─ 👥 Client C - Marketing Campaign
  └─ 👥 Internal - Agency Operations

Best for: Agencies, consultancies, project-based organizations.

By Function

🏢 Engineering Workspace
  ├─ 👥 Frontend
  ├─ 👥 Backend
  ├─ 👥 DevOps
  ├─ 👥 Security
  └─ 👥 Data Engineering

Best for: Large engineering orgs, specialized teams.

By Use Case

🏢 AI Development Workspace
  ├─ 👥 Prompt Engineering
  ├─ 👥 Code Generation
  ├─ 👥 API Integrations
  └─ 👥 Testing & QA

Best for: Focused organizations, specific workflow needs.

Hybrid Approach

🏢 Startup Workspace
  ├─ 👥 Product Development
  │   (Everyone: engineers, designers, PMs)
  ├─ 👥 Go-to-Market
  │   (Sales, marketing, support)
  ├─ 👥 Operations
  │   (Finance, legal, HR)
  └─ 👥 AI & Automation
      (Cross-functional: prompts, tools, workflows)

Best for: Startups, cross-functional work, flexible structures.

Best Practices

Start with Few Teams: Begin with 3-5 core teams. Add more as you grow. Too many teams creates confusion.

Clear Naming: Use descriptive team names that clearly indicate purpose. Avoid abbreviations or internal jargon.

Document Team Purpose: Add descriptions to teams explaining what snippets belong there and who should join.

Regular Audits: Quarterly, review team membership and remove inactive members. Archive unused teams.

Cross-Team Snippets: For snippets needed by multiple teams, create a “Shared” or “Common” team that everyone joins.

Managing Teams

Renaming Teams

Click team name in sidebar
Select “Team Settings”
Change name
Save

All members see the updated name immediately.

Archiving Teams

When a project ends or team is no longer needed:

Team Settings → “Archive Team”
Snippets are preserved but team is hidden
Can be restored later if needed

Deleting Teams

Caution: This is permanent.

Team Settings → “Delete Team”
Confirm deletion
All team snippets are deleted
Cannot be undone

Recommendation: Archive first, delete later if certain.

Transferring Team Ownership

If a team admin leaves:

Current admin goes to Team Settings
Select “Transfer Ownership”
Choose new admin
Confirm transfer

Or workspace admin can reassign ownership.

Advanced Use Cases

Client Projects

Create a team per client:

🏢 Agency Workspace
  ├─ 👥 Client: TechCorp
  │   └─ Subfolders by deliverable
  └─ 👥 Client: RetailCo
      └─ Subfolders by campaign

When project ends, archive the team but keep snippets for reference.

Onboarding Teams

Create temporary teams for onboarding cohorts:

🏢 Company Workspace
  ├─ 👥 Onboarding - Q1 2025
  │   └─ New hire resources
  └─ 👥 Onboarding - Q2 2025
      └─ Updated onboarding snippets

Testing & Staging

Separate production from development:

🏢 Engineering Workspace
  ├─ 👥 Production Snippets
  │   └─ Tested, approved snippets only
  └─ 👥 Development Snippets
      └─ Experimental, WIP snippets

Promote snippets from Development to Production after review.

What’s Next

Switching Between Teams

Learn how to quickly switch between teams

Folders & Tags Management

Organize snippets within teams using folders and tags

Moving Snippets Between Teams

Transfer snippets from one team to another

​Overview

​The Hierarchy

​Why Use Teams?

​How It Works

​Step-by-Step: Creating a Team

​1. Open Workspace Settings

​2. Click “Create New Team”

​3. Name Your Team

​4. Add Description (Optional)

​5. Set Team Settings

​6. Add Team Members

​7. Create the Team

​Team Roles & Permissions

​Team Admin

​Team Editor

​Team Viewer

​Switching Between Teams

​In Main App

​Common Team Structures

​By Department

​By Project

​By Function

​By Use Case

​Hybrid Approach

​Best Practices

​Managing Teams

​Renaming Teams

​Archiving Teams

​Deleting Teams

​Transferring Team Ownership

​Advanced Use Cases

​Client Projects

​Onboarding Teams

​Testing & Staging

​What’s Next

Switching Between Teams

Folders & Tags Management

Moving Snippets Between Teams

Overview

The Hierarchy

Why Use Teams?

How It Works

Step-by-Step: Creating a Team

1. Open Workspace Settings

2. Click “Create New Team”

3. Name Your Team

4. Add Description (Optional)

5. Set Team Settings

6. Add Team Members

7. Create the Team

Team Roles & Permissions

Team Admin

Team Editor

Team Viewer

Switching Between Teams

In Main App

Common Team Structures

By Department

By Project

By Function

By Use Case

Hybrid Approach

Best Practices

Managing Teams

Renaming Teams

Archiving Teams

Deleting Teams

Transferring Team Ownership

Advanced Use Cases

Client Projects

Onboarding Teams

Testing & Staging

What’s Next