Publish and Assign an App v2

Build the static package, publish it under an Account, assign it to Sites, and verify its independently released Workflow backends.

Prepare the package

  1. Update app.json with the stable internal Name, new Version, user-facing DisplayName, and optional navigation Rank.
  2. Confirm that icon.svg and a supported landing page are in the public root.
  3. Run npm run build.
  4. Test the built output locally.
  5. Zip the contents of build, not the build directory itself.

The ZIP root must contain app.json and one of index.htm, index.html, default.htm, or default.html. icon.svg is optional. The Console upload limit is 30 MB.

Publish the package

  1. Open Settings → Manage Apps.
  2. Click Publish App.
  3. Select the owning Account.
  4. Upload the ZIP.
  5. Click Submit after upload succeeds.
  6. Open the App details and confirm display name, internal name, Version, App key, modified date, and URL.

Publishing an existing internal Name updates that App only when it belongs to the selected Account and the Version changed. Existing Site assignments remain.

Assign Sites

  1. In App details, select an unassigned Site under Publish to a Site.
  2. Click Publish.
  3. Confirm that the Site appears in the assigned list and the App appears in navigation for a permitted Site user.

Use the remove control beside a Site to revoke its assignment. Site assignment changes visibility; it does not grant Workflow invocation.

Verify the release set

For every assigned Site, confirm:

  • The backing Workflow revisions are published in the intended Environment.
  • The Workflows are enabled.
  • The Cookie-based API Key permits the App users and Workflows.
  • Environment-scoped user access and allowed origins are correct.
  • The frontend's expected API contract matches the published backend.

App publish, Site assignment, Workflow release, and API-key authorization are separate and audited.

See also

See App Manifest, Manage Apps Screen, and App Security Model.