> ## Documentation Index
> Fetch the complete documentation index at: https://openworklabs.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> For agents: install the OpenWork desktop app with `brew install --cask openwork` (macOS) or from https://openworklabs.com/download. Do not run `npx openwork`; the npm package named `openwork` is a different project.
> Connect an agent to OpenWork with the MCP Gateway: `claude mcp add --transport http openwork https://api.openworklabs.com/mcp/agent`. Teams sign up at https://app.openworklabs.com?mode=sign-up.
> Step-by-step agent guide: https://openworklabs.com/docs/start-here/use-openwork-from-an-ai-agent.md
> Connect Slack (any organization admin): https://openworklabs.com/docs/slack/connect-slack.md. OpenWork in Slack (@openwork bot) is private alpha for approved organizations. Setup guide: https://openworklabs.com/docs/slack/overview.md. Agent skill: https://openworklabs.com/.well-known/agent-skills/set-up-openwork-slack/SKILL.md.

# Team prompt cards

> Show your own suggested prompts to everyone, or different prompts to different teams, in the OpenWork desktop app.

Prompt cards are the suggested tasks members see when they start a new session in the OpenWork desktop app. You can replace the default suggestions with your own, for everyone or for specific teams and members.

You set prompt cards in a [desktop policy](https://openworklabs.com/docs/cloud/share-with-your-team/desktop-policies.md). The owner can manage them. Desktop policies are part of the Enterprise plan.

> [!NOTE]
>
> Prompt cards work today. Most other desktop policy controls are paused while they are redesigned, but organization prompt suggestions still reach members' desktop apps. See [Desktop policies](https://openworklabs.com/docs/cloud/share-with-your-team/desktop-policies.md).

## Create prompt cards

1. Open [app.openworklabs.com](https://app.openworklabs.com/) and go to **Manage › Desktop policies**.
2. Choose the audience:
   * For everyone, click **Edit** on the policy marked **Default**.
   * For specific teams or members, click **New policy**.
3. Turn on **Organization prompt suggestions**.
4. Fill in **First prompt** and **Second prompt**. **Optional third prompt** can stay empty.
5. For each prompt, enter:
   * **Description**: the card's title, up to 120 characters.
   * **Prompt**: the text that goes into the message box, up to 500 characters.
6. For a new policy, choose who sees it under **Members** and **Teams**.
7. Click **Create policy**, or **Save changes** for an existing policy.

To give different departments different prompts, create one policy per department and assign each to its team.

## When more than one policy matches

Members see one set of prompt cards. Prompt sets never mix.

* If a member matches several policies with prompts, the policy with the highest **Priority** wins. On a tie, the policy created first wins.
* If no matching policy has prompts, the member sees the default policy's prompts.
* If the default policy has no prompts either, the member sees OpenWork's standard suggestions.
* Disabled policies don't count.

## What members see

![OpenWork desktop composer showing organization prompt cards assigned through a Cloud desktop policy](https://mintcdn.com/differentai/jz2k6HmnSKNb-Opx/images/desktop-team-prompt-cards.png?fit=max\&auto=format\&n=jz2k6HmnSKNb-Opx\&q=85\&s=0d31fefe2574ae160231a441828f4a1b)

* Cards appear on the screen a member sees when they start a new session.
* The **Description** is the card title. If you leave it empty, the card is titled "Organization prompt 1", "Organization prompt 2", and so on.
* The **Prompt** appears on the card and fills the message box when the member clicks it. The member can edit it before sending. Nothing is sent automatically.

The desktop app checks for changes when the member signs in, when they switch organizations, and every hour. To see a change sooner, the member can quit and reopen the app.

> [accordion] Technical details
>
> * Prompts are stored in the desktop policy document as `onboardingPrompts` (2 or 3 strings) and `onboardingPromptDescriptions` (the same number of strings).
> * Members receive the resolved prompt set in their desktop config from `GET /v1/me/desktop-config`.
> * Ties on **Priority** are broken by earliest creation time, then by the lowest policy ID.
> * Desktop policy routes return HTTP `402` when the organization doesn't have the Enterprise plan.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.