Complete guide to creating and managing teams in YAPL for effective collaboration.

Team Management

Teams are the organizational foundation of collaboration in YAPL. They group members together and control access to projects and resources through role-based permissions.

Understanding Teams

Teams provide:

Member Organization - Group users with shared responsibilities
Access Control - Determine who can view and edit projects
Role-Based Permissions - Define what members can do (Lead, Member, Viewer)
Project Assignment - Connect teams to projects they work on

Team Architecture

Workspace
├── Workspace Owners Team (system-generated)
│   └── All workspace owners
├── Engineering Team (user-created)
│   ├── Members with roles
│   └── Assigned projects
├── Operations Team (user-created)
│   ├── Members with roles
│   └── Assigned projects
└── More teams...

In This Section

Getting Started

Creating Teams - Set up new teams in your workspace

Roles & Permissions

Team Roles - Understanding Lead, Member, and Viewer roles

Member Management

Managing Members - Add, remove, and update team members
Team Invitations - Invite users to join teams

Project Access

Team Assignments - Connect teams to projects

Quick Reference

Task	Location
Create team	Teams > Create Team
Invite member	Teams > [Team] > Invitations
Change role	Teams > [Team] > Members
Assign to project	Projects > [Project] > Team Assignment
View team activity	Teams > [Team] > Activity

Team Types

Regular Teams

User-created teams for organizing work:

Customizable name and description
Manageable membership
Assignable to projects
Can be deleted

System Teams

Automatically created and managed:

Workspace Owners - Contains all workspace owners
Updates automatically
Cannot be modified or deleted
Provides owner access to all content

Roles Overview

Role	Description	Key Permissions
Lead	Team administrators	Manage members, assign items, full edit
Member	Standard participants	View and edit team content
Viewer	Read-only access	View team content only

Best Practices

Team Structure

Create teams based on function (Engineering, Operations)
Or create teams per project for dedicated access
Use a hybrid approach for flexibility

Role Assignment

At least one Lead per team (required)
Assign Member role for active contributors
Use Viewer for stakeholders who need visibility

Project Access

Assign teams thoughtfully to projects
Review assignments when projects change scope
Remove teams when access is no longer needed

Inviting Team Members - Getting started guide
Project Management - Working with projects
Managing Owners - Workspace administration

Was this page helpful?

Teams

On this page