```
For more control over image sizing:
```html theme={null}
```
**Supported responsive CSS properties:**
* `max-width`, `min-width` - Control width bounds
* `max-height`, `min-height` - Control height bounds
* `height:auto` - Maintain aspect ratio
* `object-fit` - Control how images fit (e.g., `contain`, `cover`)
You can add background colors to markdown tiles to emphasize sections or titles.
⚡
Welcome to your Lightdash Dashboard
Hello World!.
Or highlight something important.
Add links like this!
Use subscript or superscript
Easily colour your text.
Or change the size.
Center your text.
Or align it to the right.
You can even justify a line of text if you are trying to communicate a point that is particularly long, perhaps something like this example sentence?
Change the word spacing. 👏
Or combine a whole bunch of styles together.
It supports headings
Here's an H2 heading in red
You can include images and apply options and styles. Here's one I centered earlier:tags to tag these models. You can use sets of existing tags, or you can create a new Lightdash-specific tag. Something like this:
```bash theme={null}
{{
config(
materialized='table',
tags=['lightdash']
)
}}
```
The `lightdash dbt run` command supports dbt model selection syntax to generate .yml files for a group of models. This means you can use tags or other model selection syntax to specify which models you want to generate dimensions for in your dbt project.
```bash theme={null}
lightdash dbt run -s tag:lightdash # all models with the lightdash tag
lightdash dbt run -s payments # just payments
lightdash dbt run -s payments+ # payments and all children
lightdash dbt run -s +payments # payments and all parents
lightdash dbt run -s payments+ +customers tag:lightdash # mix and match
```
## Key features * **Natural language queries** - Ask questions in plain English and get instant answers * **Ask from a chart or dashboard** - Launch a conversation with the chart or dashboard you're viewing already pinned as context * **AI Router** - Automatically send each question to the best-fit agent, so users don't have to pick one first * **Automatic visualizations** - Get charts, tables, and dashboards generated based on your questions * **Slack integration** - Collaborate with your team directly in Slack channels * **Memory and learning** - Agents remember corrections and improve over time * **[Reviews (Beta)](/guides/ai-agents/reviews)** - Lightdash scans agent turns for likely-wrong answers and proposes one-click fixes to your semantic layer or [project context](/guides/ai-agents/reviews#the-lightdashproject_contextyml-file), so admins can improve agents at the source * **Knowledge documents** - Upload glossaries, metric definitions, and business context for your agent to consult * **Access control** - Fine-grained control over data access and permissions * **Multiple agents** - Create specialized agents for different teams or use cases * **Evaluations** - Create test suites to validate your agent’s answers and prevent regressions. * **Conversations** - Monitor all agent interactions in one place, review feedback, and build evaluation sets directly from real threads. * **AI writeback (Beta)** - Ask an agent to edit your dbt project in chat and open a pull request with the changes * **Creating & editing content (Beta)** - Agents can build and edit charts and dashboards on request # Agent memory Source: https://docs.lightdash.com/guides/ai-agents/agent-memory How AI agents learn from your corrections and feedback
Once you're set up - whether in the UI or in Slack - you can start asking questions immediately! Try asking "What kind of data can you access?" to get started:
🛒 Average basket this month: ${dbt_orders_average_of_basket_total}
💳 Total Orders this month: ${dbt_orders_count_distinct_order_id}
Additional resources:
Check out the Sales Dashboard and the Notion doc about Orders and Revenue KPIs. ``` The above code will look like this in the tooltip:`TIMESTAMP_LTZ, TIMESTAMP_TZ` | `TIMESTAMP_NTZ, TIMESTAMP WITHOUT TIME ZONE,`
`DATETIME` | | Timezone | Timezone baked into each timestamp | Timezone assumed from default data timezone (default UTC) | ### Use `DATE` only for calendar values If a column represents a calendar date rather than a moment in time, store it as `DATE`. Lightdash treats `DATE` columns as fixed calendar dates and never shifts them: `2024-03-15` stays `2024-03-15` regardless of the project timezone. Use `DATE` for values like: * A user's date of birth * A subscription start date * An anniversary * A fiscal-period boundary `DATE` is **not** what you want for event timestamps. ## Configure your connection For timestamps without timezones (naive timestamps), we assume they follow the default data timezone. You can configure this in your warehouse connection settings:
Monthly Revenue
Active Users
Loading...
;
return (
);
}
```
### Static sites
For static sites, generate URLs at build time or use edge functions:
**Next.js (server component)**
```tsx theme={null}
import jwt from 'jsonwebtoken';
async function DashboardPage() {
// Generate at request time
const token = jwt.sign({
content: {
type: 'dashboard',
dashboardUuid: 'dashboard-uuid',
},
}, process.env.LIGHTDASH_EMBED_SECRET, { expiresIn: '24h' });
const embedUrl = `https://app.lightdash.cloud/embed/project-uuid#${token}`;
return (
);
}
```
### Content management systems
Embed in WordPress, Webflow, or other CMS:
1. Create a server endpoint that generates embed URLs
2. Use iframe embed code with dynamic URL
3. Refresh tokens via JavaScript when expired
**WordPress shortcode example:**
```php theme={null}
function lightdash_embed_shortcode($atts) {
$atts = shortcode_atts(array(
'dashboard' => '',
), $atts);
$embed_url = generate_lightdash_url($atts['dashboard']);
return '';
}
add_shortcode('lightdash', 'lightdash_embed_shortcode');
```
## Token refresh
JWTs expire after the time specified in `expiresIn`. Handle token expiration:
### Option 1: Long-lived tokens
For public or semi-public dashboards, use longer expiration:
```javascript theme={null}
jwt.sign(payload, secret, { expiresIn: '7d' }) // 7 days
```
Loading content...
; if (error) returnUnable to load content
; return (
{data?.data.map((item) => (
))}
);
}
```
#### Options
```typescript theme={null}
type ListContentOptions = {
projectUuids?: string[];
spaceUuids?: string[];
parentSpaceUuid?: string;
contentTypes?: Array<'space' | 'dashboard' | 'chart' | 'data_app'>;
page?: number;
pageSize?: number;
search?: string;
sortBy?: 'name' | 'space_name' | 'last_updated_at';
sortDirection?: 'asc' | 'desc';
};
```
Loading...
;
return (
Loading analytics...
;
if (!token) return Failed to load dashboard
;
return (
For queries in:
- dashboards use `dashboardView`
- explore use `exploreView`
- chart use `chartView`
- sql chart use `sqlChartView` | Query tags are stored differently in each data warehouse: | Data Warehouse | Query Tag | | :------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | BigQuery | Writes metadata as labels in your [job history](https://cloud.google.com/bigquery/docs/managing-jobs#view%5Fjob%5Fdetails%5F2). | | Snowflake | Writes JSON metadata in the comment column of your [query history](https://docs.snowflake.com/en/user-guide/ui-history#viewing-query-details-and-results). | | ClickHouse | Writes JSON metadata in the comment column of your [query log](https://clickhouse.com/docs/operations/system-tables/query_log). | | Trino | Sends metadata as comma-separated `key=value` pairs in the [`X-Trino-Client-Tags`](https://trino.io/docs/current/develop/client-protocol.html#client-request-headers) HTTP header on each submitted query. | | Redshift | Appends JSON metadata as a SQL comment in each submitted SQL query. | | Databricks | Appends JSON metadata as a SQL comment in each submitted SQL query. | | Postgres | Appends JSON metadata as a SQL comment in each submitted SQL query. | | Athena | Appends JSON metadata as a SQL comment in each submitted SQL query. | # User attributes Source: https://docs.lightdash.com/references/workspace/user-attributes User attributes provide a way to customise Lightdash charts, dashboards, and other behaviour depending on the user that is logged in. For example, you could only show your sales team members data that are relevant to their region. User attributes are defined for your whole Organization and can only be a text value (not a date or number). Some examples of user attributes are: * Sales region * Department * Can view PII * Can view financial data To start user attributes you need to follow 2 steps: 1. Define the user attribute, users can only have user attributes that are explicitly created by admins 2. Set the user attribute value per user. User attributes can only be managed by admins. ## Managing user attributes ### Creating user attributes User attributes can be created by navigating to **Organization Settings** > **User Attributes** and clicking on the**Add attribute** button. This will create a new user attribute but it will not be assigned to any user. ### Assigning user attributes to users and groups User attributes can be assigned to users or [groups](/references/workspace/groups) by navigating to **Organization Settings** > **User Attributes** and clicking on the user attribute you'd like to assign. Select a user by email address, or a group by group name and set their value. Each user, group, and default supports **multiple values**. When you reference the attribute in SQL or `required_attributes` / `any_attributes`, Lightdash treats all assigned values as a set — see [How user and group attribute values interact](#how-user-and-group-attribute-values-interact).
concurrency: 100] Worker -->|return result| API ``` The Lightdash API publishes jobs to NATS JetStream. Worker pods consume messages from their stream and process them concurrently (default 100 concurrent jobs per pod). ## Enabling NATS ```yaml theme={null} nats: enabled: true config: cluster: enabled: false jetstream: enabled: true fileStore: enabled: false memoryStore: enabled: true maxSize: 1Gi ``` The JetStream configuration shown above reflects the defaults when `nats.enabled` is set to `true`. This deploys a NATS StatefulSet and sets `NATS_ENABLED=true` on the backend, which means the backend will start routing queries through NATS. You should always enable at least a [warehouse worker](/self-host/nats-workers/warehouse-workers) alongside NATS to process those queries — otherwise queries will be enqueued with no worker to pick them up.