> 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/messaging-policies.md).

# Messaging policies

A **Messaging policy** controls what people can do in Teams chats and channel messages — editing and deleting, Giphy/stickers/memes, translation, read receipts, and similar — for the users it's assigned to. 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 **<sales@augmentt.com>** instead of the usual controls.
{% endhint %}

## Configuration surface

Unlike Meeting policies, Messaging policies have a single settings section (plus policy details) in both the Teams admin center and Augmentt's detail view:

### Policy details

* **Description**

### Messaging settings

* **Owners can delete sent messages**
* **Delete sent messages** (any user)
* **Users can delete messages sent by bots**
* **Delete chat**
* **Edit sent messages**
* **Read receipts** — On for everyone / Off for everyone / User controlled.
* **Upload custom emojis**
* **Delete custom emojis**
* **Chat**
* **Chat with groups**
* **Custom avatars for group chats**
* **Giphy in conversations**
* **Giphy content rating** — mapped to the GIPHY rating scale: Strict → G, Moderate → PG, No restriction → PG-13.
* **Memes in conversations**
* **Stickers in conversations**
* **URL previews**
* **Report inappropriate content** (communication compliance end-user reporting)
* **Report a security concern** (security end-user reporting)
* **Translate messages**
* **Immersive reader for messages**
* **Send urgent messages using priority notifications**
* **Create voice messages** (audio messages) — Chats and channels / Chats only / Not enabled.
* **On mobile devices, display favorite channels above recent chats**
* **Remove users from group chats**
* **Text predictions** (smart compose)
* **Suggested replies** (smart reply)
* **Chat permission role** — Full permissions / Limited permissions / Restricted permissions.
* **Users with full chat permissions can delete any message**
* **Video messages**
* **Priority account chat control**
* **Automatically share files and Loop links with all people in external chats**

## Built-in and default policies

Microsoft ships four built-in messaging policies — `AllOff`, `Default`, `EduFaculty`, and `EduStudent`. Augmentt recognizes all four 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 messaging policy content of its own — there's no seed/migration data defining an Augmentt-authored messaging 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

None of Augmentt's Secure Score, Compliance Audit (CIS/CMMC), or Maester checks currently target Messaging-policy fields. The only Teams-related check in the catalog, **Teams Default External/Guest Options** (`teamsdefaultexternaloptions`), evaluates tenant-wide external access and guest permissions — it doesn't reach into per-policy messaging behavior like message editing/deletion or Giphy/stickers. Be honest with clients that a messaging-policy misconfiguration (say, unrestricted external chat sharing) won't currently surface as a posture finding; it's visible only by reviewing the policy itself in the Policies tab.


---

# 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/messaging-policies.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.