> For the complete documentation index, see [llms.txt](https://ac.docs.landis.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ac.docs.landis.cloud/daily-usage/opt-in-out-of-teams-queues.md).

# Opt In/Out of Teams Queues

{% hint style="info" %}
The Teams Call Queues panel can be enabled under [Layout](/settings/layout.md)
{% endhint %}

Prerequisite: [Enable Opt In/Out of Teams Queues (Preview)](/getting-started.md#enable-opt-in-out-of-teams-queues-preview)

This feature is in [preview](/appendix/feature-states.md).

The Teams Call Queues panel gives users the ability to view their Teams queues and opt in or out of them.

**Refresh button:** This will update the panel with the current signed in state of the queues.

**Opt In/Out:** Users can opt in or out of a queue by changing the toggle beside a queue and selecting Save.

Some queues may have the option to opt in/out disabled. This is because of the queue configuration in the Teams admin center.

**Cancel button:** This will disgard any changes that were made since the last save.

***

**Open Teams Call Queues button:** This will open the Teams queue opt in/out webpage in a browser.


---

# 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://ac.docs.landis.cloud/daily-usage/opt-in-out-of-teams-queues.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.