# Install, configure, update, and remove apps

An app extends Gideon with service connections, tools, knowledge sources, channels, or its own interface. Review the whole lifecycle, not just the install button.

## Browse and inspect
Use Apps to browse the Store and available installed or native views. Open an app’s details, inspect its source and permissions, and check the configuration it needs. Hosted model-provider apps are managed by the operator rather than offered as customer-installed inference.

## Install from a trusted source
For manual hosted installs, provide a reachable repository URL. The install flow scans and requests consent for applicable components. Do not bypass a refusal without understanding its reason. An app’s network declaration is disclosure, not containment.

## Configure
Complete ordinary app configuration in the app form. Hosted sensitive fields point you to Connections; model fields remain operator-managed. Use the exact credential name the app expects and validate a real read-only operation afterwards.

## Use contributed surfaces
An installed app may contribute pages, tools, or source providers. Open its page from navigation or its detail view. An empty source-type list can mean no provider for that feature is registered, not that creating another blank configuration will fix it.

## Update
Read the update’s source and requested changes. Hosted updates require a reachable source URL. Data is preserved by the app update flow, but verify the connection and a representative task after updating.

## Remove
Before uninstalling, inspect automations and workflows that rely on the app. Remove or revoke external authorization where necessary; deleting an app entry alone is not a universal guarantee that the external service revoked its token.