> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nightshift.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Advanced Topics

> Becoming a Nightshift power user

The most important thing to internalize about Nightshift is that it's a platform built to be consumed by Agents.
This might be awkward at first because most of us are used to working with SaaS through the SaaS provider's UI.
We indeed have a UI we call `console` but it's more of a way for humans to audit the work done by an Agent.

We've designed Nightshift to fit into the "auto" workflow as much as possible which is what we describe (rather informally) as:

* Prompt Claude (or any other agent) to research across a bunch of structured or unstructured data
* process data like running aggregations, groups, cleaning operations, etc.
* create stateful catalogs, tables, and views
* integrate these data objects into dashboards or live applications

We say this because the main way you'll interface with Nightshift is through an Agent over our [MCP server](/).
When adopting this new platform, there are a few things you should know to get the most out of Nightshift and this is what this guide is for.

We'd recommend starting with [Apps](/apps), then working through the rest:

<CardGroup cols={2}>
  <Card title="Apps" href="/apps">
    Hosted data applications, built by your agent
  </Card>

  <Card title="Notebooks" href="/notebooks">
    Saved, re-runnable SQL analysis
  </Card>

  <Card title="Policies" href="/policies">
    How access works — for people, tokens, and agents
  </Card>

  <Card title="Audits" href="/audits">
    Every change recorded, every change reversible
  </Card>

  <Card title="Sharing" href="/sharing">
    Give teammates access to apps, notebooks, and data
  </Card>

  <Card title="General Best Practices" href="/best-practices">
    Habits that make agent-driven data work go well
  </Card>
</CardGroup>