> For the complete documentation index, see [llms.txt](https://docs.tiny.plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tiny.plus/guides/admin/teams.md).

# Teams

Group your people into studios, offices or sectors, and give each one its own pipeline, news feed, reports and permissions.

A **team** is a group of people who work together: a studio, an office, a sector group. Once your firm has teams, each project, company, contact and event belongs to one. Each team gets its own page, pipeline, news feed and reports, and your settings decide what the people on a team may see and change.

Teams are part of the Pro plan. An account admin turns them on and sets them up under **Account Settings -> Teams**.

{% hint style="info" %}
"Team" means a few things in tiny+. **Team Members** are everyone with a login. A project's **team** is the people linked to it. **Bid teams** are the firms bidding together on a tender. This guide is about the groups your people work in, which your firm can call by its own word.
{% endhint %}

## Turning teams on

Open **Account Settings -> Teams** and press **Turn on teams**. Under **Your word for a team**, say what your firm calls them: studio, office, sector. tiny+ uses your word everywhere: "My studio" on the board, "Sydney studio" on a record.

Turning teams off later hides them without deleting anything. Turn them on again and everything comes back as it was.

## Making teams and seating people

Press **Add** with a name to make a team. Each team is a row: open it to give it a colour and a description, and to add its members.

* **Members.** Add a team member, and they appear as a chip. A person can be on any number of teams.
* **Leads.** Click a member's star to make them a lead. What a lead may do is set under Users (see Permissions).
* **Home team.** Each person has one home team, shown by the house. Their work counts for it: a record assigned to them belongs to their home team unless someone sets another. A person's first team becomes their home team. Click the house on another chip to move it.
* **Team members can join by themselves.** With this ticked, anyone can join the team from its page, and leave it. Without it, only an admin seats people.

Already tag your people by office or studio? **Start from a category** makes a team for each tag in a team-member category and seats everyone tagged.

New accounts can also name their teams during setup.

## A record's team

A record's team is the one set on it. If none is set, it's the home team of the person it's assigned to. Reassign a project and it moves to the new person's team. Nobody has to keep the team up to date by hand.

When the work belongs elsewhere, set the team on the record. On add and edit forms, the **Team** field comes right after **Assigned to**. Choose a team to set it, or **Follow the owner** to go back to the owner's home team. Companies and contacts can belong to more than one team: tick the others under **Also**. A client that two studios both work with belongs to both.

The record's page shows its team in the banner, under the person it's assigned to, with where it came from: "set on this record" or "from the owner".

## Permissions

Four settings under **Account Settings -> Users** say what a team gives the people on it. Each one only adds to what people could do before. None takes anything away.

* **Team-mates edit together.** The people on a record's team can edit and delete it as its owner can.
* **Team leads own their team's records.** A lead can edit any record on their team and open its confidential ones. This is on unless you turn it off.
* **Confidential records are open to their team.** A confidential project normally opens only to the people named on it. With this on, a new confidential project also opens to its team. Each project can say otherwise under **Who can see it**.
* **Project pipeline** and **Client pipeline.** Each pipeline can reach a person's **Own records**, their **Own team**, or the **Whole firm**. With Own team, the pipeline board gets a button for each team a person is on, between Mine and Everyone, their home team first.

## Reports

* **Table and chart reports** can group, sort and filter by team, and split a chart by it.
* **Built-in reports** offer each team in the **Person or team** choice. A lead can choose their own teams. With the pipeline at Own team, anyone can choose the teams they're on, and their home team is where the report opens.
* **Pipeline Trend** and **Pipeline Analysis** can split by team, and **Client Coverage** shows each company's team.
* **Scheduled reports** can cover a team's work and go to the team's members or leads, or be posted to its news feed.

The team's page opens with its numbers: members, open proposals with their fees, active projects, companies, contacts and open tasks. Each one links to the matching list, filtered to the team.

## The news feed

Every team has its own news feed. Members follow it automatically.

* **The strip over the News Feed.** It holds News Feed, Followed by you, each team you're on (your home team first), and your channels, with the rest under More. Choose one and the posts change in place. The post box then posts to that team or channel. tiny+ remembers your choice for next time.
* **What a team's feed holds.** It has posts made to the team, and posts about the projects, companies, contacts and events on it.
* **@mentions.** Type @ and a team's name to mention everyone on it.

## Defaults

Open a team's row and choose **Defaults for new records**. These pre-fill what its members add:

* tags for each record type;
* the currency, where your account has several;
* which team the new record belongs to, for a team that adds work for others.

The person adding can change any of them before saving.

## Lists, reports and automated actions

* **Lists and saved reports** can be shared with one team. Set **Visibility** to **A team** and choose the team. Only the list's maker and the people on that team see it.
* **Automated actions** can test **Team** (the record's team, or a change to it) and **Assigned to someone on**. They can also set a record's team, **Assign to the lead of its team**, post to its team's feed, and email everyone on its team or its leads.
* **Imports** can set each record's team from a **Team** column, by the team's name.

## Turning teams off

Press **Turn off teams** on the Teams screen. Records keep their teams and people keep their places, out of sight. Lists and reports shared with a team are then seen only by the people who made them. Nothing else changes until you turn teams on again.