Rudder Lookout Key Concepts
Private Beta
Learn about the core building blocks of Rudder Lookout — including workspaces, the agent, artifacts, and integrations.
The key concepts of Rudder Lookout covered in this guide make it easy to understand how the product works.
Workspace
A workspace is how your team works together in Lookout. It is the container for everything your team builds — chats, dashboards, warehouse connections, Context Hub notes, measurement plans, and source-control links — and it is the unit that decides who can see and change what.
Note that:
- Each workspace has a short, URL-friendly name (its slug) that appears in every link.
- All resources live inside exactly one workspace, and the workspace decides which warehouses, RudderStack account, and repositories the team’s chats can reach.
- A single person can belong to several workspaces and switch between them by navigating to a different workspace URL.
See Workspaces and Collaboration for roles and sharing.
The agent
The Lookout agent is a conversational assistant that works across your data stack. It can read your warehouse, explore your code repositories, draft dashboards, documentation, and measurement plans, open pull and merge requests, and operate the RudderStack control plane.
Two design rules keep it trustworthy:
- Least privilege, per task: The agent is given only the tools a task requires. With nothing connected, it can converse but has no external reach — connect a warehouse and it can query it, connect a repo and it can review it, and nothing more.
- A human approves consequential actions: The agent prepares the work and a person pulls the trigger — code changes arrive as pull or merge requests for review, dashboards and documents are drafts you approve, and public sharing is always an explicit human choice.
See How to Work with Lookout and Security and Data Handling for more details.
Artifacts
Lookout’s value is not the chat itself — it is what the chat produces. Every meaningful result is saved as a durable artifact your team can revisit, share, or hand to a teammate:
- Answers: Charts and tables produced from a live warehouse query
- Dashboards: Saved, parameterized views that re-run their queries on every load
- Documentation: Generated descriptions of how your events are instrumented, stored in the Context Hub
- Measurement plans: Structured definitions of tracking changes
- Pull requests: Code changes proposed against your repositories
Integrations
An integration plugs a real tool into the agent. Each connected system gives the agent a specific set of abilities, and the agent can only touch a system when that integration is configured for your workspace. See Integrations for setup details.
| System | What it unlocks |
|---|
| Warehouses | Run read-only queries against PostgreSQL, Snowflake, Redshift, BigQuery, and Databricks |
| GitHub / GitLab | Explore repositories, review pull and merge requests, and propose changes as pull/merge requests |
| RudderStack | Read sources, destinations, transformations, Tracking Plans, and audiences — and, with a read-write connection, manage them |
| Slack | Answer questions from a direct message or a bound channel |
| External AI tools | Let approved external AI tools call a curated set of Lookout’s tools |
Roles
Access within a workspace follows clear roles — Owner, Admin, Member, and read-only Guest access for unregistered users.
Every member can chat, build dashboards, and read documentation, while administrative actions like connecting a warehouse or managing members are reserved for owners and admins.
See Roles and Permissions for more details.
Questions? We're here to help.
Join the RudderStack Slack community or email us for support
