> For the complete documentation index, see [llms.txt](https://help.are.na/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.are.na/docs/getting-started/channels.md).

# Channels

A channel is a collection of content on Are.na, made up of both [Blocks](/docs/getting-started/blocks.md) and other channels.

What a channel becomes is up to you and whoever you share it with. It can be a reading list, an archive of research, a brainstorming canvas, or a collection of ongoing research. It can also be a mindmeld between collaborators, a private headspace for your thoughts, or a poem.

There's no wrong way to use a channel (or Are.na).

<figure><img src="/files/wiVgEa4AFeeZpN7xYJbG" alt=""><figcaption><p>A channel on Are.na</p></figcaption></figure>

### Organizing blocks in a channel

You can change the order of the contents of a channel by dragging from the top left corner of a block or channel.

{% embed url="<https://vimeo.com/1202263938>" %}

### Channel ownership

Channels can be owned by individuals and by groups. If a channel is owned by a group, anyone in the group can add to the channel.

Channels can also have any number of collaborators you invite. Collaborators have access to view, add and remove content from the channel, but cannot change channel settings.

### Adding collaborators

You can add collaborators to a channel by clicking the "Add collaborator" button in the top section of the channel. Once you're there, you can search for the person to add to your channel by name or by email.

People who follow you are added instantly. People who don't follow you are sent an invitation that they have to confirm before they're added.

{% embed url="<https://vimeo.com/1202268152>" %}

If you'd rather invite multiple people at once, you can generate an invite URL that you can send to anyone you'd like to add to the channel. Note that anyone with this link will be able to become a collaborator on your channel, so keep that in mind.

{% embed url="<https://vimeo.com/1202269569>" %}

### Channel visibility

Channels have privacy settings that determine who can view or add to them. You can choose the privacy setting when you create a channel.

#### Open Channels

Open channels are channels that **anyone on Are.na** can view and add to. If your channel is something that you'd welcome other people to contribute to, [keep the channel open](https://www.are.na/block/2401057).

For example, some popular open channels:

* [Good Sign-offs](https://www.are.na/meg-miller/good-sign-offs)
* [Feedback and Feature Requests](https://www.are.na/are-na-team/feedback-and-feature-requests)
* [Wild Animals vs. Manmade Materials](https://www.are.na/laurel-schwulst/wild-animals-vs-manmade-materials)

#### Closed Channels

Closed channels can be seen by everyone, but can only be edited by you and by any invited collaborators.

#### Private Channels

Private channels can only be seen or edited by you and by invited collaborators.\\


---

# 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://help.are.na/docs/getting-started/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.
