> 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/app-setup-policies.md). # App setup policies An **App setup policy** controls which apps are pinned to the app bar for the users it's assigned to, plus messaging and calling extensions, and whether users can pin their own apps or upload custom (sideloaded) apps. 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 ### Policy details * **Description** ### App controls * **User pinning** — whether users can pin their own apps to the app bar in addition to the ones this policy pins for them. * **Upload custom apps** (sideloading) — whether users can side-load apps outside the Teams app catalog. ### Pinned apps * **Pinned app bar apps** — the ordered list of apps pinned to the left app rail, chosen from the Teams app catalog. This is the field an admin actually edits. * **Pinned messaging extensions** — read-only in Augmentt's editor. * **Pinned meeting extensions** — read-only. * **Pinned calling apps** — read-only. {% hint style="info" %} Microsoft automatically sets the messaging, meeting, and calling extensions for a given app setup policy — they're shown for reference, not because Augmentt lets you edit them directly. Only **Pinned app bar apps** and the two toggles above are editable. {% endhint %} ### Legacy app settings * **Legacy installed apps** (`AppPresetList`) and **Legacy customization assignments** (`AdditionalCustomizationApps`) — older, superseded fields still returned by the Teams cmdlet. They're carried through in the record but aren't part of the primary editing surface. The app catalog itself is searched live against Microsoft's Teams app catalog; if that lookup fails, existing selections on the policy remain visible and editable, you just can't search for new apps to add until it recovers. ## Built-in and default policies Microsoft ships one built-in app setup policy, `FirstLineWorker`. 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 app setup policy content of its own — there's no seed/migration data defining an Augmentt-authored app setup policy template. Every **Policy Template** in the Templates tab is created by an MSP from an existing tenant policy — see Templates and Baselines. ## What isn't covered yet **App permission policies** — which Teams/Microsoft/third-party/custom apps are allowed tenant-wide (`TeamsAppPermissionPolicy`: default catalog apps, global catalog apps, private catalog apps, each with an access mode) — exist in Augmentt's backend and are readable/writable at the API layer, but aren't exposed as a policy type in the Policies tab yet. There's no filter tile, detail view, or template flow for it today; App setup policies (this page) only cover *pinning*, not *permission to install*. ## Posture-check resolution No Secure Score, Compliance Audit (CIS/CMMC), or Maester check currently targets App setup policy fields, or the related App permission policy data. Sideloading/custom-app upload settings are a common attack surface in other MSP security tooling, but Augmentt doesn't score them today — App setup misconfigurations (for example, sideloading left on for a group that shouldn't have it) are visible only by reviewing the policy in the Policies tab, not through a posture check. --- # 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/app-setup-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.