---
title: "Tray"
description: "Tray is the desktop application the people you support use. It is how they ask for help and see what is happening to their machine."
url: "https://support.outpostplatform.com/tray/"
product: "tray"
type: "concept"
status: "stub"
ai_summary: "Overview of Outpost Tray, the Windows system tray application for end users. Shows the state of their endpoint, opens support requests, carries live chat with a technician, surfaces notices from IT, and is the tenant interface in provider mode where clients get no console."
source: "https://gitlab.com/outpostplatform/docs/-/edit/main/src/content/docs/tray/index.md"
license: "CC BY 4.0"
---

# Tray

Tray is the only part of Outpost most people ever see. It sits in the Windows
system tray on a managed endpoint and gives whoever uses that machine a way to
see its state, read notices from IT, and start a conversation with a technician
without knowing anybody's email address. This section is for whoever rolls it
out and whoever answers what it sends.

<!-- TODO: write this page against the concept template.

Sections:

- What Tray is, and what somebody using a managed machine sees.
- Where it comes from: installed alongside the Agent, not separately.
- What it shows about the endpoint, and what it deliberately hides.
- Asking for help, and where that request lands.
- Live chat with a technician, and what happens when nobody is available.
- Notices and announcements from IT.
- Why Tray is the tenant interface in provider mode, where clients get no
  console of their own.
- What it does when the endpoint is offline.
-->

Follow the [concept template](https://gitlab.com/outpostplatform/docs/-/blob/main/templates/concept.md).