Browse the catalog
Open Postgres in the sidebar. The catalog shows one card for each data source available to the selected carrier. Use Search data products to filter by name or description.
The Postgres catalog. The Table preview on the right follows the selected source.
- carrier-scoped — the view contains only the selected carrier’s rows.
- global — reference data that is the same for every carrier.
- Provisioned — you already have a view for this source.
- Selected — the source shown in the Table preview panel.
Available sources
Set up access
Open a source’s details page to configure the view and its login. The left rail lists every source, so you can switch between them without returning to the catalog.Choose columns

Choose the columns to include in your view
Set an automatic expiry (optional)
Provision the view

A provisioned view, ready for its database login
Create the database login
Save the credential

The credential is shown once. Save it in your password manager or secret store.
Connect to the view
Use the Host, Port, Database, Username, and Password from the credential. SSL is required. Your login can read only its own view, which lives in thecedar_apps schema and is named like
cedar_apps.data_depot_<source>_<carrier>_<id>.
- psql
- JDBC
- Python
Private network connectivity
By default, your tools connect to the view over the internet, encrypted with SSL. If your security policy requires BI traffic to stay on a private network, Cedar can set up a private connection to your Postgres views. This is a custom setup arranged per customer: contact your Cedar account team, and we’ll work out the details with your network team.Postgres views or CDC delivery?
A Postgres view is live: every query your BI tool runs is answered by Cedar’s database. That makes views the quickest way to get current data, but it also means your dashboards depend on Cedar’s Postgres service, including its availability, performance, and maintenance windows. If you want full control of your data, with your own storage, your own retention, and your own SLA, use CDC delivery instead. Cedar pushes the data to your Azure or Amazon S3 storage, and your BI tools read from your own copy, so they keep working even while Cedar’s database is unavailable.Change the columns later
Return to the source, change the selected columns (or the automatic expiry), and select Update view with N columns. The view is updated in place, and the login and password don’t change, so your connected tools keep working. Queries that name a column you removed will start to fail, so update them at the same time.Manage existing access
The History section at the bottom of the source’s page lists every view created for that source on this carrier, including revoked ones, with who created it and when.
History lists current and past views for a source
Reset the password
Select Reset credential, then confirm. The current password stops working immediately, and the new password is shown once. Update every tool that uses the login.Revoke access
Select Revoke access, then confirm. Data Depot removes the view and its login. You can provision the source again later. Revoking can take a moment; the status shows Revoking until it finishes.Statuses
Limits
- One active view per source per carrier. To change it, update its columns rather than creating a second view.
- One login per view.
- While an earlier view for the source is still being revoked, or its cleanup needs attention, you can’t provision the source again. The button reads Cleanup required and the page says Finish or retry the existing access cleanup in History before provisioning this source again. Open History and select Retry revoke.
- Once a view’s automatic expiry passes, the button reads Provision expired until Data Depot finishes removing the view. After that, you can provision the source again.
- Views are read-only. You can’t write to Cedar through them.
Join sources together
The sources share key columns, so you can join views you’ve provisioned for the same carrier.parent_grouping_idwalks your location hierarchy. The top-level road row isn’t included, so a top-level location’s parent may not appear in the view.- Location template attributes become columns named
<location type>.<attribute>, for examplestation.region, so attributes with the same name on different location types stay separate. - The view includes deleted locations as well as current ones.
Troubleshooting
Password authentication failed
Password authentication failed
Permission denied for the view
Permission denied for the view
cedar_apps schema.A column disappeared
A column disappeared
I can browse sources but can't provision
I can browse sources but can't provision
A source I expected isn't listed
A source I expected isn't listed