Team guide
Leaving and lost Macs
When someone leaves, the team's work leaves their Macs and their own stays; when the team ends, its work stays only on its owner's Macs. When a Mac is lost, the work can come back on the person's new Mac.
When someone leaves
The sheet from Leave <team name>… lists what will be deleted before the person confirms. When an admin removes someone, the same deletion happens at the person's next sync and the Mac shows the list afterwards. If a recording is running, the removal waits for Stop, and that recording goes too when it is work.
- Deleted
- Every work meeting on the person's Macs, published or not, with its audio, transcript and notes; every copy of the team's notes; the team's folder on the Mac, its keys, and its recovery copies on the relay at once.
- Kept
- All personal meetings and notes. Notes the person published stay with the team, marked “former member”.
- Pro
- Their own, if they bought it, keeps working for their own notes. In the team it never replaced a seat. A team seat stays until an admin takes it back, and then Pro from it runs on for up to 30 days.
The owner of a team can't leave it without handing it over: Hand over… on the team's page makes another admin the team's owner. The team key and the subscription don't move with it: see When the owner or an admin leaves, below. The owner can also delete the team (When a team ends, below).
When the owner or an admin leaves
Before the team's owner goes, they choose Hand over… on the team's page and pick an admin as the team's new owner: only an admin can own a team. The rule for the team's end goes with the role. Whoever holds the team key gives it to an admin who stays, who opens it in Settings › Pro (a team key works on up to three admins' Macs), and the person leaving takes it off their Mac with Remove team key…. To change the address on the subscription, write to patum@nikioth.org. The 24 recovery words stay where the company keeps them, for the new owner.
If an admin left with a copy of the team key, write to us from the address on the subscription. We sign the team key's next revision and send it to an admin who stays, who opens it in Settings › Pro, and the copy the former admin kept then manages nothing. The new admin takes the former admin's Macs off the key in Settings › Pro. Seats, people and notes stay as they are.
When a team ends
A team ends when its free month ends and nobody bought Team, when its subscription ends and isn't renewed, or when its owner deletes it. Its work then leaves members' Macs, and only the owner's Macs keep it. With the team's recovery words, the owner can also bring in the projects that were closed to them, unless they turned that rule off (What the owner reads at the end, below).
- When a free month ends unbought, at the end of its last day in UTC, every Mac in the team goes read-only, offline Macs too, and nothing is deleted. Our relay keeps the team for 14 days, and buying Team in that time, with Buy Team… on the Mac that holds the team key, brings it all back. Then the relay deletes everything it holds for the team. For example, a free month started on November 14 runs through December 13; from December 14 the team is read-only, its work stays on members' Macs through December 27, and on December 28 (UTC) the relay deletes the team. The team's page in Patum shows the dates in your time.
- When a subscription ends, because it was cancelled or a renewal wasn't paid, the team works as before for 14 days after the last day it was paid for. Then every Mac in the team goes read-only, as A Mac without a seat describes, nothing is deleted, and the owner's reading opens. 28 days after the last paid day, our relay deletes everything it holds for the team; the team's page in Patum shows the date. Until then, paying a renewal that failed brings everything back. If you cancelled, write to us before then from the address on the subscription, and we put the same team on a new subscription; buying Team again on this site makes a new team instead.
- The owner deletes the team with Delete <team name>…, at the foot of the team's page on their Mac. The sheet first offers what the owner can keep, then lists what goes and for whom, and asks once more. It needs the relay: without a connection, nothing is deleted. The relay deletes the team's notes at once. When the owner types the recovery words in that sheet, the team is closed and read first (Deleting the team, below).
- Members' Macs
- Delete the team's work at their next sync, as when someone is removed, and say why. Personal meetings and notes were never the team's, and stay.
- The owner's Macs
- Keep the team's work, read-only and encrypted, with nothing syncing, until the owner chooses on each Mac: export it, move it into their library, or delete it. The Mac the team was deleted from keeps only what was moved; the owner's other Macs keep their work until the owner chooses there.
- Export…
- On the owner's Mac, at any time. It writes a folder of files any app opens: every work meeting that Mac reads, with its note, transcripts and attachments, and the audio if chosen; the published notes that reached it, each with its versions, transcript and remarks; and the team's settings: its people with their roles and Macs, its groups, projects and who reads them, its rules, seats and license. It never writes a key or anything else that opens the team's work. Projects closed to the owner aren't on their Mac until the owner brings them in with the recovery words, once the team has ended; the folder counts those still closed, and they go with the team. Members have no Export… of the team.
- Move into my library…
- On the owner's Mac, once the team is ending; in the sheet that deletes the team, it starts on. Every work meeting becomes a personal meeting with its recording, transcripts, note and the note's versions, actions and speakers. Each colleague's note becomes a personal meeting without a recording, with its author and remarks as the meeting's own notes. Each meeting gets a tag with the team's name, and a team project becomes a personal project with the same name. They file into the owner's own vault like any personal meeting, and renewing or deleting the team later leaves them alone.
- Pro
- Pro from a seat stops when the seat does. When a paid team ends, an owner whose Pro came from the team's seats, with no Pro of their own, sees Keep Pro for yourself, which opens Pro's checkout with a discount for a team's owner; a free month has no such offer. Without Pro, Free keeps everything they made readable.
What the owner reads at the end
Every team has this rule, on by default: “When <team name> ends, its owner can read every note shared in it”. Patum shows it on the invite before anyone joins, and on the team's page to everyone in the team. The team's owner is the person who created the team, or the person they handed it to.
- While the team runs, nobody reads a project closed to them, the owner and the admins included. The owner reads what was shared with them, like any member.
- Once the team has ended, the owner can read every note published in it, the projects closed to them included. That takes two things together: the team's 24 recovery words, typed on the owner's Mac, and a share of a key that our relay keeps for the team. Neither opens anything alone, and no Mac holds the key before the end. The relay hands its share only to the owner's Macs, and only after the team has ended.
The reading opens when a free month has ended and nobody bought Team, 14 days after the last day a paid team was paid for, or when the owner closes the team to delete it. It stays open until our relay deletes the team; after that there is nothing left to read.
- Bringing them in
- On the owner's Mac, Move into my library… and Export… ask once: “To bring the projects closed to you, type <team name>'s recovery words”. After Bring them in, the notes of those projects are on that Mac as colleagues' notes, and moving or exporting takes them with the rest. Patum uses the words once and keeps no copy. Before the relay opens the reading, the box says on which day it will. The reading doesn't need a seat.
- Deleting the team
- With Move its work into my library on, the sheet from Delete <team name>… asks for the recovery words too. The team is then closed for good: read-only for everyone, with “<team name> is closed” on every Mac, while the owner's Mac reads every project. Then the team is deleted. If the reading fails, the team stays closed and isn't deleted, and Delete… tries again.
- What it doesn't reach
- Anything never shared in the team: meetings and notes nobody published, the Outbox, and everyone's personal meetings and notes, which never left their Macs. Nor audio, which is never shared. It also leaves out notes published only to a call's attendees before the rule came into force, and, in a team created before Patum had the rule, older notes of a project whose keys no lead's Mac still held by then.
- Turning it off
- Only the owner can, with Turn off… under the rule on the team's page, then Turn Off for Good. Our relay deletes its share at once, and nothing is sealed to the key again. It can't be undone. The invite and the team's page then say “When <team name> ends, its owner reads only what was shared with them: its owner turned that rule off for good”, and the activity log shows who turned it off.
- If the team comes back
- When a team is bought or renewed after its owner read it, the key is spent: the relay drops its share, and every project gets new keys before it takes new notes. The owner's Mac asks for the recovery words again to keep the rule. Until the owner types them, notes published only to a call's attendees stay out.
- A team created before the rule
- The rule waits for its recovery words: the owner types them once with Type recovery words… on the team's page.
When a Mac is lost
A Mac's work in a team opens with a key that never leaves that Mac, apart from its recovery copy, which is split in two: one share for the admins' Macs and one kept by the relay. Neither share opens anything alone, and neither does a backup of the Mac.
- The person sets up their new Mac, or restores the lost Mac's backup onto it with Time Machine or Migration Assistant, and makes it theirs in the team: with Link another Mac… from another of their Macs, or an admin invites it for them, and a second person confirms it.
- The new Mac finds the lost Mac's work, locked, and asks for it. An admin, someone other than the person, reads six words with them and approves.
- The relay gives its share to that Mac alone, while the approval lasts (seven days at most) and only if the lost Mac stays silent. The work opens there as it was, and the lost Mac leaves the team.
If the old Mac still works, nothing is released behind its back: it says so, and it can move its work to the new Mac itself, with no admin and no copy.
- An admin's Mac
- Comes back as a member's: a recovery brings back the work, not the role. The team's owner is asked once to make the new Mac an admin's. If the owner's Mac is lost too, only the team's 24 recovery words can name an admin.
- A stolen Mac
- An admin removes it. Its work stays encrypted, closed while the Mac is locked, and is deleted the next time it connects. Its recovery copy is kept 30 days, so the person can bring their own backup to a new Mac; the thief gets nothing from it.
- Someone who left or was removed
- Gets nothing back: their Macs' recovery copies were deleted with them.
- The recovery words, lost
- We can't give them back: they're made on the owner's Mac and never reach us. Day to day, the team doesn't need them. They're needed to name an admin when every admin's Mac is lost, and for the owner's reading at the team's end. Without them, a team whose admins all lost their Macs can't get an admin again, and the projects closed to the owner go with the team when it ends.
- What can't come back
- Work from a Mac that had no recovery copy yet, and the work of a team's only admin who lost their only Mac, whose copy was wrapped to that Mac alone. What was published comes back to any new Mac of the person either way.