Your team
An organisation is the unit everything belongs to: the board, the tracker connections, the projects and the credit pool. Joining one is by invitation, and every member subscribes individually.
Invite someone
- Open the members page from the dashboard.
- Send them the invite link.
- They open it, sign in, and subscribe.
Joining is invite-only. There is nothing to type and no code to guess at: a link with no invite in it shows a page saying so rather than a form.
Each member subscribes individually, and their subscription is credited to the organisation that invited them. Every paid member adds their allowance to a pool the whole organisation draws on.
An invite link can be spent or expired. If it is, ask the owner for a fresh one.
Owners and members
| Owner | Member | |
|---|---|---|
| See the organisation's board | yes | yes |
| Invite and remove people | yes | no |
| Connect and disconnect trackers | yes | no |
| Turn on what TeamFlow writes back | yes | no |
| Delete the organisation's reports | yes | no |
The first person to sign up creates the organisation and owns it.
Reports in an organisation are visible to its members, including the name of whoever did the work. Be clear about that before you invite anyone; the privacy policy says it in full.
Belonging to more than one organisation
One address can hold a seat in several organisations. Each machine reports to exactly one of them at a time.
/teamflow:orgThat prints the organisation your reports are credited to and any others your address holds a seat in, with their ids. To move this machine:
npx -y github:macleodlabs-ai/teamflow-plugin org switch <id>Reports published after the switch are credited to the new organisation. Nothing already published moves.
Which pool a report is charged to is decided by the session, not the person: a dashboard tab, a laptop and a build box can each sit in a different organisation, and each is billed where it sits.
If you signed up alone and later join an organisation, you keep your own pool. The join asks you once, in one sentence, whether to fold that balance in or keep it separate. Both answers are recorded, nothing moves until you answer, and you are not asked again.
Remove a machine
Two ways, and either is enough.
On the machine itself:
/teamflow:logoutThat removes the stored credential and revokes it at the service.
From anywhere: a machine signed in with the device path holds a credential of its own, and the members page can revoke it. Do that when the machine is gone, shared, or you no longer have a shell on it.
Revoking stops reporting from that machine. It changes nothing already on the board.