Install and manage workspace apps

Install in the intended workspace

Apps are installed for a workspace. Before testing your app as a customer, select the workspace from the workspace menu, then open the app's marketplace listing.

1. Review the listing and its Pricing tab.
2. Choose an available plan. An explicit Free plan still requires enrollment.
3. Complete checkout when payment is required.
4. Wait for the installation and access check to complete, then open the app.

A checkout return is not proof that the subscription is active. If access is still pending, allow fulfillment to complete and check again. Avoid starting another purchase while the first is pending. See billing and entitlements for server-side access checks.

Installing in one workspace does not install in another. Membership in the publisher's workspace also does not automatically enroll that workspace in the app's subscription.

Open and manage an installed app

Open Settings > Apps to see the selected workspace's installed apps. Open app launches the app after an access check. You can also launch installed apps from Home.

Billing and uninstall controls depend on the current user's management permission and the installation's state. A member may be able to use an app without being able to change its billing or remove it. When a billing-management action is available, use it to inspect the subscription before making changes.

Do not assume uninstalling an app cancels every charge or deletes the app's stored data. Verify the subscription outcome and the app's data-retention policy separately. Developers should explain both behaviors in their own product documentation.

Verify the customer journey

Test using a workspace that does not own the app:

• An unenrolled workspace reaches plan selection for subscription-protected routes.
• A Free enrollment grants the intended features and quotas.
• A paid checkout grants access only after server-side confirmation.
• Switching workspaces changes which installation and entitlement apply.
• A member can launch the app while management controls follow their permissions.
• Failed access checks offer a useful recovery path.

Keep public marketing and health routes separate from protected application routes. See App access and service URLs for policy examples.

Recover from a launch problem

For sign-in prompts, renew the user session. For pricing redirects, verify the selected workspace and its subscription. For permission errors, ask a workspace administrator to check access.

If the app opens but returns its own error, inspect its service health and logs. Installation success does not verify every downstream service. Use Troubleshooting to distinguish enrollment, route-policy, and application failures.