> For the complete documentation index, see [llms.txt](https://helpdesk.augmentt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.augmentt.com/modules/secure/teams/channels-policies.md). # Channels policies A **Channels policy** controls channel creation and discovery for the users it's assigned to — private and shared channels, and whether external users can be invited into or join a shared channel. It's one of the five Teams policy types on the **Policies** tab; see Teams for the tab layout, assignment precedence, and template/baseline workflow shared by every policy type. {% hint style="info" %} Teams is a licensed feature. If a client isn't authorized for it, the page shows a notice asking you to contact **** instead of the usual controls. {% endhint %} ## Configuration surface Channels policies are the smallest of the five policy types — one settings section beyond policy details: ### Policy details * **Description** ### Channel creation and discovery * **Discover private teams** — whether private teams can be surfaced in search for users who aren't members. * **Create private channels** * **Create shared channels** * **Invite external users to shared channels** — whether users can share a channel with people outside the tenant. * **Join external shared channels** — whether users can participate in a shared channel another organization invites them into. {% hint style="info" %} Standard (general/public-within-team) channels are always available and aren't configurable through this policy — only the private- and shared-channel behaviors above are. Augmentt's backend also has broader channel-creation and cross-tenant sharing fields on this record (org-wide team creation, classic-channel and threaded-channel toggles, sharing with a team in the org) that aren't yet surfaced in this section — see the note below. {% endhint %} ## What isn't covered yet **Channel-level posting permissions** — who can post or reply in a specific channel — aren't managed by Augmentt at all. Unlike everything else in this policy type, that setting lives per channel (`channelModerationSettings` in Microsoft Graph) rather than tenant-wide, and enumerating every team and channel in a tenant is a materially different, much more expensive operation than the tenant-wide policy reads Teams otherwise relies on. It isn't part of this release. ## Built-in and default policies Microsoft ships one built-in channels policy, `Default`. Augmentt recognizes it as Microsoft-managed: **Edit** and **Delete** are disabled with an explanation rather than being sent to Microsoft and failing. `Global` is the tenant's baseline custom policy and also can't be deleted. Augmentt doesn't ship any preset channels policy content of its own — there's no seed/migration data defining an Augmentt-authored channels policy template. Every **Policy Template** in the Templates tab is created by an MSP from an existing tenant policy — see Templates and Baselines. ## Posture-check resolution No Secure Score, Compliance Audit (CIS/CMMC), or Maester check currently targets Channels-policy fields. The Teams-related check in the catalog, **Teams Default External/Guest Options** (`teamsdefaultexternaloptions`), covers tenant-wide external access and guest permissions, not channel creation or shared-channel external participation. A tenant that allows unrestricted shared-channel invites to external users won't show up as a posture finding today — that's only visible by reviewing the policy directly. --- # 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://helpdesk.augmentt.com/modules/secure/teams/channels-policies.md?ask=&goal= ``` `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.