> 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

Collections of content on Are.na

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="https://3477914774-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYHdbQfmTtGrkgTWzb7VG%2Fuploads%2Fdsq5fTTSb0jrhzajrPsQ%2FScreenshot%202024-01-22%20at%206.22.52%E2%80%AFPM.png?alt=media&amp;token=882f2ec7-6f46-4a28-a800-5500e1129d74" alt=""><figcaption><p>A channel on Are.na</p></figcaption></figure>

### Creating a channel

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

To create a channel, click the "+ New Channel" button at the top right of the screen.&#x20;

Choose a title for your channel. If you'd rather not think of a title right now, you can always use our random title generator by clicking the <i class="fa-shuffle">:shuffle:</i> icon.

Next, select the visibility of the channel.&#x20;

* **Private channels** are only visible to you and to people you set as collaborators&#x20;
* **Closed channels** are visible to everyone but only you (or your collaborators) can add to them
* **Open channels** are visible to every AND anyone with an Are.na account can add to them. If your channel is something that you'd welcome other people to contribute to, [keep the channel open](https://www.are.na/block/2401057). 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)

### Adding content to your channel

There are many ways to get blocks into your channel. For the basics, check out [Adding blocks](/docs/getting-started/blocks/adding-blocks.md). Once you get the hang of it, try using the [Browser extension](/docs/getting-started/browser-extension.md)or even exploring our [API](https://www.are.na/developers).

### 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>" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.are.na/docs/getting-started/channels.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.