# How to Work with Rudder Lookout


{{< customreadfile "/includes/lookout/beta-callout.md" >}}

Lookout is a conversational surface wrapped around your warehouse and your RudderStack workspace. Almost everything starts as a chat message; the agent does the work, and the durable results land where your team already works.

## In this section

| Guide | <div style="width: 350px;">Description</div> |
|-------|------------------------------------------------|
| [Chat and Ask Questions]({{< ref "lookout/working-with-lookout/chat.md" >}}) | Ask in plain English and get a chart or table grounded in a live warehouse query. |
| [Dashboards]({{< ref "lookout/working-with-lookout/dashboards.md" >}}) | Turn answers into saved, parameterized dashboards that re-run on every load. |
| [Context Hub]({{< ref "lookout/working-with-lookout/context-hub.md" >}}) | Generated documentation, team notes, agent memory, and reusable skills. |

## Review and approval

The same rule applies across all these tasks — the agent drafts and proposes, and you review and decide. The agent can read your warehouse and your repositories, but consequential actions — saving an audience, sending one to a destination, publishing a dashboard — are staged for a human to dispatch.

Note that:

- **Read access is read-only**: The agent queries your warehouse; it never writes to or alters your data.
- **Source control is read-only**: The agent reads your repositories for context. It cannot open pull requests, create branches, or commit.
- **Sharing is explicit**: Publishing a dashboard is an action a person takes, never something the agent flips on by itself.

See [Security and Data Handling]({{< ref "lookout/security.md" >}}) for more details.

<br />