Clubs Pipelines For schools Get the app

Clubs · pipelines

One organization, many teams.

A theatre company isn't one group — it's a season, a tech crew, a box office and a board. A pipeline lets you run all of them under one project. Join the umbrella once and its teams start appearing on your deck, while strangers still see only the front door.

free · works today · no setup beyond a few taps

The idea

An umbrella, and teams under it.

The umbrella is a normal project — the one people find and join. Each team under it is also a real project, with its own application questions, its own roster and its own chat. What the link changes is who finds the team and what joining it means.

Who can find it

Each team carries its own visibility, and it's independent of the umbrella's. A club that keeps itself off the deck can still run something it very much wants strangers to find — and vice versa.

What joining gets them

When you accept someone onto a team, they either join that team alone, or that team and the umbrella. Cast in the show, now in the company — or just in the show.

Two settings, set per team, changeable any time. Everything below is one of these two.

Setting one

Who can find a team.

In the app this is the first pill under a team's name.

Members only — default Off the open deck. Appears on the deck of everyone who joined the umbrella. This is the setting that makes a pipeline worth having — a tryout, a trip or the next production reaches your members without reaching the whole app.
Anyone On the deck like a normal project, even if the umbrella is hidden. For the show you're casting from outside, the open workshop, the fundraiser.
Invite only Nobody discovers it — including members of the umbrella. The only way in is a link you send.

The one that catches people out

"Members only" is not private. Every member of the umbrella can see it, which is exactly right for a committee and exactly wrong for an exec board. If a team is meant to be closed even to your own members — officers, a discipline committee, anything discussing people — it needs invite only.

Setting two

What joining a team gets them.

The second pill. One question: does being accepted here also put them in the umbrella?

This team only — default They're added to the team. The umbrella's roster doesn't change. Right when the umbrella is a roster of record — an elected body, dues-paying members, anything where being on the list means something.
This team and the umbrella They're added to both, with both chats. Right when the umbrella is the community and you want everyone who turns up in it.

It only ever adds. Nobody is removed from the umbrella by leaving a team, and turning the setting off later doesn't remove anyone it already added.

Three shapes

What people actually build.

Almost every real organization is one of these, or a mix.

The umbrella

theatre, media, cultural orgs
  • Riverside Drama — auto-join
    • Spring Musical — members only
    • Tech Crew — members only
    • Publicity — members only
    • Exec Board — invite only

Anyone can join the umbrella; the teams are where the commitments live. Turn on "and the umbrella" where being cast should make you part of the company.

The funnel

club sports, robotics, debate
  • Climbing Club — auto-join
    • Competition Team — members only
    • Trip Leaders — invite only

Never gate the front door. The open club is how people find you; the selective team is how you field a squad. Leave the team on members-only — you want the people already in the club to see the tryout, not the whole app.

The season

anything on a calendar
  • Model UN — standard
    • Fall Conference — Sept–Nov
    • Spring Conference — Feb–Apr

One org that never ends, teams that do. Give each a Project Window so the dates ride on the card and nobody applies to something that happened in March.

In the app

Setting one up.

Everything lives in one screen. Open the umbrella project, go to the Members tab, open Pipeline and tap Manage pipeline.

Add a team

+ New team here creates a brand-new project already linked to this one — the parent is filled in for you. Attach existing project takes one of your existing projects and files it underneath instead. Attaching never changes who can already see it.

Set the two pills

Each team shows its current settings — who can find it, and what joining gets them. Tap either to change it. Both are editable forever; nothing here is a one-shot decision made at creation.

Rearrange whenever

↑ Move elsewhere re-parents a team under a different project. × detaches it back to standalone — it keeps its members, its chat and its audience, it just stops being part of the pipeline.

Two things happen on their own

Creating a team posts it into the umbrella's chat, so the people it was made for hear about it in the room they're already in rather than waiting to swipe past it. And from that moment it's on their deck — you don't have to tell anyone twice. Invite-only teams stay silent on both counts, by design.

Worth knowing

Limits and gotchas.

  • Five teams per project. Bigger orgs nest — a team can have its own teams, so a Season team can hold each production. Nesting goes ten deep, which nobody has ever needed.
  • The umbrella needs the best cover. For a stranger it's usually the only one they'll see; a members-only team is invisible until they've joined.
  • Don't make a team out of something that should be a channel. If a group doesn't need its own application and its own roster, it wants a channel inside the club instead. Every team is a separate roster to recruit for and a separate chat to keep alive.
  • Attaching doesn't hide anything. Filing a live project under an umbrella keeps its current audience — it won't vanish off the deck mid-recruitment because you did some organising.
  • Detaching keeps everything. A team that leaves a pipeline keeps its members and chat. A members-only one becomes public, since "members only" has no meaning without an umbrella.