> 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.md). # Teams Teams is where you manage Microsoft Teams policies and tenant-wide settings for your clients — messaging, meetings, channels, external access, and app setup — from Augmentt instead of the Teams admin center, and reuse the same configuration across multiple client tenants as a **Template** or **Baseline**. {% 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 %} The module has three tabs: **Policies**, **Settings**, and **Templates**. ## Policies The Policies tab manages five Microsoft Teams policy types, one at a time via a row of filter tiles at the top of the page: * **Meeting** — scheduling, join and lobby behavior, chat and engagement, content sharing, recording and transcription, and audio/video settings for meetings. * **Messaging** — what people can do in chats and channel messages: editing and deleting messages, Giphy/stickers/memes, read receipts, translation, priority notifications, and similar. * **Channels** — channel creation and discovery, including private and shared channels and whether external users can be invited into or join a shared channel. * **External access** — per-policy control over communication with external Teams organizations, unmanaged (consumer) Teams accounts, Skype users, and Azure Communication Services. * **App setup** — which apps are pinned to the app bar, messaging extensions, and calling extensions, and whether users can pin their own apps or upload custom (sideloaded) apps. Each tile shows how many policies of that type exist for the selected client. Selecting a policy from the table opens its full detail, organized into the same sections as the Teams admin center (for example a meeting policy breaks out into Scheduling, Join & lobby, Engagement, Content sharing, Protection, Recording & transcription, and Audio & video). {% hint style="info" %} Every policy type also shows **Assigned to users** and **Assigned to groups** in its detail view. A user assigned a policy directly always takes precedence over one they inherit through a group; among groups, the group with the lowest priority number wins. {% endhint %} ### Editing, assigning, and deleting * **Edit** opens the same section layout in an editable form. Microsoft's own built-in policies (for example the meeting policy `Default`, or messaging policy `EduStudent`) can't be edited or deleted — Augmentt disables those actions with an explanation rather than letting the change fail against Microsoft. * **Assign** lets you attach a custom (non-global) policy to specific users and/or groups, with a precedence rank for groups. * **Delete** is available for tenant-authored custom policies only — the `Global` policy and Microsoft's built-in presets can't be removed. ## Templates and Baselines Rather than build the same policy by hand in every client tenant, you save a policy as a reusable **Policy Template**, and combine several templates into a **Baseline** you deploy together in one pass. This mirrors the Templates/Baseline pattern used elsewhere in Secure (Defender, Intune, and so on) — Teams templates and baselines are separate from Compliance Audit's [Posture Templates](/modules/secure/security-posture/posture-templates.md), which target a different set of Microsoft 365 checks. * **Create a policy template** — pick a client tenant and one of its existing policies (of a given type — Meeting, Messaging, Channels, External access, or App setup), give the template a name and description, and Augmentt saves that policy's settings as a reusable template you can deploy elsewhere. * **Create a settings template** — the org-wide Settings tab (below) can also be saved as a template on its own, listed as a **Settings template** alongside the five policy-type templates. * **Create a baseline** — group any mix of policy templates and/or a settings template together under one name, so deploying the baseline pushes all of them to a client in a single action. From the Templates tab you can view or edit any saved template or baseline, and see which templates belong to a given baseline. ### Deploying From the Policies tab, the **Deploy** menu offers: * **Policy** — deploy a single saved template to a client, reviewing (and adjusting, if needed) its settings before confirming. * **Baseline** — deploy every template in a saved baseline to a client in one pass; each template's settings are shown for review before you submit. Deployment runs as a background task you can watch to completion; once it succeeds, the new or updated policy appears immediately in the Policies list for that client. ## Settings The Settings tab covers the tenant-wide Teams configuration that isn't a per-user policy — the equivalent of the Teams admin center's org-wide settings and the guest-access side of Entra ID: * **Guest access** — who can invite guests (No one / Admins and Guest Inviters / Admins, Guest Inviters, and members / Everyone, including guests). * **External federation** — whether the tenant allows all external domains, only specific ones, blocks only specific ones, or blocks all external domains, plus the domain list where relevant. * **Guest meeting permissions**, **Guest messaging permissions**, and **Guest calling permissions** — what a guest can do once they're in. * **Org-wide app settings** — third-party and custom app access at the tenant level. * **Team creation** — whether users can create teams/groups themselves, and if so, which security group is allowed to. Selecting **Modify** opens all of these sections in one editable form. As with policies, you can start from a saved **Settings template** using the template picker at the top of the edit form instead of setting every field by hand. {% hint style="warning" %} External federation here is tenant-wide (`Use organization settings` is the default an External access **policy** falls back to). A per-policy External access override always wins for the users it's assigned to; federation set here only applies where no more specific policy overrides it. {% endhint %} ## What isn't covered yet * **App permission policies** (which Teams/Microsoft/third-party/custom apps are allowed tenant-wide) exist in Augmentt's backend but aren't exposed as a policy type in the Policies tab yet — there's no tile or template flow for it today. * **Channel-level posting permissions** (who can post or reply in a specific channel) aren't managed by Augmentt. Unlike everything above, that setting lives per channel rather than tenant-wide, and isn't part of this release. {% hint style="info" %} No prior Stonly knowledge base article exists for Teams — this is a newer capability, so there's no legacy guide being replaced here. {% endhint %} ## In this section * [Meeting policies](/modules/secure/teams/meeting-policies.md) * [Messaging policies](/modules/secure/teams/messaging-policies.md) * [Channels policies](/modules/secure/teams/channels-policies.md) * [External access policies](/modules/secure/teams/external-access-policies.md) * [App setup policies](/modules/secure/teams/app-setup-policies.md) * [Settings](/modules/secure/teams/settings.md) Each page breaks that policy type (or Settings area) down into its real UI subsections with the full field list. --- # 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.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.