On this page

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.

Who can do this

Every action on this page needs the Manage database credentials permission (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.

How it works#

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.

Generate credentials#

  1. Open Configure Settings → Integrations → Database Access. The page is headed Manage Database Access. If the entry is missing, your role lacks Manage database credentials.
  2. Select Generate Credentials (the button shows Generating... while it works).
  3. The credential appears as Pending and flips to Active once the role and policies are provisioned. The Connection Details modal opens immediately so you can copy what you need.

One credential set per organization

Each organization has at most one set of credentials. If one exists, Generate Credentials returns an error asking you to delete it first. A credential that ended up Failed is replaced automatically when you generate again.

Connect your tool#

The Connection Details modal offers two ways to copy the connection:

  • Quick Copy — a complete Connection String for tools that accept a URL.
  • Individual Fields — for tools with a form:
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.

You can come back for the password

The password is stored encrypted and anyone with Manage database credentials can reveal it again through View Details while the credential is Active. Treat it like any other secret and share it only with people who should have the data.

Manage existing credentials#

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 values#

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.

Security and scope#

  • Read-only. SELECT only; nothing can be changed through these credentials.
  • Your organization only. Row-level security keys every query to your organization.
  • Read replica. Queries never touch the primary database.
  • Gated by one permission. Generate, view, regenerate, sync, revoke, activate, and delete all require Manage database credentials.
  • Statement statistics are private. The pg_stat_statements and pg_stat_statements_info views are not readable with read-only credentials, because they exposed other logins' query counts.

Item type hierarchy#

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;

Changed on 2026-10-06

The 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.

Status table renames#

Changed on 2026-11-17

The old status and workstream names were removed from the read-only database. Queries, dashboards and scheduled reports that still name an old table, column or type now fail: switch them to the new name in the tables below.

DevStride renamed its status vocabulary in the read-only database on 2026-10-07, as announced in the 2026-09-07 notice. The old names were kept working alongside the new ones until 2026-11-17, when they were removed:

Old name (removed) 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 new tables and columns hold the same data the old ones did, so a query needs only its names changed. If a new name returns a permission error, select Sync Tables.

Workstream tables#

The workstream half of the rename shipped the same day and was removed on the same day:

Old name (removed) 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

If workstreams returns a permission error, select Sync Tables.

History and notification values#

Changed on 2026-11-11

Item history, notifications and the activity log now store the new words, including every record written before the change. A query that filters on an old value below now returns no rows (for notifications.action, an error since 2026-11-17: see Old values removed from the column types): switch it to the new value.

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 values in history, jobs, automation runs and imports#

Changed on 2026-11-16

The activity log, background jobs, automation runs and import runs now store 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 (for activity_logs.type, an error since 2026-11-17: see Old values removed from the column types): 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, and a final clean-up on 2026-11-17 covered records written while that release was rolling out, so every record now reads workstream.

Old values removed from the column types#

Changed on 2026-11-17

The old words are no longer allowed values of the three columns below. A query that compares one of these columns with an old value now fails with an error such as invalid input value for enum activity_log_type: "folder", where before it returned no rows. Switch the query to the new value.

Column (type) Removed values Use instead
activity_logs.type (activity_log_type) folder workstream
notifications.action (item_notification_action) lane_modified status_modified
integration_provider_links.devstride_entity_type (devstride_entity_type) lane, folder status, workstream

The columns keep their names and their type names, and no stored row held a removed value, so queries that already use the new values, and your BI tool's saved connection, need no change. A BI tool that lists a column's allowed values in a filter picker shows only the current ones once it refreshes its schema.

  • GitHub
  • Connect AI & the MCP Server — the MCP tools get_database_credentials, generate_database_credentials, and delete_database_credentials manage the same credential
Powered by DevStride