Skip to main content

Teams

A Team lets you share a Marquee with other people. The owner shares a host; accepted members launch on it as if it were their own.

Team management is web-only. The API, CLI, and MCP tools do not manage teams, but existing Marquee and Playground operations honor accepted team access.

Creating a team may require the collaboration preference. Accepting an invitation and using a shared Marquee do not. See Feature Preferences.

Roles​

  • Owner: creates the team, invites and removes members, changes member roles, transfers leadership, shares and unshares Marquees.
  • Admin: uses shared Marquees and can leave the team. Admin is a role value today, not a membership-management grant.
  • Member: accepts the invitation, uses shared Marquees, and can leave the team. Members can't invite people or change team membership.

Only the owner can share resources into the team.

The creator is the owner, and ownership only moves through Transfer leadership. Transfer leadership to another accepted member before leaving; the new owner is promoted and the previous owner becomes an Admin. A team can be deleted only after every other member has left or been removed.

The owner can assign Member or Admin. Only a leadership transfer changes the owner.

Invitations​

The owner invites people by username or GitHub handle. Invitations remain pending until accepted or declined and do not expire automatically. An invite for a future user attaches when they register with that username. Declined invites can be sent again.

What sharing a Marquee means​

Sharing grants management access; there is no read-only role. A shared Marquee appears beside the member's own and works for launches, templates, CI, and schedules.

  • Playgrounds on a shared Marquee are shared in practice. Everyone who can manage the Marquee can see and manage the Playgrounds running on it: the host is shared capacity, not isolated per member.
  • Other resources are not implicitly shared. Members still need their own Playspecs, Props, Agents, and Secrets. A shared Marquee doesn't expose the owner's private resources, and a member's Genie chats stay theirs.
  • Names collide across members. Subdomains are unique per Marquee across everyone's Playgrounds. Raw Docker host ports collide only when a template explicitly opts into preserving Compose ports: or when a launch provides explicit port mappings; by default Fibe strips local-only Compose host bindings.

Funding​

There is no team wallet. The owner funds the Marquee, and an unfunded Marquee blocks the owner and members alike with MARQUEE_NOT_FUNDED. See Billing: When your balance runs low.

When sharing ends​

When the owner unshares the Marquee, you leave or are removed from the team, or the owner leaves:

  • Your Playgrounds on that Marquee are destroyed.
  • Your live Genie chats on it are stopped.

You keep your own Marquees and other resources. Leaving only ends access to shared resources.

Move any work you need before sharing ends.

FAQ​

Can members share their own Marquees into the team?

No. Sharing is owner-only today: members use what the owner shares.

Can I share anything other than a Marquee?

Not today. Marquees are the only team-shareable resource; everything else stays personal. There are no team-scoped Secrets, API keys, or audit logs: those stay per-account, and team membership doesn't change them.

Does a shared Marquee let members see my Genies or Props?

No. Marquee access alone doesn't grant access to your other resources. Members see and manage the Playgrounds running on the shared host, but your Genies, their chats, your Props, and your Secrets stay private.

What happens to my teams when I delete my account?

You automatically leave every team you're a member of. Teams you own are not cleaned up automatically: transfer leadership or delete the team first.

Last updated on