# Managed connections

Managed connections give your workspace a resource provisioned by Strive. Choose a managed catalog entry and create the connection without supplying a separate service's credentials. Provisioning still needs to complete successfully before the resource can be used.

## Available resource types

**Platform Store** holds files and supports file and storage browsing. It is the managed storage used for App files and imported snapshots. “Local” in a storage experience refers to this managed store, not access to your computer's entire filesystem.

**Platform Database** provides structured tables. Use its connection view to inspect tables and their rows. This database surface is different from the user tables held inside an individual App; deleting a database table and deleting an App table are different operations.

**Platform Search** supplies a managed search provider. It supports search queries rather than a browseable list of all internet content.

**Platform Vector Store** holds vectorized information for retrieval. Its contents are representations used for similarity search, rather than a replacement for the source document viewer.

## Using a managed resource

Name each connection for its purpose, inspect its detail page, and test it before connecting an automation. Select it explicitly in a workflow or App where a connection is required. Creating the resource alone does not define the workflow that reads or writes it.

Managed does not mean consequence-free. Emptying or dropping managed database tables, deleting files, or clearing vectors changes the stored data. Before deleting a managed connection, inspect its referencing workflows and read the confirmation about resource cleanup. If you only need to stop a workflow, pause or edit that workflow rather than destroying its resource.

See [connection data](/docs/connections/browse-data) and [revoke or delete](/docs/connections/revoke-and-delete) for the relevant distinctions.