Skip to content

Share with people

You share a collection, a single entry or a whole hub with the people you choose, and each person gets a role: view, comment or edit. It works like sharing in Notion.

How to share

Every collection, entry and hub has a Share & privacy button at the top right. Its “Who can see it” part has four choices:

Choice Who can see it
Only me (the default) you
People the people you invite, each with a role
Anyone with the link anyone who has the link
Public anyone on the web; see Public pages
Role Can
View see the entries
Comment see and comment
Edit see, comment and change entries

A link gives only View or Comment, and it can have an end date.

Example: you invite your coach Anna to Workouts with the role Comment. She sees every workout and comments on “Morning run, 5.2 km”. She cannot change it.

The share dialog is a protected screen: no design can restyle, cover or fake it. Sharing, adding members and changing roles are changes only you can make. You confirm each one with Face ID, a fingerprint, Windows Hello or your device password. An agent or kzx can only suggest a share.

A shared space has its own place in the cloud

A shared collection moves into its own space in the cloud. The owner pays for it. Each member’s devices sync with it. Each person’s own data stays in their own place.Shared spaceWorkouts, in the cloudthe owner’s Pro paysYou (owner, Pro)your other data: Cloud SyncAnna (member, Free)her own data: Cloud Sync, one device
The shared collection lives in its own space in the cloud; both people sync with it.
  • A shared collection gets its own private space in the cloud, only for it.
  • The owner pays and needs Pro. The people you invite can be on Free.
  • Everyone you invite needs a Kaizendex account. Every plan has one, Free too.
  • A Free member uses the shared space on every device. The owner’s plan pays for it. The member’s own data uses Cloud Sync for one device until they go Pro.
  • Two people can write in the same entry at once. Text merges word by word, so no one loses words.

Share a hub

Sharing a hub with a person is like giving them a key. They see your real hub: every tab, with your data.

Example: your Training hub has three tabs: This week’s workouts (a view of Workouts), Fitness (a dashboard with a kilometres chart and a sleep chart) and My training notes (a note). You share Training with your coach Anna, with the role Comment.

You share the Training hub with Anna. Before you share, the app lists everything she will see: Workouts, Sleep, the Fitness dashboard and My training notes. Anna then sees the same hub, every tab, with your real data.Your Training hubThis week’s workoutsFitnessMy training notesyour real dataBefore you shareAnna will be able to see:WorkoutsSleepthe Fitness dashboardMy training notesAnna seesThis week’s workoutsFitnessMy training notesrole: Comment
The list comes first, so nothing goes out by surprise.
  • Open the hub’s Share & privacy panel and invite people, as for a collection.
  • Before you share, the app lists everything they will be able to see: “Workouts, Sleep, the Fitness dashboard, My training notes”. Nothing goes out by surprise.
  • The collections and entries the tabs show join the share, at the same role.
  • It is normal sharing, with the rules on this page: the owner pays, and the people you invite can be on Free.
  • Publishing a hub to the Library is different. It never includes your data. See Publish to the Library.

Keep some entries private

You can keep one entry out of a shared collection. Example: Workouts is shared with Anna, but the entry “Physio notes” is set to Only me. Anna never sees it. An entry’s own choice wins over its collection’s.

What else is shared, and what is not

Thing Rule
A view, or an entry with Chart or View blocks (such as a dashboard) Sharing it shares its source collections at the same role. The dialog lists them.
A hub Every tab joins the share: the collections and entries its tabs show, at the same role. The dialog lists them.
A collection or entry set to This device only is never shared. A shared collection must stay in Cloud Sync: making it This device only stops the sharing, after a warning.
A collection set to Cloud Sync, end-to-end encrypted Sharing turns end-to-end off for it, after a warning: “Sharing turns off end-to-end for this collection. We can read it, like any Cloud Sync collection.” It switches to plain Cloud Sync. End-to-end entries inside it switch too, and the same warning lists them. When you stop sharing, you can turn end-to-end on again. See End-to-end encryption.
A member’s AI sees the shared collection only if the owner allows AI on it. This holds inside Kaizendex; a member can still copy what they see.
Designs a member made wait for your Use it; anything in them that can act starts off
The space’s automations run only in the space’s own place in the cloud; see below

Automations in a shared space

Automations of a shared space run only in the space’s own place in the cloud, on the space’s collections, on the owner’s allowance. The owner switches them on. Each member opts in before an automation may change the entries that member made.

Members see only automations that touch nothing but the collections shared with them. Anna sees “tag every new workout New”. She does not see an automation that also reads your Sleep: not its name, not its steps, not its code. Its changes to Workouts show in history as “changed by an automation of Daniel’s”. More: Where and when automations run.

When the owner stops paying or leaves

Any Pro member can take the space over within 30 days. If no one does, the space closes and every member keeps a copy.