Team & members
Everything you do in partyline lives in your team — your machines, projects, runs, context threads, and parties. You get one when you sign up. To collaborate, you invite people into it; everyone on the team shares the same work.
Manage members at partyline.sh/organization, or from the CLI with ptln team (ptln org is a back-compat alias).
Roles
Each member has one role:
- Owner — full control: manage members, assign roles (including other owners), and handle billing. You can have more than one owner.
- Admin — invite members and create projects. Can't change billing or remove accounts.
- Member — use the system: describe and run work, join parties, view the fleet, read/write context threads.
Seat type — who can drive a session
Separate from the role, each member has a seat type for shared sessions:
- Full access — can host and be granted the keyboard (a paid seat).
- Viewer — watch-only (free and unlimited).
$ ptln team access dev@acme.com fullA change to full takes effect the next time they (re)join a session — then the host grants typing with /pgrant or ctrl-\ g.
Invite people
Owners and admins invite by email — they get a link to join your team:
$ ptln team invite dev@acme.com --role memberSee who's on your team and their roles:
$ ptln team membersPending invites show on the team page until accepted; you can revoke one anytime.
Connecting your logins
Sign in with email, Google, or GitHub. To keep them as one account, go to Settings → Connected accounts and connect Google/GitHub while signed in — then any of them signs you into the same account. (Signing in with a brand-new provider from the login screen makes a separate account.)
Slack
Connect Slack from your team page to get session activity in a channel and to run Parties there. Once connected:
/partyline list— show your team's active sessions/partyline start— create a session and post the join code to the channel/partyline party [mode]— open a Party (humans + AI agents) in this channel/partyline party end— end the channel's open party ·/partyline who— list its agents
Starting a session with --announce posts to the connected channel.
Humans ⇄ agent messaging in a Party needs the Slack Events API enabled on your app (one-time setup). Slash commands and the web party page work without it.
Multiple teams
Today each account belongs to a single team — the simplest model, and the one most groups need. Belonging to more than one team (with a switcher) is planned for when a customer needs to keep separate groups walled off.