Team

The headline first, so you don't hunt for it later. In Lighter the team is teamlead-only. A team admin gets the full console; a plain member gets nothing — they don't even have a «Team» item in the menu. This is a deliberate decision, not a missing feature: on the platform most members have no team-level access anyway, so we didn't draw them half a broken screen. They just work, and their stats roll up to the teamlead.

The three screen states

What you see at /app/team depends on who you are:

1. No team → the «Create or join» screen.
2. You're an admin / owner → the full team console.
3. You're a plain member who hit the URL directly → a short notice, and nothing else.

One at a time.

State 1 — No team: create or join

If you're not in any team yet, the screen offers two cards.

• Create a team. A Name field → the Create button. You become the owner of a new team. (This card is hidden if team creation is disabled network-wide — then only joining remains, with an explanatory note beside it.)
• Join a team. Someone sent you an invite — paste it here. The form accepts either a full invite link of the form gang-join/{id}/{key}, or a separate team id and key. The Join button.

Workflow 1 — Create a team

1. Open «Team». With no team, the item is visible to whoever is allowed to create or join.
2. Type a name. In the Create a team card, enter a Name.
3. Hit «Create». Done — you're the owner, and the screen reloads into the full console.

Workflow 2 — Join by invite

1. Get an invite. Your teamlead sends an invite link gang-join/{id}/{key} (or the id + key pair).
2. Paste the link. Paste the whole link into the Join card's field — the id and key are extracted for you. Or enter the id and key separately.
3. Hit «Join». The key is checked server-side; if it matches, you're in.

State 2 — The team console (admin / owner)

The full console. A team card up top, a members table below, an invite panel and a «danger zone» to the side/below.

Team card. The team name and a Settings button — Settings edits only the name and description. Nothing else: Lighter carries no team visibility flags (see the gotchas below).

Members table. Columns: # · name · email · Role · contacts · stats → · actions.

• Role renders as two values: Owner (the boss) with an Admin tag, or Member.
• Badges: «You» on your own row, «Owner» on the team creator's row.

• Row actions (admin only): a role toggle (make admin / remove admin) and Kick. Both are disabled on the owner's row and on your own row.
• stats → leads to that member's stats (team data, see Workflow 6).

Invite panel.

• Shows the join URL gang-join/{id}/{key} and a Copy button — after copying, a «Copied» toast pops up.
• A Reset key button — generates a new key. Confirm: «Reset the invite key? Old links will stop working.»

Danger zone. A Delete team button with a hard confirm: «Delete this team for everyone? This action is irreversible.» Deletion removes the team and detaches all members.

Workflow 3 — Invite to the team

1. Open the «Invite» panel.
2. Hit «Copy». Next to the gang-join/{id}/{key} link — you'll see a «Copied» toast.
3. Send the link. Pass it to the new cat any way you like. They paste it into their Join card (Workflow 2) — and they're in the pack.
4. (As needed) Reset the key. An old link leaked — hit Reset key, confirm «Reset the invite key? Old links will stop working.». The key rotates, every old link dies, so copy the new one.

Workflow 4 — Manage members

1. Find the member's row in the table.
2. Make admin / remove admin — click the row's role toggle. The role flips between Member and Admin.
3. Kick — click Kick, confirm «Kick <name> from the team?». The member loses the team (their user_gang is zeroed), but their account stays intact.

Workflow 5 — Rename the team

1. Click «Settings» in the team card.
2. Edit the «Name» (and, if you like, the Description).
3. Save. The header updates immediately; the edit round-trips to the same classic team backend.

Workflow 6 — View team data

1. Drop into a member. In their row, click stats → to reach their numbers.
2. See team-wide data in the reports. Team-wide stats live in Reports and Conversions — flip Scope there to Team, and the stats aggregate across the whole pack.

State 3 — Plain member (direct URL only)

You're a plain member. You have no «Team» item in the menu — the only way to reach this screen is by typing the address by hand. You'll then get a short notice along the lines of «You're in a team — it's managed by your teamlead», and that's all: no member list, no team data, no «Leave» button.

Good to know (the gotchas)

• Exactly two role levels: admin and member. Nothing sits between them. Don't look for «access levels» — the platform doesn't have any.
• The owner is untouchable. The boss can't be kicked, demoted, or forced to leave — only the whole team can be deleted.
• You can't touch yourself either. The role toggle and Kick are disabled on your own row.
• A member doesn't self-leave. Lighter has no standalone «Leave» — only via the teamlead or the classic /gang.
• The four team visibility flags (home / users / stats / filter) aren't in Lighter. The whole visibility-settings block is dropped — those flags stay under the classic /gang, and Lighter never touches them.
• The invite link is the classic route gang-join/{id}/{key}, not some /app/ path. It works for any cat regardless of which interface they use.
• Resetting the key breaks old links. After Reset key, every previously-sent invite stops working — be sure to hand out the new link.

Coming from your old tracker

This is your old tracker's «Team» — the same users under one team. The invite link is the same team invitation you're used to. The difference is honesty: we don't draw members control panels they don't actually run — the teamlead steers the team, and the pack just catches profit.