# Platform Database

A dedicated Postgres schema the platform manages for you. Zero setup — pick it as a source or destination in any workflow.

## What this connection offers

Strive supplies the managed database connection. Use it for reading or delivering workflow records, and inspect its tables and individual rows from Connections. Emptying a table and dropping it have different effects.

| Detail | Value |
| --- | --- |
| Available uses | records |
| Sign-in | Managed by Strive |
| Catalogue identifier | `platform_database` |
| Connection scope | tenant |
| Direction | both |

## Connect

1. Open **Connections**, choose to connect a service, and select **Platform Database** with the uses listed above.
2. Give the connection a recognisable name.
3. Complete creation; no external secret is required for this entry.
4. Check the connection status and run a connection test where offered.
5. Select this saved connection in the app, workflow step, storage browser, or Assistant task that needs it.

## Connection settings

This connector declares no ordinary configuration fields. Its sign-in or managed provisioning flow supplies the access it needs.

## Diagnose a failure

Check the connected account, its permission to the target, the selected folder, table or collection, and the connection’s current status. A successful sign-in is not proof that a particular resource is shared with that account. An empty search or folder page is not necessarily an authentication error. Revoke access when it is no longer needed; deleting the connection can also affect its tools and synced data. See [connection lifecycle](/docs/connections/revoke-and-delete).