> For the complete documentation index, see [llms.txt](https://swu-forge.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://swu-forge.gitbook.io/docs/teams/team-folders.md).

# Team Folders

Team folders are a shared workspace for everyone on a team. When a folder is marked as a team folder, every team member gets visibility (and, depending on their role, edit rights) on the decks inside it. Subfolders inherit the team scope from their parent.

## Naming your team

Every team name is unique. When you create or rename a team, extra spaces at the start and end are removed and double spaces between words become single spaces. If another team already has that name — even with different capitalization, like "Rebel Cell" vs "rebel cell" — you'll see "A team named … already exists" and need to pick something else. A team also can't share a name with another player's username, so nobody can mistake a team for a person. Naming a team after your own username is fine, and so is changing only the capitalization of your team's name.

## What team members can do with team decks

Team members can operate on decks that live in their team's folders, with limits scaled to their role:

| Action                                                            | OWNER | ADMIN | EDITOR | VIEWER |
| ----------------------------------------------------------------- | :---: | :---: | :----: | :----: |
| Read the deck (view, export, JSON, proxy PDF, share image)        |   ✓   |   ✓   |    ✓   |    ✓   |
| Edit a deck **you created** (cards, rename, format, notes)        |   ✓   |   ✓   |    ✓   |    ✗   |
| Change the **cards** in a deck a teammate created                 |   ✓¹  |   ✓¹  |   ✓¹   |    ✗   |
| Rename / reformat / re-note a teammate's deck                     |   ✓   |   ✓   |    ✓   |    ✗   |
| Manage versions and branches                                      |   ✓   |   ✓   |    ✓   |    ✗   |
| Move a teammate's deck between **this team's** folders            |   ✓   |   ✓   |    ✓   |    ✗   |
| Move a teammate's **sym-linked** deck between this team's folders |   ✓   |   ✓   |    ✗   |    ✗   |
| Make the deck linkable (enable/disable its public link)           |   ✓   |   ✓   |    ✓   |    ✗   |
| Delete the deck (removes **all** members' recordings on it)       |   ✓   |   ✓   |    ✓   |    ✗   |
| Add the deck to public browse/search lists                        |   ✓   |   ✓   |    ✗   |    ✗   |
| Create a team folder (or promote your own folder into the team)   |   ✓   |   ✓   |    ✓   |    ✗   |
| Rename / move a team folder                                       |   ✓   |   ✓   |    ✓   |    ✗   |
| Delete a team folder                                              |   ✓   |   ✓   |    ✗   |    ✗   |
| Demote a team folder back to personal                             |   ✓   |   ✗   |    ✗   |    ✗   |

A per-folder VIEWER override locks a member to read-only on that one folder, regardless of their team-wide role.

### Contributors (content creator teams)

Teams run by a content creator have one more role, **CONTRIBUTOR**. It's what subscribers get when they join a creator's team through Discord. A contributor can do everything a viewer can, and can also share **their own decks** into the team's folders:

* **Share a deck:** choose **Create sym link** on one of your decks and pick the team folder. The deck appears there for the whole team, and it stays yours. You keep editing it as usual, and everyone else on the team can only view it.
* **Take it back out:** choose **Remove sym link** on the deck in the team folder. Nothing else changes, and no games or replays are lost.
* **What a contributor can't do:** edit, move, rename or delete anyone else's decks, or create, rename or move the team's folders. You also can't move a deck's home into a team folder. Sharing is always by sym link, so the deck stays yours.

Team **owners and admins** can remove any shared deck from the team's folders. On the team's **Decks** page, use the ✕ next to the deck. On **My Decks**, choose **Remove from team folder** from the deck's menu. This only takes the deck out of the team. It stays with the member who shared it.

A per-folder VIEWER override turns a contributor into a viewer on that folder, which is how a creator keeps a curated folder off-limits.

A teammate's deck always stays in its team. You can move it to another of the team's folders, but not into a different team or into your own personal folders. Only the person who created it can take it somewhere else.

¹ **Changing the cards in a deck someone else made is off by default.** A team owner or admin can turn it on with **Let members edit each other's decks** in team settings. While it's off, a deck's card list can only be changed by the person who created it — everyone else (even admins) is limited to viewing, renaming, tagging, and recording against it. See [Editing a teammate's deck](#editing-a-teammates-deck) below.

Battle Log access on a team deck doesn't require any extra permission — being a team member is enough.

When you open a team deck, a **Team decks** link in the deck's actions (next to **Create sym link** and **Move to folder**) takes you back to your team's Decks page.

## Editing a teammate's deck

By default, only the person who created a deck can change its cards. A team **owner or admin** can loosen this from **Team → Settings → Deck editing** by turning on **Let members edit each other's decks**. Once it's on, anyone with an Editor role or above can edit any team deck's cards, not just their own.

With it turned on, the **Edit Deck** button appears on a teammate's deck just like on your own — open it in the Workshop or Browse view, add, remove, or swap cards, and save. Your changes update the shared team deck in place; you don't get a personal copy. (Prefer to work on your own version? Use **Clone deck** to duplicate it into your personal decks first.)

> **Heads up when the deck isn't yours.** Opening a teammate's deck shows a warning banner across the top of the builder. Because a shared team deck can be linked into Karabast, a teammate might be in a live game with it at the moment you edit — and saving a changed list can cost them that game. If you're not sure, clone the deck and edit your copy, or check with the owner before saving. This is exactly why the setting is off until a team decides to enable it.

## Linking and recording on a team deck

Team decks **are** linkable. Any EDITOR (or above) can enable a team deck's public link; once it's on, the **decklist** is viewable and importable by anyone with the URL — that's how teammates pull a shared deck into Karabast to record against it. What stays private is the *battle log*: a team deck's matches and replays are **never** world-public (the "make match public" control is hidden for team decks), so your team's games and tech don't leak through a shared replay link. Team decks also stay out of public browse/search directories — the link shares the list by URL only.

Recording on a shared team deck is **membership-gated, not ownership-gated**: once the deck is linkable, *any* team member — including a VIEWER — can record games against it directly, without copying it into their own collection. Every member's games attach to the same team deck and show up under that deck's Battle Log, attributed to whoever recorded them (see the per-user tabs in [Battle Log](/docs/battle-log/battle-log.md)). They also roll up into the [team battle log](/docs/teams/team-battle-log.md) archetype stats.

> Deleting a team deck removes **every** member's recordings on it, not just yours. EDITOR and above can delete, behind a type-the-deck-name confirmation.

## On the My Decks page

Once you're a member of at least one team, the **My Decks** page grows a scope filter strip at the top with chips for **All**, **Personal**, and each team you belong to. The strip is hidden if you're not on any teams.

* **Team folders** in the sidebar display the team's photo (or first-letter avatar) next to the name. A lock icon appears next to the name if your role on that folder is VIEWER or CONTRIBUTOR (hover it: for a contributor it says you can still add your own decks).
* **Team decks** in the deck list show a small team badge after the format badge.
* **Rename folder** appears on folders you can write to (EDITOR or above on a team folder, or any personal folder you own); a VIEWER role — including a per-folder VIEWER override — hides it. **Delete folder** is more restricted — it only appears for OWNER/ADMIN (or any personal folder you own).
* **Folder right-click menu**: right-click (or long-press) a folder for its actions — **Rename**, **Delete**, and the scope moves below. The available items depend on your role and the folder's scope.
  * **Move to …** (promote) shows on a **top-level personal folder you own**, with one entry per team where you're EDITOR or above. It moves the folder and everything inside it into that team.
  * **Make personal** (demote) shows on a **top-level team folder** when you're the team **OWNER**. It pulls the folder's whole subtree back into your personal decks and clears per-folder overrides.
  * Promote/demote are offered only on **top-level** folders so a moved folder never ends up parented under a folder in the other scope.
* **Move to folder…**: from a deck's **More actions** menu or its right-click menu, pick any team folder you have write access on. For your own decks the list also includes **Top level** and your personal folders. For a teammate's deck, the list only shows that team's folders.
* **Drag-and-drop**: you can drag your own decks into any team folder you have write access on. Folders with a VIEWER role refuse drops with a red border. Cross-scope folder moves (e.g. dragging a personal folder onto a team folder) are blocked — use the right-click **Move to** / **Make personal** actions instead.
* **Reordering folders**: drag a folder onto the thin line *between* two sibling folders to set a custom order (dropping a folder *onto* another folder still re-parents it). **Personal and team folders never intermingle** — you can reorder within the Personal group and within each team's group, but a folder can't be dropped into the other group's order. Reordering needs write access (a VIEWER can't reorder), and is paused while a search/filter is active. **A team's folder order is shared** — one canonical order every member sees; your personal folder order is your own.
* **Sections (Created by me view)**: **Created by me** — the first item in the left sidebar — is the only view that shows personal and team folders together, so it groups them under labeled section headers — **Personal** first, then one per team (header = the team name, with the team photo and a lock if you're a VIEWER). Headers aren't folders: you can't rename or delete them, and a team section is renamed only by renaming the team. The Personal / single-team scopes show one group with no header.
* **New folder** input creates a folder under the active scope. New folders land at the end of their group.

## On a team's Decks page

Each team has its own Decks page that lists every deck filed in the team's folders as a tree. Each folder with contents has a **chevron** to collapse or expand it (folders start expanded), and the header has **Expand all** / **Collapse all** buttons to toggle the whole tree at once.

A **trophy** next to a deck's name marks it as the **top performing version of its archetype** — the deck with the best win rate (min 10 decided games) among every team deck sharing that leader + base. If two members keep separate lists of the same archetype, the trophy points to the one that's actually winning. See [Top decks](https://github.com/acousineau/swu-deck-visualizer/tree/main/docs/howto/team-top-decks.md) for how the ranking works.

## Concepts

* **Promote**: turn a personal folder into a team folder. The folder and every descendant become team-scoped. Only the folder's current owner can promote it.
* **Demote**: pull a team folder (and its descendants) back into personal scope. The whole subtree gets re-homed under the team owner's personal tree, and any per-folder overrides on the subtree are deleted. Only the team **OWNER** can demote.
* **Per-folder override**: replaces a member's team-wide role for one specific folder. Lateral or downward only — you cannot give an EDITOR an ADMIN override.