Use Database Access when the reports built into DevStride are not enough: connect a BI tool — Metabase, Tableau, Power BI — or any SQL client straight to your organization's data and build your own dashboards.
You generate one set of read-only PostgreSQL credentials for the organization, paste them into the tool, and query.
MANAGE_DATABASE_CREDENTIALS), which Owner and Admin hold by default and which you can grant to a custom role in Roles & Permissions. It is deliberately separate from Manage Integrations: issuing a database login is a higher trust tier than connecting Slack. Members never see the page.Generating credentials creates a dedicated PostgreSQL role for your organization. The role can only SELECT, row-level security policies restrict every query to rows belonging to your organization, and the connection goes to a read replica, so your dashboards never slow down the live application.
Think of it as a window onto the same tables the product uses, with everyone else's data filtered out before you ever see it.
The Connection Details modal offers two ways to copy the connection:
| Field | Value |
|---|---|
| Database Type | postgresql |
Host, Port (5432), Database | As shown |
| Username | The generated role name |
| Password | Masked; reveal it on demand |
| Schema | public |
| SSL | Enabled or Disabled, as shown |
The modal also suggests a display name for the connection — DevStride - {Your Organization Name} — with a Copy button.
Once a credential is active, the card is titled Read-Only Database Access and shows the role name, a colored Status, the creation date, and these actions:
| Action | When to use it |
|---|---|
| View Details | Reopen Connection Details to copy the string or reveal the password. Active credentials only. |
| Regenerate Credentials | Rotate the password. The old connection string stops working immediately, so update every tool that used it. DevStride warns before regenerating. |
| Sync Tables | Appears only when there are tables your credentials cannot read yet — for example after a DevStride release adds one. Until you sync, querying a new table returns a permission error. |
| Revoke Access | Disable login without deleting anything. Status becomes Deactivated. |
| Activate Access | Re-enable a revoked credential. Shown only while Deactivated. |
| Delete | Drop the PostgreSQL role, remove its policies and grants, and delete the record. Cannot be undone. |
| Status | Meaning |
|---|---|
| Active | Ready to use. |
| Pending | Being provisioned. |
| Syncing | New tables are being granted. |
| Failed | Provisioning did not complete. Generate again to replace it. |
| Deleting | Being removed. |
| Deactivated | Login disabled by Revoke Access. |
SELECT only; nothing can be changed through these credentials.pg_stat_statements and pg_stat_statements_info views are not readable with read-only credentials, because they exposed other logins' query counts.Which item types can sit under which is stored in the work_type_parents table, one row per pairing of an item type and a type it may sit under. An item type can have several parent types (see Item Types), so a type can appear in several rows.
| Column | Meaning |
|---|---|
work_type_id | The item type (a row of work_types). |
parent_work_type_id | A type it may sit directly under (also a row of work_types). |
organization_id | Your organization. |
date_added, date_updated | When the pairing was recorded. A type's primary parent is its row with the earliest date_added. |
A type with no rows is a top-level type. To list every type with its parents:
select child.name as item_type, parent.name as parent_type
from work_type_parents p
join work_types child on child.id = p.work_type_id
join work_types parent on parent.id = p.parent_work_type_id
order by child.name, p.date_added;
work_types columns parent_work_type_id and children were removed. Queries, dashboards, or scheduled reports that select either column now fail: read work_type_parents instead. If your credentials were created before this change, select Sync Tables to start reading work_type_parents.DevStride has renamed its status vocabulary in the read-only database, as announced in the 2026-09-07 notice:
| Old name (still works) | New name |
|---|---|
lanes | statuses |
lane_collections | status_collections |
lane_id (on workitems, item_transactions) | status_id |
lane_rank (on workitems) | status_rank |
lane_collection_id (on boards, teams, board_folders) | status_collection_id |
automate_lanes (on organizations) | automate_statuses |
service_desk_lane_settings, service_desk_reopen_lane_id (on work_types) | service_desk_status_settings, service_desk_reopen_status_id |
type lane_types | type status_types |
The old table names are now read-only views with identical columns, and every old column is kept equal to its new twin, so dashboards and scheduled queries keep returning the same results. Your credentials can read both names; if a new name returns a permission error, select Sync Tables.
| Old name (still works) | New name |
|---|---|
folders | workstreams |
folder_count, archived_folder_count (on folders) | workstream_count, archived_workstream_count (on workstreams) |
root_folder_number (on workitems, notifications) | root_workstream_number |
next_folder_number (on item_counters) | next_workstream_number |
folders is now a read-only view over workstreams with identical columns, including folder_count and archived_folder_count, and each old *_folder_number column is kept equal to its new twin, so dashboards and scheduled queries keep returning the same results. Your credentials can read both names; if workstreams returns a permission error, select Sync Tables.
| Where | Old value (no longer stored) | New value |
|---|---|---|
item_transactions.transaction_type | added_to_lane, removed_from_lane | added_to_status, removed_from_status |
notifications.action | lane_modified | status_modified |
notifications.summary (item notifications) | Lane modified, New folder created, Folder description modified | Status modified, New workstream created, Workstream description modified |
activity_logs.data | laneId, laneRank (the field of a change, and the keys of the before and after snapshots); rootFolderNumber (in itemMetaData) | statusId, statusRank; rootWorkstreamNumber |
Older records were rewritten once, in place, so one new value now covers the whole history: you do not need to match both spellings.
workstream where they stored folder, including every record written before the change. A query that filters on folder in these places now returns no rows: switch it to workstream.| Where | Old value (no longer stored) | New value |
|---|---|---|
activity_logs.type | folder | workstream |
activity_logs.data | itemType and a relationship's entity of folder | workstream |
jobs.input, jobs.output, jobs.progress | itemType of folder; in recalculation jobs, the folders count, the folder entity type and the folder_count, archived_folder_count field names | workstream; workstreams, workstream, workstream_count, archived_workstream_count |
workflow_runs.input | itemType of folder | workstream |
import_job_runs.import_result, import_job_runs.errors | itemType of folder | workstream |
Only these system-written values changed: text people typed (descriptions, messages, custom field values) and the input a webhook sent to an automation are stored as they were. Older records were rewritten once, in place, during the 2026-11-16 release; a small number of records written while that release was rolling out may still read folder until a later clean-up rewrites them too.
The legacy status and workstream names are removed no earlier than 90 days after the 2026-09-07 notice sent to every organization with active credentials — so not before 2026-12-06 — and only after one further release; you will receive a second notice before removal. If you maintain dashboards or scheduled queries against these tables, move them to the new names during that window.
get_database_credentials, generate_database_credentials, and delete_database_credentials manage the same credential