Teams
A Plyloft team is a private GitHub repository that holds the member list and the shared library. Your code, the board and the skills stay on GitHub; Plyloft’s server only checks who holds a seat.
The owner buys the seats, from 2 to 50, and holds one of them. Each of the others goes to a teammate’s GitHub account. A teammate has Team, Pro included, while they hold a seat and are signed in to Plyloft with that same GitHub account (your Plyloft account is your GitHub sign-in). Teammates don’t buy anything.
Seats are changed in Manage subscription on your account page: added seats are charged pro rata straight away; fewer seats take effect at renewal, and never below the number of seats people hold. Prices include VAT.
Join or create a team
Section titled “Join or create a team”- Turn on Work with a team in Settings › Account › Setup (during the first setup, choose With a team). Then open Settings › Team and press Join or create a team.
- To create one, choose Create a team and fill in the Team name and the Repository (private, on GitHub; Plyloft suggests a name). You are its owner.
- To join, choose I have an invite code, or pick the team under Teams that invited you. Setup shows what joining grants before anything happens, then clones the team’s projects into your projects folder.
Invite people
Section titled “Invite people”In Settings › Team › Members and library, press Add somebody and type a teammate’s GitHub login. Check access lists exactly what Plyloft would grant (push access to the team repository and each team workspace) before you press Send invites. Then the page says: Invitation sent to alice. They accept it on GitHub, then join from Plyloft. You can also Copy invite and send the code yourself; it carries no secret.
Give the team a workspace
Section titled “Give the team a workspace”Under Give the team a workspace, the owner adds a repository from this computer’s workspaces (or another one by name). It joins the team’s manifest, and every member can open it from their own Plyloft. Press Check access on each existing member so GitHub lets them into it.
Remove someone
Section titled “Remove someone”The owner opens Settings › Team › Members, the member’s ⋯ menu, and Remove from team…. It removes their GitHub access to the team repository and the team workspaces, and updates the member list. Cards they claimed stay assigned to them until someone reassigns them.
What a team shares
Section titled “What a team shares”- A board on GitHub Issues. The team’s workspaces keep their board on GitHub Issues, so tiles carry the issue number (Ready to start · #21). A card a teammate took reads Claimed by alice · #21 on your Board, and your own reads Claimed by you. Start build on someone else’s card asks Already claimed by alice. Claim it too?, with Cancel as the default, and names their open pull request when Plyloft knows it.
- Skills. Promote to Team and the skill loads in every member’s Claude and Codex sessions. It shows under In the team library in Library › Skills.
- Overlapping edits. Before you ship, the result warns Overlapping edits · Shipping both may conflict on: and names a teammate’s open pull request and the files, for example PR #23 · Rate limits · src/api/limits.ts.