You don’t have access to Quarry yet
Your role doesn’t include Query Lab, Slate or Documents. Ask a Quarry admin to give you access.
Settings
Your Quarry account and connected services.
—There aren’t any guides for the pages your Quarry role can use yet. Ask a Quarry admin if you need access.
Query LabAsk Keystone in plain English or write SQL, read-only.
Step-by-Step
Query Lab runs read-only SQL against the databases an admin has connected, starting with Keystone. Every statement is a single SELECT with row and time limits.
Choose the connection, database and schema at the top of the Console. The schema tree on the left lists tables, grouped by dbt layer when dbt docs are connected.
Type a question in Ask AI and Quarry writes the SQL from your dbt docs, runs it, and fixes it if it fails. Or write SQL yourself, with autocomplete.
Results show as a table with an AI summary of the highs, lows and anything unusual. Download them as CSV or Excel.
Click Tell me why? to have the AI break the numbers down, follow dbt lineage and check for data gaps. You get the likely driver and the queries behind it.
Click Send to Slate to turn the query into a slide.
Console, Logs and Links
Tabs and sessions for your queries. Each tab has its own link, and Share Session sends a set of queries to someone else.
Every query Quarry ran, with its SQL, time, rows and errors. Admins can see everyone’s.
Result snapshots you shared, with who can open them. Revoke one at any time.
SlateTurn a query into a board-ready Google Slides deck.
Step-by-Step
Slate starts from SQL. The AI picks the chart and writes the headline and takeaways; every number on the slide comes from your query, never the model.
Paste SQL into Slate, or click Send to Slate in Query Lab to bring the query and its context along.
Run it and confirm the rows are what you expect. Lock freezes the SQL so the published numbers can be reproduced.
Pick the audience, the chart type (or let the AI decide) and the comparison, then generate. Change it in plain English, e.g. “make it a stacked column by segment”.
Add the slide to your deck, along with section dividers and text slides. Reorder them as you go.
Name the deck and publish. Quarry creates the deck and its data Sheet in your Google Drive (connect Drive in Settings › Account) and opens it when it’s ready.
DocumentsKeep saved queries in folders.
Saving and Organizing
Queries you save in Query Lab land in Personal. Make folders (and folders inside folders) from the + next to Personal in the sidebar.
Admins see every saved query in Everyone, grouped by who owns it.
Open a saved query in the Console, or move, rename or delete it from its row.
ConnectionsAdmins: connect databases and choose what people can query.
Step-by-Step
Nothing can be queried until an admin turns it on here.
Open Connections from the account menu and add an AWS account. Quarry connects through an IAM role wherever it can, not shared passwords.
Quarry lists the databases it finds. Turn on the ones people may query and choose their schemas.
Point Quarry at the manifest.json your dbt deploy publishes. The AI then reads model descriptions, grain and column docs before writing SQL.
Access ControlAdmins: decide who can sign in and what each role can do.
People and Roles
Add someone by their work email and pick a role. Change or remove a role at any time.
Superadmins choose what each role is allowed to do. Changes apply without a redeploy.
See Quarry exactly as a lower role does. The worker enforces it, and anything you save is still saved as you.
Add Someone
People with Access
| Person | Role | Status |
|---|
| Permission |
|---|