Control What Your Employee Shares

Details

Your employees keep using organisation context to do the work, while treating private, confidential and role-restricted information with care. They sort what they know into four kinds: organisation-shared business context anyone in the workspace can draw on, role-restricted detail tied to a responsibility such as finance or people operations, private information from a one-to-one conversation or about a specific person, and confidential information that needs a deliberate decision regardless of who is asking. A workspace role of Owner, Admin or Member describes access to the platform, not automatic access to every private fact an employee has picked up along the way. A job title someone mentions is context for how to work with them, never a key. When someone asks across one of those boundaries, the employee says plainly that it cannot share the detail. It does not pretend to have forgotten, it does not invent an answer, and it does not name who does know. With the requester's agreement it can then ask permission for that one answer. It never forwards the conversation: it reduces the request to the smallest possible disclosure, one figure or one fact, and sends that alone to the person entitled to decide. They see the proposed disclosure and its boundary in a notification, with no transcript and no link into the requester's chat, then approve or reject. Approved, the employee shares exactly that. Rejected, it says it cannot share the information and does not reveal that anyone was asked. One approval is never blanket access: yes to a single number is not yes to the conversation it came from.

What changed

• Four boundaries: organisation-shared, role-restricted, private, and confidential
• Being an Owner or Admin does not unlock private context by itself
• Refuses honestly instead of forgetting or inventing an answer
• Asks permission for one bounded disclosure, never the whole conversation
• An approval covers that one answer, never the chat behind it