Manage Apps screen

Use Manage Apps to publish App packages under an Account, download a configured sample App, review published App metadata, and control which Sites show an App in Console navigation.

This screen manages shared App publish and Site assignment. The backing Workflows can use v1 Runtime or v2 Runtime, although the current generated sample and agent-assisted build journey target v2 Runtime Workflows.

Open Manage Apps

Open Settings → Manage Apps.

The navigation item requires App publish permission. The list contains Apps owned by Accounts for which you have permission to publish Apps. Site assignment additionally requires App grant/revoke permission, and users need Site App list permission for assigned Apps to appear in Site navigation.

App list

The list provides these columns:

Column	Description
App	Shows the user-facing DisplayName. Recently changed Apps can include a recency badge.
Version	Shows the internal Name followed by the published Version.
Ownership	Shows Owned when the App belongs to an Account available to you.

Use the search field to filter by DisplayName or internal Name. Click an App row to open its details. Click refresh to reload the list.

When the list is empty, the page displays No Apps here. The generic empty state can also show New App and Learn more; use the page-level Publish App action for package upload, while Learn more opens the Building Apps documentation. Download a sample App is available when you have access to at least one Site.

Page actions

Action	Availability and effect
Publish App	Opens the package upload dialog.
Download a sample App	Available when you have access to at least one Site. Opens the configured sample download dialog.
Help	Opens the Building Apps documentation.
Refresh	Reloads the Apps visible to your Account permissions.

Publish a new App

The Publish new App dialog contains:

Field or action	Description
Account	Required. Selects the Account that will own the App.
App package	Required ZIP file. The Console upload limit is 30 MB. The package must contain a valid root app.json and landing page.
Submit	Publishes the uploaded package. It remains disabled until both the Account and uploaded package are available.
Cancel	Closes the dialog without publishing.

Publishing uses the Name in app.json to create a new App or update an existing App. See App manifest and package for the package layout and update rules.

The Console displays an alert when Account loading, package upload, or publish fails.

Download a sample App

The Download a sample App dialog creates a project configured for a selected Site and Environment.

Field	Required	Description
Site	Yes	Defaults to the current or preferred Site. Changing it reloads the Environments available to you and clears the API-key selection.
Environment	Yes	Defaults to the current Environment when it belongs to the selected Site, otherwise to the first available Environment. Changing it clears the API-key selection. Use a Test Environment for development.
API key	No	Lists Cookie-based Keys in the selected Environment that include your user. Selecting one injects an OpenAPI definition for the v2 Runtime Workflows permitted by that key.
OpenAPI version	Yes	Selects the generated OpenAPI format and defaults to OpenAPI 3.

Click Download after the required fields are selected. The downloaded ZIP contains the sample project and .env.local values for the selected Tenant, Site, and Environment. If you selected an API Key, its permitted v2 Runtime Workflow routes are used to generate openapi.yml.

See Apps for local development steps.

App details

The App detail page displays read-only publish metadata:

Field	Description
Display name	User-facing name shown in Console navigation.
Name	Stable internal identity from app.json.
App key	Service-generated identifier. Use the copy control when you need the exact value.
Version	Currently published manifest version.
Modified date	Time of the latest recorded App change.
App URL	Public landing-page URL generated from the published package. Use the copy control to copy it.

Click Audit trail to open the App's publish and Site-assignment history in a new tab.

Site assignment

The Sites area lists each Site to which the App is currently published. Each row shows the Site name and key.

To add the App to a Site:

1. Select an unassigned Site from Publish to a Site.
2. Click Publish.

The button remains disabled until you select a Site. After the request succeeds, the details reload and the Site moves into the published list.

To remove an assignment, click the remove control on the Site row. Removal is submitted immediately and the details reload after it succeeds.

Site assignment controls whether the App appears in that Site's Console navigation. It does not grant access to the App's backing Workflows; embedded calls still require a Cookie-based Key that permits the signed-in user and target Workflow.

Delete an App

Delete an App package from its details page when it is no longer needed. First remove every Site assignment. The delete action remains unavailable while any Site is assigned, including a Site you cannot currently see or manage.

1. Open the App in Manage Apps.
2. Remove its Site assignments from the Sites area, arranging removal by another authorized administrator where necessary.
3. Click Delete and review the confirmation.
4. Confirm deletion to remove the App and return to the App list.

Deleting the App package is separate from deleting its backing Workflows. If the App was assigned to a Site while you were reviewing it, deletion can fail and the Console reloads the details. Review the updated assignments and the reported error before trying again.

Alerts and failures

The Console displays operation-specific alerts when it cannot list or load Apps, load Accounts, upload or publish a package, generate the sample, or change a Site assignment.

If package upload succeeds but publish fails, the dialog remains open so you can review the alert. Correct and upload the package again when the manifest or ZIP is invalid. If a list, detail, or Site-assignment request fails, refresh or reopen the screen after resolving the reported permission or service problem.

Publish states are separate

App package publish, Site assignment, Workflow release, and API-key authorization are separate operations. Republishing an App does not release backing Workflow revisions. Assigning an App to a Site does not publish its package to another Account or expand its Workflow permissions.

See Flowgear Apps and App security model for the complete lifecycle and authorization model.