Team hub
The Team hub is home base for your organization — where you connect and verify the people you work with, and reach them through the encrypted team layer. It gathers your org's roster, the three ways to reach the team — Signals, Broadcasts and Asks — and the shared memories your team pools, all in one place.
Local-first, but not alone. Zimac keeps your work on your machine, and the Team hub is the deliberate bridge to everyone else: identity-verified connections to your teammates, and a small set of channels — status, directives, questions — that carry only what you choose to share, end-to-end encrypted. It's the org layer on top of a private core.
⧉ Your org's people
Connect to teammates and verify who's who by directory identity.
⧉ The team layer
Signals, Broadcasts and Asks — the encrypted ways to reach everyone.
⧉ Shared memories
The pooled, distilled conclusions your team chooses to hold in common.
⧉ One home base
Everything org-wide that isn't already its own tab lives here.
What it is#
The Team hub is the studio for anything that spans your whole organization. It's where the local-first app meets the people around you: the roster of teammates you've connected to, the encrypted channels for reaching them, and the shared memory your team builds together. If a task is about the org rather than just you, it starts here.
Connecting your org#
The hub is where you connect and verify the people in your organization. Teammates are identified by their directory-attested identity — rooted in your org sign-in — so a connection isn't just a name you typed, it's a verified principal. That verified roster is what everything else in the team layer rests on: a signal, a broadcast or an ask goes to real, confirmed people, not a guess.
The three tabs#
The hub gathers the three encrypted ways to reach your team, each with its own guide:
All three ride the same end-to-end-encrypted machinery over your verified roster — the server relays sealed envelopes it can't read. They're documented in full on their own pages; the hub is where you compose them and watch the responses come back.
Shared memories#
Beyond the channels, the hub holds your team's shared memories — the team memory space your org pools in common. It's the counterpart to your private memory: where a signal sent to the team brain lands, so the distilled conclusions everyone agreed to share become a resource the whole team can draw on. Your private notes stay private; only what's deliberately shared lives here.