Teams

What a team is

A team sits between your organization and its products, and owns the products assigned to it. Without teams, your organization owns every product directly.

Whoever owns a product, one person answers for it: the product's Accountable owner. An item added under a team's product, with Same as the parent as its Owner, is owned by the team too.

A team's members are the people and agents who hold a role at the team. A role held there covers every product the team owns, and the team's page lists its members with their roles. A team of one is enough. See People and access.

Off by default

A new organization starts with teams off. While they're off, every product belongs to the organization, and BLOM shows no team anywhere:

• The screen that lists the organization's products by owner is titled Products. With teams on, it's Teams and products.
• Atlas View has no Team filter and no Teams count.
• Product View's Switch product lists products without grouping them by team.
• Add a product doesn't ask who owns the new product: the organization does.

Turn teams on or off

Only an Administrator can change the setting. Everyone else sees it on Settings with Only an Administrator can change this.

1. Open Settings

   Select Organization at the foot of the rail, then Settings.

2. Find the Teams card

   It shows the setting as it is, such as Now: Off, beside BLOM's default, Off.

3. Change it

   Select Turn teams on, or Turn teams off. BLOM confirms with Teams are on. or Teams are off.

BLOM records each change in the organization's history, with who made it and when.

What changes with teams on

• Teams and products lists each team with the products it owns, by Number, Product, Accountable owner, and State, then the products the organization owns directly.
• Atlas View adds a Team filter beside Product, Initiative, and Owner, and a Teams count on its Hierarchy tile. Its map groups products under the team that owns them.
• Product View's Switch product lists the products you may see by team.
• Once your organization has a team, Add a product asks who owns the new product, under Owned by: the organization directly, or one of its teams.
• Once your organization has a team, an agent's delegation can reach A team, as well as the organization or a product.

Add, rename, and remove a team

An Administrator manages teams on Teams and products. BLOM records each change with who made it, when, and why.

• Add a team creates a team with the name you give it. No other active team in the organization may have that name, whatever its letter case. Adding a team moves no product and changes no task or PDLC.
• Rename, on a team's row, renames it. The team keeps its products and its members, and its earlier name stays in its history.
• A team that owns no product can be removed. While it owns one, BLOM refuses and names each product to move first. A removed team's PDLC versions pass to the organization, and the tasks that recorded them keep them.

An Administrator can also rename the Team level for the whole organization, such as to Department and Departments. BLOM then uses that word wherever it names the level, and no owner, member, or role changes.

Move a product to another team

An Administrator moves a product into a team, out of a team to the organization, or from one team to another. Before the move, BLOM shows what it touches: the product's owner, who gains or loses access, and the PDLC that covers its new work.

The product keeps its number, its tasks, its documents, and its history. Open tasks keep the PDLC version they recorded, and new tasks follow the new owner's PDLC. BLOM refuses a move into a team that has no PDLC version, and names what's missing.

Related