> For the complete documentation index, see [llms.txt](https://doc.anytype.io/anytype-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.anytype.io/anytype-docs/collaborate/chats/direct-channels.md).

# Direct Channels

A **Direct Channel** is a private, one-on-one connection between you and another user. It is also called a 1:1 channel and has all the capabilities of a regular [Channel](/anytype-docs/basics/space.md).

Both participants have equal access: there's no admin, no role hierarchy, no permissions to set. It's a place for quick check-ins, a private discussion, creating new Objects, or a side conversation about something happening in another Channel.

<div data-with-frame="true"><figure><img src="/files/gtyTA3Vx3SO4LkEy0uFD" alt=""><figcaption></figcaption></figure></div>

## Why it matters

Your 1:1 channel with another user exists when you create it. It works offline, syncs when a connection appears, and remains private between you both.

How does this work? When you start a private chat with someone, both of your devices independently create the *same* chat space using a bit of math based on both your keys. Since you're both starting from the same ingredients, you both land on an identical result — no server needed to set it up or approve it.

That means you can start chatting right away, even offline. Once your devices find a way to connect (internet, local network, whatever's available), everything syncs up automatically and merges together smoothly, without conflicts. There's no "owner" of the chat in the usual sense — you're both equal participants with the same rights. And it's always just the two of you: nobody can be added or removed from a 1:1 chat.

**In short: users do not need internet access or anybody's permission to collaborate in a 1:1 channel. This is built with your digital freedoms in mind.**

## How it works

A Direct Channel is created automatically when you start a conversation with another user. Once created:

* Both members see the Direct Channel in their Vault Sidebar.
* Either member can post messages and create Objects.
* Both can mute notifications independently.

You can have a 1:1 with any other user — including members of shared Channels you both belong to. The Direct Channel exists separately from those shared Channels.

## Starting a Direct Channel

1. Click any member's profile picture or name
   1. In a Chat.
   2. In a Channel members list.
   3. In an @-mention.
2. Click **Connect** or **Send message** in the popup.
3. The Direct Channel is created.
4. Send messages, create Objects, and collaborate as usual.

<div data-with-frame="true"><figure><img src="/files/2vS5zsO93cCmhKpUqXzJ" alt=""><figcaption></figcaption></figure></div>

## Notifications

By default, you'll be notified about every message in a Direct Channel. To change this:

1. Right-click the Direct Channel in the Vault, **or**
2. Click the three-dot menu inside the channel.
3. Choose **Mute.**

Each member sets their own notification preferences for the same Direct Channel.

## Leaving a Direct Channel

You can leave a Direct Channel by:

1. Right-clicking it in the Vault.
2. Selecting **Leave Channel**.

When you leave, the channel disappears from your Vault — but the other member's copy remains. Any new messages they send will not reach you. If you reconnect, you will re-enter the original Direct Channel with them.

To leave permanently and clear all history, you can also delete the channel — but this only deletes your local copy. The other member retains their side.

## Tips

{% hint style="warning" %}
You can't add a third person to a Direct Channel. If a one-on-one conversation needs to expand, create a regular Channel and invite both people.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.anytype.io/anytype-docs/collaborate/chats/direct-channels.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.