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

# Custom Branded Service Desk App tester guide

> Test the Custom Branded Service Desk App in Slack in alpha: what it does, the flags that turn it on, a step-by-step test run, known limitations and what the team is exploring next.

**You're testing the Custom Branded Service Desk App in Slack, a new feature in alpha.** It puts your service desk's own Slack app in front of Ravenna:

* **Your branding:** app name, icon, short and long descriptions, background color, and up to five slash commands.
* **One deploy for the whole organization:** Ravenna creates one app per Slack organization and installs it in every connected workspace, including workspaces that join later.
* **Ticketing moves over:** once the app is in every connected channel of a workspace, it handles tickets there, and the Ravenna app points people to it.

The [Custom Branded Service Desk App](https://docs.ravenna.ai/integrations/slack/branded-app.md) page describes the app with its main flag on. One part sits behind an extra flag. Where it changes what you see, the page calls it out in a callout like this one.

| Flag | What it controls | Default |
| - | - | - |
| slack-branded-app | **Main flag.** The **Branded app** section on the Slack integration, branding, deployment, and the **App management** permission for privileged Slack access. If you can see **Branded app** on the Slack integration, it's on for you. | Off |
| integrationDetailPage | Opens the **Branded app** settings as their own settings page from the Slack connection list, instead of inside the Slack integration panel. | Unconfirmed |

> [accordion] Where extra flags change the docs
>
> | Flag | Where it's called out |
> | - | - |
> | `integrationDetailPage` | [Open the service desk app settings](https://docs.ravenna.ai/integrations/slack/branded-app.md#open-the-service-desk-app-settings), how you get to the **Branded app** settings |

> [accordion] How to test
>
> **1. Connect app management**
>
> Open the Slack integration and its **Branded app** settings. On the **Deployment** tab, click **Connect privileged access** on each Slack workspace or Enterprise Grid organization that shows **Needs Slack admin approval to deploy**, and grant **App management**. See [Connect privileged access](https://docs.ravenna.ai/integrations/slack/branded-app.md#connect-privileged-access).
>
> **2. Save branding**
>
> On the **Branding** tab, upload a square icon, enter an app name and short description, pick a background color, and add a slash command such as `/acmehelp`. Click **Save**. See [Set your branding](https://docs.ravenna.ai/integrations/slack/branded-app.md#set-your-branding).
>
> **3. Deploy**
>
> On the **Deployment** tab, click **Deploy**. Check that each workspace turns Installed, then Handles tickets once the app has joined every connected channel. See [Deploy the app](https://docs.ravenna.ai/integrations/slack/branded-app.md#deploy-the-app).
>
> **4. Use it in Slack**
>
> Post a request in a connected channel and check that your app replies with your name and icon. Run your slash command. DM your app and file a request. See [What changes in Slack](https://docs.ravenna.ai/integrations/slack/branded-app.md#what-changes-in-slack).
>
> **5. Check the Ravenna app pointer**
>
> Open a new DM with the Ravenna app, or run `/rav`. Check that it answers with **Support requests now go through** your app and a **Message** button that opens a DM with your app.
>
> **6. Change the branding**
>
> Change the app name and save. On **Deployment**, check that **Update app** is highlighted, click it, and check that Slack shows the new name. See [Update the app](https://docs.ravenna.ai/integrations/slack/branded-app.md#update-the-app).

> [accordion] Known limitations
>
> These work as designed. Don't report them as bugs:
>
> * Each Slack organization gets one service desk app. An Enterprise Grid organization shares one app across its workspaces.
> * A workspace keeps the Ravenna app for tickets until the service desk app has joined every connected channel there. A private channel the Ravenna app isn't in blocks the switch until someone adds the app to it.
> * Threads started before the switch finish with the Ravenna app, because Slack only lets an app edit its own messages.
> * Slack only accepts PNG, JPG, and GIF icons.
> * People can't install the service desk app from Slack's app directory. Ravenna installs it.
> * Removing a deployed service desk app is done by Ravenna. Contact your Ravenna representative to remove it.

> [accordion] What we're exploring
>
> These are ideas the team is working through during the alpha. They aren't commitments, and they can change or be dropped.
>
> * **Ravenna AI in the Ravenna app:** once your service desk app handles tickets, the Ravenna app could become an AI assistant in Slack instead of pointing people to your app.


## Related topics

- [Custom Branded Service Desk App](https://docs.ravenna.ai/integrations/slack/branded-app.md)
- [Betas](https://docs.ravenna.ai/documentation/get-started/betas.md)
- [Guides](https://docs.ravenna.ai/guides/overview.md)
- [Foundry guide](https://docs.ravenna.ai/guides/how-to/foundry/overview.md)
- [Deal desk](https://docs.ravenna.ai/guides/playbooks/revops/deal-desk.md)


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