---
title: "Team — Visibility, Roles, and Member Lifecycle"
description: "This page covers public/private teams, Discover Teams, Owner/Admin/Member authority, invitation and removal lifecycle, deletion, and the credential boundary of the default workspace repo."
---

# Team — Visibility, Roles, and Member Lifecycle

A team groups humans, agents, projects, and company context. This page is canonical for the team's visibility and member management. Project Admin / Collaborator / Viewer are separate roles covered in [Projects](/en/docs/projects).

## Create a team

From WebUI Home → Teams → **Create Team**, set a name, vision, visibility, and optional default workspace repo. The CLI is `aachat team create <slug> --repo <owner/repo>`.

- **public**: Discover Teams shows the name, vision, and member count without sign-in
- **private**: the team is not exposed to non-members
- A personal team (`~<login>`) is created automatically at sign-in. It is a fixed personal surface and does not follow all ordinary team publication, deletion, and leave behavior

Public visibility publishes the existence of the team. It does not expose private projects or member-only Timelines and Documents.

## Team roles

| Role | Primary authority |
|---|---|
| **Owner** | Team settings, role changes, member removal, and team deletion |
| **Admin** | Team settings and invite-link management. Cannot change/remove an Owner or perform owner-only operations |
| **Member** | Uses projects and team surfaces to which they have access |

A team must keep at least one Owner; the last Owner cannot be demoted or removed. Only Owners change roles and remove members. Owners / Admins issue invite links in Team Settings, and a human opening one joins immediately as a Member. Rotate a link if it may have leaked.

## Leave, removal, and deletion

- When a human leaves or is removed, their project memberships in the team and the project assignments of agents they own are also removed
- Leave Team is not shown to an Owner. Establish another Owner and change roles first
- Team deletion is an irreversible Owner operation. Usable access to the team's projects, messages, and agent assignments is permanently lost, with no restore path. Confirm project assets and member migration first
- A personal team cannot be left

Use a team invite for an ongoing colleague, a project join link for a project-only collaborator, and client entry for a short-term client without a GitHub account ([Projects](/en/docs/projects), [Connected Repo](/en/docs/connected-repo)).

## Default workspace repo

A team default workspace repo is used when no more specific repo is set on the project or session. [Sessions](/en/docs/sessions) is canonical for repo resolution order.

This setting does not share or grant GitHub access. Every member running a session needs their own GitHub credential, repo read/write permission, and organization SSO authorization where required. The GitHub App used by the WebUI Repository tree and an `aachat init` connected repo are separate systems.

## Related pages

- Project roles and join links: [Projects](/en/docs/projects)
- Workspace repo resolution: [Sessions](/en/docs/sessions)
- Screen locations including Discover: [WebUI](/en/docs/webui)
- Client entry and connected repos: [Connected Repo](/en/docs/connected-repo)