Team guide

Groups and rules

Admins set the team's rules, and a group's leads can make them stricter for their group. Patum applies every rule on each Mac, and a setting a rule fixes shows a lock.

Groups

A group such as Engineering, Product or Leadership owns its projects, and its leads decide who is in it. While the team runs, admins can't read a group's notes unless they are in the group, and neither can the team's owner. When the team ends, its owner can read every note shared in it, unless they turned that rule off (The team's end, below).

A group's leads set its own rules within the team's: a group can make them stricter, never looser. A setting a group's rule fixes shows a lock and the group's name.

The audience
The default audience and the ones allowed. A group can make the people invited to the call the default, so that a stakeholder call is never shared wider by accident.
Drops
Who may drop a note into the group's projects: named groups, or the whole team. Whoever drops a note can't read the project: Product passes a summary to Engineering, nothing more. By default, no one may.
Passing notes on
Whether the group's leads, or its members, may pass a note on to people it wasn't published to. Nothing flows onward or up by itself, and by default no one may. A note passed on is a copy that names the original, and its author sees it in the activity log.
Transcripts
Whether the group's notes may carry their transcripts, where the team allows them.
Providers
Whether cloud providers may write and answer for the group's notes, and, with Enterprise, whether the company's AI server does. Without them, the group's notes are written and answered on each member's Mac.
Work audio
How long the audio of the group's work meetings is kept, never longer than the team's rule.

Rules for admins

A setting that a rule fixes shows a lock and the team's name on the person's Mac.

Never send them to a cloud provider
On by default. Work notes, action items and follow-ups stay on the Mac, and so does any Ask or Live context answer that reads the team's work, even when the person has a provider turned on for their own meetings.
Company AI server
In Enterprise. An admin can name the company's own model server (LM Studio, vLLM, Ollama or another OpenAI-compatible server, in the office or in its cloud), so that small Macs don't have to write the team's work. Only text of the team's work goes there: never audio, never personal meetings, and transcription, speaker labels and call questions stay on the Mac. When the server can't be reached, a Mac that has the notes model writes the work itself.
Transcripts may be published
Turn it off and no transcript is published to the team.
Members can share work meetings outside the team
On by default. Turned off, Copy as Text, Share, Share as PDF, Export, Export Transcript, Print, follow-up drafts and Send Actions to Reminders are refused for work meetings, and while a window shows work, Patum asks macOS to leave it out of screen sharing and screenshots. Publishing to the team stays.
Let people know
Requires Patum's recording notice for work recordings.
Require Touch ID to open Patum
Turned on by default for a team member on a Mac that has it, and can be required.
Keep recovery copies
On by default. Each Mac keeps a recovery copy of its team key in two shares, one for the admins and one on the relay, and neither opens anything alone. Turn it off and no Mac writes a copy, each deletes its own, and no admin's Mac approves a recovery (When a Mac is lost).
Keep work audio
Until the note is written, or for 3, 30, 60, 90 or 180 days. Older work audio is deleted for good; the note and transcript stay. Until the note is written means three days after the recording at the latest, and never while a step such as naming the speakers still needs the audio.
Don't recognize voices in work meetings
Off by default. On, work meetings keep and compare no voiceprint, not even a member's own voice profile: voices are told apart within each meeting and named from the invite or by hand. Personal meetings keep the person's own setting.

The team's end

One rule belongs to the team's owner alone: “When <team name> ends, its owner can read every note shared in it”. It is on by default. Everyone sees it on the invite before they join, and on the team's page. The owner can turn it off with Turn off… on the team's page, and then it stays off for good; the invite and the page say so. What the owner reads at the end says what it reaches and what it doesn't.

The activity log

Admins see an activity log: joins, leaves, removed Macs, groups, projects, publications, withdrawals, recoveries and rule changes, including the rule for the team's end turned on or off, its key spent and the team closed. It never records what anyone read, and it holds no note text.