> For the complete documentation index, see [llms.txt](https://docs.taskade.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taskade.com/workspaces/workspaces/teams.md).

# Teams

***

## Table of Contents

* [Overview](#overview)
* [Key Terminology](#key-terminology)
* [Workspace Organization Methods](#workspace-organization-methods)
  * [Method 1: Workspace per Department](#method-1-workspace-per-department)
  * [Method 2: One Workspace, Folders per Department](#method-2-one-workspace-folders-per-department)
  * [Method 3: One Workspace, Folders per Function](#method-3-one-workspace-folders-per-function)
* [Permission System](#permission-system)
* [Step-by-Step Setup](#step-by-step-setup)
* [AI-Powered Team Features](#ai-powered-team-features)
* [What's Next](#whats-next)

***

## Overview

Taskade is designed for teams of any size. This guide covers the different ways to organize your workspace — from small teams to large enterprises — and how AI-powered features amplify team productivity.

> **Genesis hint:** Teams that use Genesis apps can give every department custom internal tools, dashboards, and client portals — all connected to the same Workspace DNA.

***

## Key Terminology

| Term          | Definition                                                               | Analogy                        |
| ------------- | ------------------------------------------------------------------------ | ------------------------------ |
| **Workspace** | Top-level container for folders, projects, and templates                 | Like a company or organization |
| **Folder**    | Container for projects nested within a workspace                         | Like a department or team      |
| **Project**   | Digital canvas for tasks, notes, and collaboration                       | Like a document or whiteboard  |
| **Space**     | Collaborative workspace with sub-spaces (max 2 levels: Root → Sub-space) | Like a team room               |

***

## Workspace Organization Methods

### Method 1: Workspace per Department

Create a separate workspace for each department with function-specific folders.

| Setup                | Detail                                                     |
| -------------------- | ---------------------------------------------------------- |
| **Structure**        | One workspace per department                               |
| **Folders**          | Function-specific folders within each workspace            |
| **Invitations**      | Team members in their respective workspaces                |
| **Cross-department** | Invite members from other departments to specific projects |

**Example:**

| Marketing Workspace | HR Workspace        | Accounting Workspace | Engineering Workspace |
| ------------------- | ------------------- | -------------------- | --------------------- |
| Home (Default)      | Home (Default)      | Home (Default)       | Home (Default)        |
| Meetings            | Performance Reviews | Accounts Payable     | Sprint Planning       |
| Campaigns           | Hiring Pipeline     | Budget Tracking      | Code Reviews          |
| Social Media        | Training            | Invoicing            | QA & Testing          |
| Analytics           | Policies            | Reporting            | Infrastructure        |

**Ideal for:**

* Medium to large organizations
* Specialized, independent teams
* Functional/divisional structures
* Teams with minimal cross-department overlap

### Method 2: One Workspace, Folders per Department

A single workspace with department-level folders.

| Setup                | Detail                                                 |
| -------------------- | ------------------------------------------------------ |
| **Structure**        | One workspace for entire team                          |
| **Folders**          | One folder per department                              |
| **Invitations**      | Each member added to their department folder           |
| **Cross-department** | Easy collaboration — everyone is in the same workspace |

**Ideal for:**

* Small to medium teams (under 50 people)
* Teams with frequent cross-department collaboration
* Startups and growing companies

### Method 3: One Workspace, Folders per Function

A single workspace with function-specific folders (not department-based).

| Setup                | Detail                                                         |
| -------------------- | -------------------------------------------------------------- |
| **Structure**        | One workspace for entire team                                  |
| **Folders**          | One folder per function (Meetings, Operations, Planning, etc.) |
| **Permissions**      | Function-level access control                                  |
| **Cross-functional** | All departments contribute to shared function folders          |

**Ideal for:**

* Cross-functional teams
* Matrix organizations
* Project-based structures

***

## Permission System

Taskade uses a **5-role, 7-tier RBAC** permission system:

| Role             | Capabilities                                                   |
| ---------------- | -------------------------------------------------------------- |
| **Owner**        | Full control — manage workspace, billing, members, all content |
| **Admin**        | Manage members, projects, folders, agents, automations         |
| **Collaborator** | Create and edit projects, use agents, run automations          |
| **Participant**  | Edit assigned tasks, comment, chat                             |
| **Viewer**       | Read-only access to shared content                             |

> Permission inheritance flows: Organization → Workspace → Folder → Project. Members inherit permissions from higher levels unless overridden.

***

## Step-by-Step Setup

### Create a Workspace

| Step | Action                                                      |
| ---- | ----------------------------------------------------------- |
| 1    | In your dashboard, click the **+** icon on the left sidebar |
| 2    | Enter the workspace name                                    |
| 3    | *(Optional)* Choose a workspace logo                        |
| 4    | *(Optional)* Invite team members                            |

### Create Folders

| Step | Action                                                   |
| ---- | -------------------------------------------------------- |
| 1    | Open your workspace                                      |
| 2    | Click **New folder** under Home                          |
| 3    | Enter the folder name                                    |
| 4    | *(Optional)* Choose a folder logo                        |
| 5    | *(Optional)* Share the folder with specific team members |

### Create Projects

| Step | Action                                        |
| ---- | --------------------------------------------- |
| 1    | Open a folder                                 |
| 2    | Click **+ Create new** (top-right corner)     |
| 3    | Type the project title                        |
| 4    | *(Optional)* Share the project to collaborate |

***

## AI-Powered Team Features

| Feature                     | How It Helps Teams                                   | Learn More                                                     |
| --------------------------- | ---------------------------------------------------- | -------------------------------------------------------------- |
| **Taskade Autopilot**       | Generate entire team workspaces from a single prompt | [Taskade Autopilot](/ai-features/ai-features/autopilot.md)     |
| **AI Agents**               | Create specialist agents for each department         | [Custom AI Agents](https://www.taskade.com/learn/genesis)      |
| **Multi-Agent Teams**       | Teams of agents that collaborate (Business+)         | [Multi-Agents](https://www.taskade.com/learn/genesis)          |
| **Automation Workflows**    | Automate cross-department processes                  | [Automation Triggers](/automations/automation.md)              |
| **Genesis Apps**            | Build internal tools and dashboards for teams        | [Taskade Genesis](https://www.taskade.com/learn/genesis)       |
| **Shared Agent Chats**      | AI + human conversations together                    | [Custom AI Agents](https://www.taskade.com/learn/genesis)      |
| **Version History**         | Track all changes across team projects               | [Version History](/taskade-genesis/genesis/version-history.md) |
| **Real-time Collaboration** | Multiple users editing simultaneously (OT-based)     | Built-in                                                       |

***

## What's Next

| Guide                                                                | What You'll Learn              |
| -------------------------------------------------------------------- | ------------------------------ |
| [Taskade Autopilot](/ai-features/ai-features/autopilot.md)           | Auto-generate team workspaces  |
| [Editing & Formatting](/workspaces/workspaces/editing-formatting.md) | Format and style team projects |
| [Embed Taskade](/workspaces/workspaces/embed.md)                     | Share projects on your website |
| [Version History](/taskade-genesis/genesis/version-history.md)       | Track team changes             |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.taskade.com/workspaces/workspaces/teams.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.