Database Access for BI Tools

Database Access lets you connect modern business intelligence (BI) tools—such as Metabase, Tableau, or Power BI—or any SQL client directly to your organization's DevStride data. You generate a set of read-only PostgreSQL credentials, plug them into your tool of choice, and build custom dashboards, cross-reference metrics, and generate insights beyond the reports built into DevStride.

How it works

When you generate credentials, DevStride creates a dedicated read-only PostgreSQL role scoped to your organization. The connection points at a read replica of the database (not the live primary), so your queries never affect production performance. Access is limited to SELECT only, and row-level security policies keep every query isolated to your own organization's data.

Open Database Access

1. Open Organization Settings.
2. In the Integrations section of the left settings rail, select Database Access (the database icon, listed alongside GitHub, Slack, and Identity Providers).

The page header reads Manage Database Access.

The rail only shows what your role can manage, so if the entry is missing you don't have Manage database credentials. Ask an Owner or Admin to grant it to your role.

Generate credentials

If no credentials exist yet, the page shows a Database Access card explaining that you can generate read-only database credentials to access your organization's data and connect using any SQL client or BI tool.

1. Select Generate Credentials. (The button shows Generating... while it works.)
2. DevStride creates a read-only role, a secure password, and the row-level security policies that scope access to your organization. The credential first appears as Pending and flips to Active once provisioning completes.
3. The Connection Details modal opens immediately so you can copy everything you need.

Connection Details

The Connection Details modal gives you two ways to copy your connection information:

• Quick Copy — a single, copyable Connection String for tools that accept a full connection URL.
• Individual Fields — each parameter on its own, for tools that ask you to fill in fields:
  • Database Type (postgresql)
  • Host
  • Port (defaults to 5432)
  • Database
  • Username
  • Password (masked by default; reveal it on demand)
  • Schema (always public)
  • SSL (Enabled or Disabled)

The modal also suggests a display name for your BI tool, formatted as DevStride - {Your Organization Name}, with a Copy button so the connection is easy to recognize in your tool.

Manage existing credentials

Once a credential is active, the card shows the role name, a colored Status label, the date it was created, and a row of action buttons. The active section is titled Read-Only Database Access.

• View Details (eye icon) — reopen the Connection Details modal to copy the connection string or reveal the password. This is available only while the credential status is Active.
• Regenerate Credentials (sync icon) — rotate the password. The previous connection string stops working, so you'll need to update any tools that used it. DevStride warns you before regenerating.
• Sync Tables — shown only when there are tables that haven't been synced yet.
• Revoke Access (red) — disable the credential's ability to log in without deleting it. The status changes to Deactivated.
• Activate Access — re-enable a revoked credential. This appears only when access has been deactivated.
• Delete (red X) — remove the credential entirely. Deleting drops the PostgreSQL role, removes all associated policies and permissions, and deletes the credential record. This action cannot be undone.

Status values

As credentials are provisioned and managed, you may see any of these statuses:

• Active — ready to use.
• Pending — being provisioned.
• Syncing — tables are being synced.
• Failed — provisioning didn't complete; generating again replaces a failed credential.
• Deleting — the credential is being removed.
• Deactivated — access has been revoked (login disabled).

Security and scope

• Read-only. Credentials are granted SELECT access only—they can't change your data.
• Isolated to your organization. Row-level security policies key every query to your organization's data.
• Read replica. Connections go to a read replica, not the primary database.
• Restricted to roles that manage database credentials. Generating, viewing, regenerating, revoking, activating, syncing, and deleting credentials all require the Manage database credentials permission. Owner and Admin both hold it by default, and you can grant it to a custom role in Configure Settings → Permissions.

Related pages

• GitHub

Upcoming table renames

DevStride is renaming its status and workstream vocabulary throughout the product — the API and MCP tools already use the new words, with deprecation windows listed on the API keys page — and the read-only database will follow in a later release: the tables lanes, lane_collections and folders become statuses, status_collections and workstreams, and the kept tables gain canonical twins of their lane_* and *_folder_* columns. Nothing changes for your queries on the day of that release: the current table names stay available as read-only views with identical columns, and the current column names keep working alongside their twins.

The legacy 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 in a release after the rename itself. If you maintain dashboards or scheduled queries against these tables, plan to move them to the new names during that window.