> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getsnippets.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating Teams

> Create and manage teams within your workspace

## 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

<iframe src="https://player.vimeo.com/video/1104085882?h=0&title=0&byline=0&portrait=0&autoplay=1&muted=1" width="100%" height="450" frameborder="0" allow="autoplay; fullscreen; picture-in-picture" allowfullscreen />

### 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:

1. Search for members by name or email
2. Select their role:
   * **Admin**: Full control over team
   * **Editor**: Can create/edit snippets
   * **Viewer**: Can view snippets only
3. 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

1. Click team name in sidebar
2. Dropdown shows all your teams
3. Select a team to switch
4. 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

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

<Tip>
  **Clear Naming**: Use descriptive team names that clearly indicate purpose.
  Avoid abbreviations or internal jargon.
</Tip>

<Tip>
  **Document Team Purpose**: Add descriptions to teams explaining what snippets
  belong there and who should join.
</Tip>

<Tip>
  **Regular Audits**: Quarterly, review team membership and remove inactive
  members. Archive unused teams.
</Tip>

<Tip>
  **Cross-Team Snippets**: For snippets needed by multiple teams, create a
  "Shared" or "Common" team that everyone joins.
</Tip>

## Managing Teams

### Renaming Teams

1. Click team name in sidebar
2. Select "Team Settings"
3. Change name
4. Save

All members see the updated name immediately.

### Archiving Teams

When a project ends or team is no longer needed:

1. Team Settings → "Archive Team"
2. Snippets are preserved but team is hidden
3. Can be restored later if needed

### Deleting Teams

**Caution:** This is permanent.

1. Team Settings → "Delete Team"
2. Confirm deletion
3. All team snippets are deleted
4. Cannot be undone

**Recommendation:** Archive first, delete later if certain.

### Transferring Team Ownership

If a team admin leaves:

1. Current admin goes to Team Settings
2. Select "Transfer Ownership"
3. Choose new admin
4. 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

<Card title="Switching Between Teams" icon="toggle-on" href="/guides/switch-teams">
  Learn how to quickly switch between teams
</Card>

<Card title="Folders & Tags Management" icon="folder-tree" href="/guides/folders-tags-management">
  Organize snippets within teams using folders and tags
</Card>

<Card title="Moving Snippets Between Teams" icon="arrow-right" href="/guides/move-snippets-teams">
  Transfer snippets from one team to another
</Card>