Readers and rights

In a small company, people still should not read each other’s mail. Zyx keeps each person’s own rights on every search and every answer.

Folders, people and roles

The company’s files live in one company folder. Each subfolder is a workplace with its own permissions, inherited downward. People have one of three roles: owner, member or viewer. A person’s turn reads and writes only the folders they may.

Every item carries its readers

When Zyx copies an item into its search (a mail, a Notion page, a Slack day, a calendar event), it stores who may read it.

The connection’s readers always count. On a company connection that is the owner; on a person’s own connection, that person alone.
Plus the people the app names. Where the app says who may see an item, Zyx adds those people: a Slack channel’s members, a calendar event’s organizer and attendees, a Linear team’s members, a SharePoint or OneDrive file’s permissions, a Teams channel’s members. They are matched by their work address or Slack id in Zyx’s People settings, and only on a company connection.
Where Zyx does not read the app’s own sharing (Dropbox and Zendesk per-item sharing, Jira and Confluence restrictions, HubSpot record owners, Salesforce sharing rules), the item gets the connection’s readers only. That is the narrower choice: Zyx shows less, never more. Teams thread replies and Slack thread replies are not copied at all.

The answer rule

An item reaches an answer only when every person who can read that answer is among the item’s readers. In a shared chat, that means everyone in the chat. So a colleague’s question never finds your mail, and a shared chat never quotes something only one of its members may see.

Private chats and own connections

A staff member can connect their own mailbox or Notion key, or sign in to a company app with their own account. Their own connections answer only in their private chats.
A private chat opens for its person alone. It never reaches learning, traces, the wiki, or another person’s search. Its cards are decided by that person.
The owner sees, for each person, only “name - app - status”. Never their mail, pages or chats.
Company connections answer in shared chats, schedules and triggers.

Each person downloads their own private chats from Settings, My data (My data and the export).

Tested before every change

A test in Zyx’s local check calls every API route of the workspace as the owner and as a colleague, and fails on any leak. The check runs before every change is pushed.

Fast deletion

Something deleted in an app leaves Zyx’s search at the next sync. Some apps can make it faster, within seconds: Slack, GitHub, Linear and Zendesk can post a signed webhook, and for Outlook mail, OneDrive and Google Drive Zyx keeps its own change subscription. SharePoint files and Teams messages leave at the next sync. A notice is only a hint: Zyx asks the app again with its own key and removes only what the app confirms is gone. Fast deletion needs the public webhook door to be set up. See Status and limits for what was proven live.

Your profile

Each person has their own profile: a memory file with a few fixed sections (about you, how you like to work, your goals, people you work with, your boundaries) and a small file with up to five writing voices, for example “customer mail”. You can open and edit both by hand. Zyx picks the voice that fits the task. The owner cannot read a staff member’s profile.

Journals and memory

Each person has a private journal folder. Nothing in Zyx’s own .zyx folders is indexed for search, and a search over the whole company skips every other person’s journal. Memory is kept per folder and per person, shown on the Memory screen, and each learned line can be undone.