Publish and maintain a Studio listing

Open the app in Studio

Select the app's owning workspace, open Studio, and choose your app. Keep the marketplace listing, deployment state, and application source in mind as separate things you maintain.

A listing change does not build or deploy your application. A successful deployment does not replace a review of the public listing, access policy, or checkout experience.

Edit listing details

The listing editor autosaves supported changes such as the display name, headline, visibility, and image. Wait for the save state to confirm completion before navigating away.

When saving fails, keep the editor open, check the error, and retry. Review the public listing after saving, including its image and its appearance at a narrow viewport. Image/banner actions can save separately from text fields.

The listing currently does not provide a complete long-form description editor. Do not assume that all marketplace content can be authored through this screen.

Maintain pricing

Use the manifest billing configuration for declared offerings, prices, and entitlements. Review the Pricing tab and the customer-facing listing after a confirmed update.

Check that Free is an explicit plan, recurring amounts include the interval, and feature limits match the app's server-side enforcement. The current public plan presentation can show an offering's default price; declaring several prices does not guarantee a monthly/yearly selector in every surface.

Do not present one-time credit purchases as a production-ready customer flow. See billing availability.

Source and deployments

The Source panel exposes available app endpoint information and connection state. A "Not connected" state is not a source editor or proof of automatic repository synchronization. Review source changes in your repository and deploy through the supported deployment workflow.

Use the Deployments tab to inspect history. Open a deployment for its status, source information, service stages, and events. Use the deployment ID when diagnosing a failure or asking for help. A saved listing, queued deployment, and successfully deployed app are distinct states.

Before sharing the listing

1. Confirm listing edits finished saving.
2. Open the public listing and inspect its content and Pricing tab.
3. Test installation and launch from a customer workspace.
4. Check that protected routes require the intended enrollment.
5. Confirm that cases appear in Home when your app implements them.
6. Verify that the latest deployment reached a successful terminal state.

Studio edits and atrium.yaml are not a bidirectional source-control workflow. Review differences before a later manifest deployment or atrium sync; see Manifest lifecycle.