> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agentdesk.team/llms.txt
> Use this file to discover all available pages before exploring further.

# Sessions and privacy

> Find conversations and understand ownership, project binding, and fixed visibility.

A session is one conversation with an agent. Use separate sessions for separate topics or projects, and return to an existing session for a related follow-up.

## Find and organize sessions

The session sidebar supports search and visibility filters:

| Filter | Shows |
| - | - |
| **All** | Sessions your account is allowed to see. |
| **Mine** | Sessions owned by you. |
| **Shared** | Shared sessions visible to your role. |

Project grouping and the project filter organize the visible list. You can pin a project, open it, and move it up or down in the sidebar. Pinned sessions, unread indicators, and available conversation actions help you return to ongoing work.

Opening a session restores that conversation. **Mark all sessions as read** for an agent clears its unread state; it does not finish any work items.

## Choose a project for a new session

Start a new session from the intended project or choose its project binding before the first message.

| Scope | What it means |
| - | - |
| **Project session** | Work and newly created tasks use that project context; shared project instructions can apply. |
| **Workspace session / No project** | A common conversation without a bound project. Legacy task creation uses General. |
| **Task execution session** | A conversation attached to a particular task run; open it from Task Detail. |

A project reference in a message is additional context. It does not change the session binding. To work in another project, create a new session with that binding.

Project-filter choices in the sidebar are navigation preferences. They do not move task records, files, or an existing session.

## Choose visibility before sending

Turn **Private conversation** on before the first message when only you should be able to view the conversation. With private mode off, the conversation uses workspace visibility, subject to role permissions.

Visibility locks once sending starts. You cannot convert an existing shared session to private, or a private session to shared, by changing that toggle later. Start a new session with the desired visibility instead.

Shared visibility does not make the conversation public on the internet. It also does not transfer ownership or automatically let every viewer send messages.

## Ownership and access

Roles can allow **Own sessions** or **All workspace sessions**, with read and write permissions controlled separately. A workspace owner's administrative role does not make every private conversation theirs.

If a session opens read-only, your role allows viewing without message changes. If a session is unavailable, check the selected workspace, agent, project filter, archive state, and your permissions.

Conversation actions such as rename, pin, archive, or export are shown only where supported and permitted. Archiving a conversation and archiving a task are separate actions.

## Follow a task run

Open a task's **Current execution** session for the running conversation, or an entry in **Execution history** for an earlier run. Keep the task ID with any follow-up so the agent can inspect current task state.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.