--- title: "Guided walkthrough session — Rig guide" description: "The 30-minute guided session that takes a team from logged in to working on their own: the agenda block by block, what to prepare, and how to run it yourself." canonical: "https://rig.so/guides/walkthrough-session" format: markdown --- Search guides, references, playbooks…⌘K Browse guides Guided session · Onboarding # The 30-minute guided walkthrough A single half-hour session that takes your team from having a Rig login to actually driving it. Six blocks, thirty minutes, run on your own workspace with your own data. This page is the plan: what it covers, how to prepare, and how to run it yourself if you would rather not book one. ## What the session is It is not a demo. A demo shows what the product could do; this session gets everyone in the room to the point where they can open Rig on Monday and use it without help. Everything runs on your workspace, reading your data, so the screens people see are the screens they will see afterwards. Nothing is built or changed during the half hour: questions get asked, apps get run, queries get inspected. That keeps the pace up, and nobody has to worry about breaking something while they are still learning where things are. The single most important idea in the session is the difference between live and validated. Live means a report is connected to your warehouse and can run against it. Opening a data app shows its most recent saved run; use Run Now to query the warehouse again. A new run is only as fresh as the source data last synced into the warehouse. Validated means someone has compared those numbers against your existing report, over several periods, and agreed they match. A report can be live on day one and not yet validated, and that is a normal state to be in. ## The 30-minute agenda One person drives on a shared screen. It works the same remote or in a room. The timings are deliberately tight — if a block overruns, the later ones get trimmed rather than the session running long. | Time | Block | What you see | | --- | --- | --- | | 0:00–3:00 | Frame | No screen. What is live today, what is still being validated, and what happens next. | | 3:00–8:00 | Navigate | The left rail, its three groups, the settings pages, and the command palette. | | 8:00–15:00 | Ask | A question answered in chat, the SQL behind the answer, and a follow-up in the same thread. | | 15:00–22:00 | Data apps | Opening an app, running it, inspecting its queries, and tracing one number back to a row. | | 22:00–26:00 | Claude connector | Optional. Connecting Rig to Claude and asking the same question from there. | | 26:00–30:00 | Admin and close | A minute on roles and access, then next steps and where to send questions. | ## What each block covers ### Frame — 0:00 to 3:00 No screen for the first three minutes. Which of your reports are live, which are still being compared against the old system, and what is needed to finish that comparison. This is the reason the session exists — everything after it is easier once the room agrees on where things stand. ### Navigate — 3:00 to 8:00 The left rail, read top to bottom. It has three groups: one for using the product, one for improving the answers it gives, and one for the data sources behind it. Below that sit your inbox, help, settings and the workspace switcher. The rail only shows what your role allows, so if a colleague mentions a link you do not have, that is your role rather than a fault. The block ends on the command palette, which is the fastest route back to anything you have seen once. Backed by [Start here: your first 15 minutes](https://rig.so/guides/start-here). ### Ask — 8:00 to 15:00 A question typed into chat, answered live, with the generated SQL opened up afterwards. Then a follow-up in the same thread, to show that it keeps context. The point to take away: every answer shows you its query, so when a number looks wrong that is the first place to look — and the fix is usually a definition rather than a bug. Chat reads your data and does not change it unless someone explicitly turns actions on. Backed by [Ask your data](https://rig.so/guides/chat-basics). ### Data apps — 15:00 to 22:00 One of your own apps, opened and run while everyone watches. Then the recent runs, the queries behind the page, and the underlying rows — tracing a single number on the page back to the data it came from. The session finishes the block on sharing: who a page can be shared with, and how to see what is already shared. Backed by [Data apps: open, run, inspect, share](https://rig.so/guides/data-apps-basics). ### Claude connector — 22:00 to 26:00 Optional, and the first block to drop if time is short. Connecting Rig to Claude from your integrations settings, then asking the same question there and comparing it with the answer from the chat block. Same data, same rules, different window: connecting Claude does not widen anyone's access. Backed by [Connect Rig to Claude](https://rig.so/guides/connect-ai-tools). ### Admin and close — 26:00 to 30:00 About a minute on the access screens — roles, collections, the access matrix, and previewing what a given role can see — then the close: what is needed from you, which lessons to read first, and where questions go. Skip the admin part entirely if nobody attending administers the workspace. Backed by [Admin: people, roles, access](https://rig.so/guides/admin-people-and-roles). ## What you can do afterwards By the end of the half hour, everyone who attended should be able to: - Find chat, data apps, connections and settings without hunting for them. - Say in one sentence what live means and what validated means for one of your own reports. - Ask a question, read the answer, and open the query that produced it. - Open a data app, run it, and explain where one number on it came from. - Know why they cannot see everything a colleague can see. - Know where to send a number that does not match, and why that helps. ## How to prepare The session is short, so a little preparation buys a lot. Before the call, it helps to have: - Everyone logged in already. If someone signed up and is waiting for approval, get them approved beforehand rather than losing five minutes to it live. - Two or three real questions. Things your team actually asks each week. Better than whatever gets improvised on the day. - The reports you want to compare against. Whatever you use today for the same numbers, so validation has something to measure against. - The business rules behind your definitions. How a record gets categorised, what counts and what does not, which edge cases are excluded. These are what make an answer match your own reporting. - A view on who gets which role. Roughly who needs to read, who needs to build, and who administers the workspace. - A shared place for questions. A doc or channel where anything unanswered gets written down and picked up afterwards. Recording the session If you want a recording for people who cannot make it, agree that on the call before anyone presses record, and agree where it will be stored. The session shows live data from your workspace, so the recording is your data and should be stored wherever your own policy says it belongs. ## Who should attend Keep it small enough that people ask questions. A good room is: - The people who read the reports. Whoever opens the numbers each week. They get the most out of the first four blocks. - Whoever owns the definitions. The person who can settle what a metric means when the room disagrees. - One workspace admin. Someone who will be adding colleagues and setting roles. Without them, the last block has no audience and should be dropped. - Anyone who will build on top of it. Optional for this session, but they get more out of the data apps block than anyone. ## Running it yourself You do not need us in the room. The agenda above works as a self-run session: one person on your side drives, everyone else watches and asks. The lessons linked from each block are the long-form version of the same material, so reading them in order covers the same ground at your own pace. Two habits make it work. Run through the click path once on your own first, so the apps you plan to open have already returned data that day. And write down every question the room raises, even the ones you can answer — the list of what people wanted to know is the best guide to what to set up next. Afterwards, send the group three links in this order: [your first 15 minutes](https://rig.so/guides/start-here), [asking your data](https://rig.so/guides/chat-basics), then [data apps](https://rig.so/guides/data-apps-basics). That is about an hour of reading and it covers everything the session showed. Send it the same day, while it is still fresh. Was this guide helpful? Yes No --- - [This page as HTML](https://rig.so/guides/walkthrough-session) - [Site map for language models](https://rig.so/llms.txt) - [API and agent documentation](https://rig.so/developers)