# Install & manage apps

Keep track of what is installed, what is being built, and who can use it.

Source: https://docs.opser.com/apps/managing/

## Discover and install
Open the **App Store** to see apps offered to your workspace. Review an app’s description and requirements, then use the installation controls if you have permission. Installation availability depends on the catalog and app requirements. Every plan includes unlimited installed apps.

After installation, check **Settings → Apps** and the sidebar. An app can be installed without being visible to every user; access permissions determine who can open it.

## Installed apps and work in progress
Settings → Apps separates the workspace’s app management from discovery in the store. Inspect installed apps, work being built, and operation history. A draft or preview is not the same as the version your team uses in production.

**Your apps · Fictional data**

Northstar has a customer portal and feedback board built for its workflows. These fictional examples do not describe a fixed app catalog.


For agent-built apps, follow the [internal app](https://docs.opser.com/capabilities/internal-apps/) or [external app](https://docs.opser.com/capabilities/external-apps/) guide and review the publication result.

## Updates and permissions
Apps update automatically: when a new version is published, it installs by itself and the people who manage apps get a notification. To update apps yourself instead, turn off **Update apps automatically** in **Settings → General**, under **Workspace**; each new version then arrives as an update notification for you to install. An app you customized never updates automatically, because its update has to be reviewed and merged with your changes. If an automatic update fails, you get an update notification to install it yourself.

Before changing an app, understand the affected workflow and data. Verify key screens and agent tools after an update. Review grants for newly introduced capabilities rather than assuming every user should receive them.

## Removing an app
Read the removal confirmation and understand the effect on its records, connected workflows, dashboards, and automations. Export or preserve information your team needs before a destructive removal. Do not treat uninstalling as a reversible way to hide an app from one user; adjust that user’s access instead.

## If an installation fails
Inspect the reported operation error. Common causes include missing access, a required dependency, or an invalid build. Check [troubleshooting](https://docs.opser.com/help/troubleshooting/) and include the app name and error when asking for help.