Settings - Apps

Settings > Apps is where you add your own apps to your customer: purpose-built Widgets (Custom Apps) and HTML apps. Once an app is uploaded and enabled, it appears in the widgets sidebar of the Content Designer and the Slide Designer, ready to drag onto a page.

Apps you add here belong to your customer only. No other customer sees them.

Who can use it

• Role: only the Administrator role. Other roles don't see the menu.
• Package: the Business and Enterprise packages. It isn't available on Essential.
• UI Profiles can hide the menu, the add button, or the management actions, even from an Administrator.

Learn more: Settings permissions — Apps

Two kinds of apps

Type	What it is	What you upload
Widget	A Custom App built on the official Wallboard boilerplate and SDK. It has its own settings in the editor, and data you can bind like any other Widget.	The app ZIP your build produces
HTML/CSS/JS bundle	A self-contained web page made of HTML, CSS and JavaScript.	A ZIP with index.html at its root, with every asset referenced by a relative path

The All, Widgets and HTML apps buttons at the top of the page filter the list by type. You can switch between card and table view, and search by name.

The workflow at a glance

1. Build the app package
2. Add the app
3. Upload the package
4. Enable the app
5. Use it in content
6. Keep it up to date

1. Build the app package

• Widget: built from the official Custom App boilerplate. The quickest route is an AI coding agent connected to Wallboard MCP, which builds, checks and packages the app for you. It hands back two ZIPs: the app ZIP you upload here, and a source ZIP to keep for later changes. Never upload the source ZIP as the app. Learn more: Develop a Custom App with AI
• HTML app: any static web page, packaged as a ZIP with index.html at the root of the archive.

Prefer not to build it yourself?

Our Services team can deliver an app as a paid development project — contact [email protected]. Custom App development and troubleshooting are not part of standard support; see Develop a Custom App with AI for what that means.

2. Add the app

1. Go to Settings > Apps and click the button (Add app).
2. Choose the type: Widget or HTML/CSS/JS bundle.
3. Enter a Name and, optionally, a Description.
4. Choose the Widget category: the group of the widgets sidebar the app appears in. Custom apps is the usual choice.
5. Click Save.

The app is created empty and disabled. It needs a package before it can be used.

3. Upload the package

1. Open the app's actions on its card and choose Upload bundle.
2. Select the ZIP file and upload it.

For an HTML app, the upload window reminds you of the package rules: index.html at the root of the ZIP, and relative paths for every asset.

A Widget package identifies itself by the name and version in its config.json. Both are required, and you can't upload a package whose name and version match another app your customer already has.

4. Enable the app

Open the app's actions and choose Enable. Only an app with an uploaded package can be enabled; until then, the option explains why it isn't available.

Once enabled, the app is offered in the widgets sidebar to everyone in your customer who edits content. Disable takes it out of the sidebar again.

5. Use it in content

1. Open a Content or Slide in the designer.
2. In the widgets sidebar, find the app in the group you chose as its Widget category, or type its name into Search widgets.
3. Drag it onto the canvas.

For a Widget app: set it up on its Main tab, using the settings the app offers. If it shows data, bind it like any other Widget. Keep frequently changing data, such as prices or a queue, in a datasource like an internal table, so it can be updated without uploading a new version of the app. Learn more: Databinding, Internal Datasources

For an HTML app: the page plays as it was built. To change what it shows or does, edit its source files and upload an updated package (see below). The Main tab offers these settings:

Setting	What it does
Trust bundle	Lets the app access the editor or player session. Only turn it on for apps you trust. Turning it off also turns off microphone and camera access.
Allow microphone	Lets the app use the microphone. Needs Trust bundle and the browser's permission.
Allow camera	Lets the app use the camera. Needs Trust bundle and the browser's permission.

Use the Other tab for layout and appearance, as with any Widget.

6. Keep it up to date

The app's card offers:

Action	What it does
Edit	Change the name, description and Widget category, or enable and disable the app.
Replace bundle	Upload a new package for the app — see the caution below.
Download	Download the app's current package.
Copy App ID	Copy the app's identifier.
Enable / Disable	Offer the app in the widgets sidebar, or take it out.
Remove	Delete the app from your customer.

Replacing a Widget app

Content that already uses a Widget app is tied to the name and version in the app's config.json. To update that content in place, the replacement package must keep both the same. A package with a different name or version counts as a different app, and the content already using the old one doesn't switch over to it.

Give your AI agent the source ZIP of the current version when you ask for changes — see Develop a Custom App with AI.

HTML apps don't have this concern: their identity is set automatically and stays the same when you replace the bundle.

Apps provided by Wallboard

Wallboard can also make apps available to your customer. These don't appear in Settings > Apps and you don't manage them, but they show up in the widgets sidebar and are used the same way as your own.