# Private and shared work

By default, your team works with one shared Dija and sees each other's work: conversations, job logs, and **Memory**.

The single exception is anything Dija reads from your personal tools (such as your personal mailbox, calendar, or meeting notes) and any output built from that data. Personal-tool work stays private to you alone, hidden even from your manager and the workspace owner.

## What the team shares

- **Company-tool jobs:** Any job that uses only shared company tools, such as your CRM, belongs to the team. Everyone can follow its progress and read its result on **Jobs**.
- **Job history and Memory:** All non-private jobs, the **Company brain**, and approved team notes. See [Memory](memory.md).
- **Shared and visible chats:** Group channels are shared, and individual chats in [the Dija web app](https://app.dija.ai) appear under **Team** in the sidebar with any private replies omitted. When Dija searches past messages for someone, it searches only shared group channels and that person's own chats, never a colleague's direct chat.

## What becomes private to you

A job becomes private the instant it first reads one of your personal tools (see [Company tools and your own tools](tools.md)). From that point on, only you can view:

- The job itself and its step-by-step log.
- Questions from the job and its final result, which route only to your personal channels and never to a group chat.
- Any chat replies from Dija that draw on that job.
- Any memory note the job proposes, until you approve sharing it.

A job can access only the personal tools of the person who started it. Dija never opens a colleague's mailbox or calendar for your work, or yours for theirs.

## How privacy flows across work

Privacy tracks what data was actually read:

- **Searching shared history keeps a job shared:** When a team job searches **Memory** or past jobs, private records are excluded from search results, so the team job remains shared.
- **Jobs start shared until they read personal data:** Every new job begins as a shared team job (unless started directly from a private reply) and switches to private only if it reads a personal tool or earlier private work. Helper jobs spawned by a private job are private too, and a parent job becomes private if it takes in a private helper's output.
- **Direct chats isolate private turns:** When Dija answers you using private work, that reply is visible only to you, and any follow-up job launched from that reply starts private. On later turns in the same chat, Dija sees only a placeholder where the private reply stood, so subsequent replies return to being shared unless they read your private data again.
- **Group channels never use private data:** Because everyone in a group channel reads Dija's replies, Dija never draws on anyone's private work there.

## Proposing team notes from private work

A private job never writes directly into shared **Memory**. Instead, it proposes any candidate note privately to you with its supporting evidence. Only when you approve it does the note enter shared **Memory** (or, if your role cannot approve that note type on your own, move forward as a standard team proposal for your manager to review).

## What remains visible to the team

- **Outbound action requests:** External actions proposed by a private job, such as sending an email from your mailbox or updating a CRM record, still follow workspace rules and appear on **Approvals**, where you or anyone above you can review them. See [Approvals and rules](approvals.md).
- **Connection status:** **Connections** displays which tools are linked and who owns each connection, never what Dija read inside them.

## Enforced independent of hierarchy and the model

Reporting lines never override privacy. Managers and workspace owners can review outbound approval requests from people below them, but cannot read their private jobs, logs, chat replies, or unapproved private notes.

This boundary is enforced by the database query layer alongside tenant separation between companies, so a model mistake or prompt cannot expose your private work to anyone else.
