> ## Documentation Index
> Fetch the complete documentation index at: https://help.qrtub.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Team Overview

> The container that owns every Collection, Item, Link and print batch in QRtub — where teams come from, who can belong to several, and what only the owner controls

A team is the container that owns your QRtub data. Collections, Items, Links, reserved numbered
patterns, page templates, print batches and Media all belong to a team, not to a person — which
is why two people on the same team see exactly the same Collections and the same pool of Links.

Every team also holds its own member list and its own subscription. Nothing is shared between
two teams: a Link created in one team cannot be assigned to an Item in another, and a plan bought
for one team does not cover the other.

## Where your team came from

Most teams are created one of three ways:

* **Automatically, at signup.** Creating a QRtub account creates a team named after your email
  address — `jane's Team` for `jane@example.com` — with you as its owner.
* **By you, deliberately.** Use **Create Team** in the team switcher at the top of the left
  sidebar. See [Creating a Team](/team/create-a-team).
* **By someone inviting you.** If you signed up by clicking a team invitation, no personal team
  is created for you at all. You land straight in the team that invited you.

You can belong to as many teams as you are invited to, and switch between them at any time. Only
memberships you have actually accepted count — see
[Switching Between Teams](/team/switching-teams).

## What only the owner can do

Every team has exactly one owner: the person recorded as its owner, which starts out as whoever
created it. The owner is the only member who can change the team's name, slug or logo, invite or
remove members, manage pending invitations, see the Subscription section, or delete a Collection
or an Item. Everything else — creating Collections and Items, editing fields, creating, editing
and deleting Links, building Pages, running print batches, importing and exporting CSVs — every
member can do. Details in [Team Roles](/team/roles).

## The Team page

Open **Team** in the left sidebar. The header shows the team's logo, name, slug and member count,
with an **Edit** button for the owner. Below it, four tiles: **Members** (accepted members),
**Pending** (invitations sent to people without a QRtub account), **Owners** and the date the team
was created.

Then the members table — **People with access**, **Last Seen**, **Status** and **Access** —
followed by a **Danger Zone** with the **Leave Team** button. One thing worth knowing about that
table: the **Last Seen** column does not track activity. It shows when the person joined the team,
or when they were invited if they have not joined yet. Nobody's last sign-in or last edit is
recorded anywhere in QRtub.

## Related

* [Switching Between Teams](/team/switching-teams)
* [Team Roles](/team/roles)
* [Inviting Team Members](/team/invite-members)
* [What Is a Collection?](/collections/overview)