Teams
Teams let people at the same company share visibility into each other's bins. One team maps to one company workspace; a user belongs to at most one team at a time (active or pending).
Create a team
Go to Teams in the console and enter a company or team name. Whoever creates the team becomes its leader: they manage membership, can rename or delete the team, and configure company storage. The name is the only required field — there is no domain verification or SSO in the beta, so the name is self-declared.
Finding your company's team
If your account email uses a company domain, the Teams page may suggest an existing team: "People at your email domain already have a team." The match is based on the email domain of the person who created the team.
Two things to know about this suggestion:
- It is a discovery hint only, never an access control. Seeing the suggestion does not grant access, and not seeing it does not block you — anyone can request to join any team, and every join goes through leader approval regardless of email domain.
- Public email providers (gmail.com, outlook.com, yahoo.com, icloud.com, protonmail.com, and similar) are excluded from matching, so a personal-email account never suggests, or is suggested to, an unrelated "team" of strangers.
Joining: request, then approval
There are no direct invites in the beta. Joining is always request-then-approve:
- You request to join a team (from the suggestion, or after being told the team exists).
- Your request shows as pending — "Your request to join {team} is awaiting approval." While pending, you have no visibility into the team or its bins.
- The team's leader sees the request in their leader panel and approves or denies it. A denied request simply disappears; you can request again later. Someone previously removed from a team can also request to rejoin.
Roles
There are two roles: leader and member. Each team has one leader — the person who created it.
Leaders can:
- approve or deny join requests
- remove members
- rename the team
- delete the team
- configure company storage (see company storage)
- see team stats with a per-member breakdown
Members can see the team's member list, team-scoped bins, and team stats aggregates — but never per-member breakdowns; that boundary is enforced at the API level, not just hidden in the UI.
The leader cannot leave or be removed. If a team should no longer exist, the leader deletes it. There is no leadership transfer in the beta.
Team-scoped bins
A bin can be filed under your team when you create it. Team-scoped bins are visible to every active member of the team; personal bins stay personal.
Visibility is read-only for teammates: they can open a team bin, see its runs, manifests, and files, but only the bin's owner can edit the spec, mint collection links, archive, or delete it. Teammate-owned bins show "Owned by {email}" in the bin list.
A bin's team scope is set at creation and cannot be changed afterwards in the beta.
The MY / TEAM toggle
When you are on a team, the console's stats band shows a MY / TEAM toggle. MY shows your own bins and stats; TEAM shows the team's bins and aggregate stats. The toggle drives both the stats band and the bin list below it — they read the same scope, so the console always shows one consistent view.
Leaders in team scope get an additional "Show per-member breakdown" control (bins, storage, last active, per member) and a pending-requests indicator.
Leaving and removal
When a member leaves a team, or a leader removes them:
- Team-scoped bins they created stay with the team. Remaining members keep visibility; the departed person still owns those bins and sees them as personal bins.
- Their personal bins are untouched.
- Active collection links are unaffected. Tokens belong to bins, not memberships — a customer mid-collection notices nothing.
- They can request to join a team again later.
Deleting a team removes members' access immediately. Bins filed under the team are not deleted — they are un-scoped back to personal bins, still owned by whoever created them.