> For the complete documentation index, see [llms.txt](https://happybara.gitbook.io/channitor/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://happybara.gitbook.io/channitor/reference/joining-behavior.md).

# Joining Behavior

### Channitor can be configured to join new public channels by default, or require approval.  

* **New channel setting**

  > Change the behavior of Channitor towards newly created channels. Options available:
  >
  > * `Auto` Join every new channel automatically.
  > * `Manual` Ask in the newly created channel whether it should join. Waits for team member to respond.

#### The number of zero-activity days before a channel expires and archiving is prompted can also be modified.

* **Expiration threshold**

  > The number of days a channel can go without activity before Channitor starts sending reminders
  >
  > * The setting in the `Joining Behavior` section only applies to channels joined in the future.
  > * Use the select menu at the top of the [`Watched Channels`](/channitor/reference/watched-channels.md) section to adjust settings for specific channels.

#### Specific channels can be joined in bulk using the section menu in this section.  Options to join all channels and remove Channitor from all channels are also available.

![](/files/-MCJu0kKa9oQyVnEEi4h)

### Channels:Users (C/U) Ratio <a href="#cu-ratio" id="cu-ratio"></a>

This is the number of public channels divided by the number of users across your workspace.  It's a good measure of how fragmented your information is in Slack.  The sweet spot varies for every team, but **3-5** is a good place to be.

{% hint style="info" %}
**All public channels** are included in the C/U ratio calculation, regardless of whether Channitor has joined them or not.
{% 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://happybara.gitbook.io/channitor/reference/joining-behavior.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.