diff --git a/src/content/docs/query-your-data/explore-query-data/notebooks/add-queries-to-notebooks.mdx b/src/content/docs/query-your-data/explore-query-data/notebooks/add-queries-to-notebooks.mdx
new file mode 100644
index 00000000000..346e11fcd61
--- /dev/null
+++ b/src/content/docs/query-your-data/explore-query-data/notebooks/add-queries-to-notebooks.mdx
@@ -0,0 +1,115 @@
+---
+title: Blocks in notebook
+tags:
+ - Query your data
+ - Explore and query data
+ - Notebooks
+ - NRQL
+metaDescription: 'Learn about notebook blocks, active blocks, action toolbars, and how to add and manage query blocks in your New Relic notebooks.'
+freshnessValidatedDate: never
+---
+
+Query blocks are the core component of notebooks, allowing you to write NRQL queries and visualize the results within your document. You can add multiple query blocks to a single notebook to build a comprehensive data story.
+
+## Active block
+
+The active block is the currently focused, interactive unit within your notebook. It serves as your immediate workspace for writing code, running queries, or adding documentation.
+
+The active block is immediately visible, making it easy to spot within your notebook. It is identified by two key visual cues:
+* **Clear Borders**: The active block is highlighted with a distinct, clear border color.
+* **Visible Toolbar**: It is the only cell that displays the actions.
+
+Queries coming from [Data Explorer](https://docs.newrelic.com/whats-new/2024/11/whats-new-11-11-data-explorer/) are added to the active block if the active block is of type query. If the active block is currently markdown, a new query block is added.
+
+To change an active block you need to select or add another block in the notebook.
+
+When a Markdown Block is active, it automatically enters editing mode featuring a two-column layout:
+* **Editing Column (Left)**: This is where you type and format your Markdown code.
+* **Live Preview Column (Right)**: This displays a real-time visual preview of your formatted documentation.
+
+## Action toolbar
+
+To help you optimize your workspace and maintain a clean view, the notebooks interface features an action toolbar. It consolidates core query actions into a compact, icon-based menu and groups secondary controls into a dedicated Actions Menu.
+
+### Core actions (Top of the Query block)
+
+These essential, frequently used actions are accessible at the top of the query block:
+* **Run query**: This is now represented by a play icon and executes the current query.
+* **Recent queries**: Allows you to quickly access and reuse your last 10 recently executed queries from your current session.
+* **Recommended queries**: Provides suggestions for queries.
+* **Copy query link**: Generates a shareable link to the current query.
+
+### Actions Menu (Secondary controls)
+
+The Actions Menu houses additional, less frequently used, or organizational controls.
+* **Add another query**: Inserts a new, empty query block into your notebook.
+* **Remove query**: Deletes the query from multi-query TIMESERIES.
+* **PromQL translator**: A utility for translating queries into PromQL (Prometheus Query Language).
+* **Clear**: Removes the query from the query input.
+* **Create alert**: Initiates the process for setting up a new alert based on the query results.
+* **Move up/down/to the top/to the bottom**: Reorganizes the current query block's position within the notebook.
+* **Delete block**: Deletes the active block.
+
+## Add a query block
+
+To add a query block to your notebook:
+
+1. Open your notebook in the query console.
+2. Click **+ Query**.
+3. Write your [NRQL query](https://docs.newrelic.com/docs/nrql/nrql-syntax-clauses-functions/) in the query editor.
+4. Press **Run** or **Enter** to execute the query and display results.
+
+
+ All NRQL queries supported in the standard query builder work in notebook query blocks. You can query any data type including metrics, events, logs, and traces. All [chart types](https://docs.newrelic.com/docs/query-your-data/explore-query-data/use-charts/chart-types/) and customizations available in the standard query builder are supported in notebooks.
+
+
+
+## Query block management
+
+
+
+
+1. Select the query block.
+2. Click the **three-dot menu** in the top-right corner.
+3. Select **Duplicate**.
+
+
+
+
+
+Reorder your query blocks to improve your narrative flow and organize your analysis logically. This helps you tell a better story by placing related queries together or arranging them in a sequence that makes sense for your investigation.
+
+1. Select the query block you want to move.
+2. Click the **three-dot menu**.
+3. Select from:
+ * **Move up**
+ * **Move down**
+ * **Move to top**
+ * **Move to bottom**
+
+
+
+
+
+1. Select the query block you want to delete.
+2. Click the **three-dot menu**.
+3. Select **Delete**.
+4. Confirm the deletion.
+
+
+
+
+## What's next?
+
+* Return to [Get started with notebooks](/docs/query-your-data/explore-query-data/notebooks/introduction-notebooks) for an overview
+* Explore [Dashboards](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards) for building persistent data visualizations
+* Learn more about [Chart types](/docs/query-your-data/explore-query-data/use-charts/chart-types) for visualization options
\ No newline at end of file
diff --git a/src/content/docs/query-your-data/explore-query-data/notebooks/introduction-notebooks.mdx b/src/content/docs/query-your-data/explore-query-data/notebooks/introduction-notebooks.mdx
new file mode 100644
index 00000000000..f12c84d672b
--- /dev/null
+++ b/src/content/docs/query-your-data/explore-query-data/notebooks/introduction-notebooks.mdx
@@ -0,0 +1,174 @@
+---
+title: Create data-driven documents with notebooks
+tags:
+ - Query your data
+ - Explore and query data
+ - Notebooks
+metaDescription: 'Use New Relic notebooks to create structured, data-driven documents that combine queries, visualizations, and descriptive text into shareable assets for investigations, post-mortems, and analytical insights.'
+freshnessValidatedDate: never
+---
+
+
+ We're still actively developing notebooks, but we're excited for you to try this powerful new feature! This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy/).
+
+
+When investigating complex issues or sharing insights with your team, you often find yourself jumping between different tools, copying queries, taking screenshots, and struggling to maintain context as you piece together a complete story from your data. Traditional dashboards are great for monitoring, but they fall short when you need to document investigations, create detailed post-mortems, or build step-by-step analytical workflows.
+
+Notebooks solve this problem by providing a dynamic and organized way to tell a complete story with your data. They are structured, data-driven documents that let you combine queries, visualizations, and descriptive text into a single, shareable asset, eliminating the need to switch between multiple tools or lose important context during your analysis.
+
+## Use cases
+
+Use notebooks to improve your workflow and turn raw data into actionable stories:
+
+* **Query, analyze, and visualize data**: Query all your observability data (logs, metrics, events) and create visualizations to gain a better understanding of your system's performance.
+* **Create post-mortems and incident documents**: Collaborate with your team to document investigations and create a clear, reusable record for incident post-mortems and root cause analysis.
+* **Build reusable workflows and runbooks**: Create and share step-by-step guides for complex analysis.
+* **Add context and narrative**: Use Markdown to easily add detailed titles, notes, and explanations to your queries and charts, transforming disconnected data points into a cohesive story.
+
+## Get started with notebooks
+
+Now that you understand the basics of notebooks, you're ready to start creating and managing your own notebooks.
+
+### Access notebooks
+
+To access notebooks:
+
+1. Go to **[one.newrelic.com](https://one.newrelic.com)**.
+2. Open the **Query your data** console from the drawer at the bottom of the page.
+3. Click **Notebooks** in the query builder header to see a list of all notebooks created by your organization.
+
+
+
+
+ Navigate to notebooks by going to **Query your data > Notebooks**
+
+
+
+
+
+You have two simple ways to start a new notebook:
+
+### Start from the notebooks index
+
+1. Click **+ Create a notebook** at the top-right corner of the index.
+2. Give your notebook a meaningful name (names are searchable, so use relevant keywords like your service or application name).
+3. Click **Create**.
+4. In the query console drawer, type your first query.
+
+### Start from the query console
+
+1. Open the query console (the drawer at the bottom of the platform).
+2. Create your desired queries and Markdown blocks.
+3. Click the **Save**.
+4. Name your notebook, and click **Save**.
+
+
+
+
+
+### Search and sort notebooks
+
+To find specific notebooks in your organization:
+
+1. **Search by name**: Use the search bar at the top of the notebooks index to find notebooks by name or keywords.
+2. **Sort notebooks**: Click the sort dropdown to organize notebooks by:
+ * Name (A-Z or Z-A)
+ * Last modified date (newest or oldest first)
+ * Created date (newest or oldest first)
+ * Favorites (starred notebooks appear first)
+3. **Filter by favorites**: Click the star filter to show only your favorite notebooks.
+
+### Duplicate a notebook
+
+1. Open the notebook you want to duplicate.
+2. Click the arrow next to the tab name in the console drawer and click **duplicate**.
+3. Click **Duplicate** from the context menu.
+4. A copy of the notebook will open in a new tab, ready for editing.
+
+### Mark a notebook as favorite
+
+To quickly find your most important notebooks, you can mark them as a favorite:
+
+1. Click the star icon next to a notebook's name in the index page.
+2. The icon will turn yellow, and the notebook will be grouped at the top of the index list.
+3. Click the star icon again to remove it from your favorites.
+
+
+
+
+
+
+ Deleting a notebook is permanent and cannot be undone. Once deleted, the notebook and all its content are permanently removed from the system. Make sure to duplicate any notebooks you want to preserve before deleting.
+
+
+1. On the notebook index list, click the three-dot action menu for the notebook you wish to delete.
+2. Click the **Delete** option.
+3. Confirm the deletion by clicking **Delete** again.
+
+
+
+
+## Notebook blocks
+
+Blocks are the fundamental building units of a notebook. They are individual sections you add to structure your analysis and narrative.
+
+### Query blocks
+
+Use query blocks to write [NRQL queries](/docs/nrql/nrql-syntax-clauses-functions/) and visualize the results. All single query [chart types](https://docs.newrelic.com/docs/query-your-data/explore-query-data/use-charts/chart-types/) and customizations available in the standard query builder are supported in notebooks.
+
+### Text blocks
+
+Use Markdown to add rich text, titles, context, explanations, and descriptive text to tell the story of your investigation.
+
+### Block actions
+
+Every [block](/docs/query-your-data/explore-query-data/notebooks/introduction-notebooks/) can be manipulated to organize your document:
+
+* **Duplicate**: Create a copy of the block
+* **Delete**: Remove the block from your notebook
+* **Move Up/Down**: Reorder blocks within your notebook
+* **Move to Top/Bottom**: Quickly move blocks to the beginning or end
+
+## Notebooks permissions
+
+Before you start creating notebooks, it's important to understand how permissions work and who will have access to your notebooks.
+
+### Organization association
+
+Every notebook is a resource that belongs to the organization in which it was created. This association is permanent and cannot be changed. Notebooks cannot be shared between different organizations. If the organization is deleted, the notebook is deleted as well. If a user moves to a different organization, they will not have access to notebooks from their previous organization.
+
+### Current permissions model
+
+
+ Notebooks currently do not have granular permission settings. Anyone in the organization who has access to the feature can create new notebooks, edit and delete existing ones.
+
+
+**Current capabilities:**
+* All organization members with notebooks access can view all notebooks
+* All organization members with notebooks access can create, edit, and delete any notebook
+* Notebooks are automatically shared across your entire organization
+
+
+## What's next?
+
+Now that you understand the basics of notebooks, you can:
+
+* Learn more about [blocks in notebook](/docs/query-your-data/explore-query-data/notebooks/add-queries-to-notebooks/)
+
+You can also explore related features:
+* [Dashboards](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards) for building persistent data visualizations
+* [Query builder](/docs/query-your-data/explore-query-data/query-builder/introduction-query-builder) for creating individual queries
+* [Charts](/docs/query-your-data/explore-query-data/use-charts/use-your-charts) for understanding visualization options
\ No newline at end of file
diff --git a/src/content/docs/query-your-data/explore-query-data/notebooks/notebooks-examples.mdx b/src/content/docs/query-your-data/explore-query-data/notebooks/notebooks-examples.mdx
new file mode 100644
index 00000000000..d8e23d591dc
--- /dev/null
+++ b/src/content/docs/query-your-data/explore-query-data/notebooks/notebooks-examples.mdx
@@ -0,0 +1,347 @@
+---
+title: Notebook examples and use cases
+tags:
+ - Query your data
+ - Explore and query data
+ - Notebooks
+ - Examples
+translate:
+ - jp
+ - kr
+metaDescription: 'Explore real-world examples of New Relic notebooks for incident investigations, performance analysis, and team collaboration to get inspired for your own data stories.'
+freshnessValidatedDate: never
+---
+
+Get inspired by these practical notebook examples that demonstrate how to create compelling data stories for common use cases. Each example shows how to combine queries, visualizations, and narrative text to build effective analysis documents.
+
+## Incident investigation notebook
+
+Create a comprehensive incident investigation document that helps your team understand what happened and how to prevent it in the future.
+
+### Structure
+
+**Markdown block: Incident overview**
+```markdown
+# Production API Outage - October 15, 2024
+
+**Incident Start**: 2024-10-15 14:32 UTC
+**Incident End**: 2024-10-15 15:18 UTC
+**Duration**: 46 minutes
+**Impact**: 15% of API requests failed
+
+## Summary
+Our main API experienced elevated error rates starting at 14:32 UTC...
+```
+
+**Query block: Error rate timeline**
+```sql
+SELECT count(*) as 'Total Requests',
+ filter(count(*), WHERE httpResponseCode >= 400) as 'Errors'
+FROM Transaction
+WHERE appName = 'api-production'
+TIMESERIES 1 minute
+SINCE '2024-10-15 14:00:00' UNTIL '2024-10-15 16:00:00'
+```
+
+**Query block: Error breakdown by endpoint**
+```sql
+SELECT count(*) as 'Error Count',
+ average(duration) as 'Avg Duration (ms)'
+FROM Transaction
+WHERE appName = 'api-production'
+ AND httpResponseCode >= 400
+FACET request.uri
+SINCE '2024-10-15 14:00:00' UNTIL '2024-10-15 16:00:00'
+ORDER BY count(*) DESC
+```
+
+**Markdown block: Root cause analysis**
+```markdown
+## Root Cause Analysis
+
+### Timeline of Events
+- **14:32**: Error rates began climbing for `/api/users` endpoint
+- **14:35**: Database connection pool exhaustion detected
+- **14:45**: Database scaling initiated
+- **15:18**: Service fully recovered
+
+### Contributing Factors
+1. Unusual traffic spike during product launch
+2. Database connection pool too small for peak load
+3. Missing rate limiting on user registration endpoint
+```
+
+**Query block: Database performance during incident**
+```sql
+SELECT average(duration) as 'Query Duration (ms)',
+ count(*) as 'Query Count'
+FROM DatabaseSample
+WHERE host = 'prod-db-01'
+TIMESERIES 5 minutes
+SINCE '2024-10-15 14:00:00' UNTIL '2024-10-15 16:00:00'
+```
+
+## Performance analysis notebook
+
+Track and analyze application performance trends over time to identify optimization opportunities.
+
+### Structure
+
+**Markdown block: Analysis overview**
+```markdown
+# Weekly Performance Review - Week of October 14, 2024
+
+## Objectives
+- Review application response times across all services
+- Identify performance regressions
+- Track progress on optimization initiatives
+
+## Key Metrics
+- P95 response time target: < 500ms
+- Error rate target: < 0.1%
+- Apdex score target: > 0.85
+```
+
+**Query block: Response time trends**
+```sql
+SELECT percentile(duration, 50) as 'P50',
+ percentile(duration, 95) as 'P95',
+ percentile(duration, 99) as 'P99'
+FROM Transaction
+WHERE appName IN ('web-frontend', 'api-backend', 'auth-service')
+FACET appName
+TIMESERIES 1 day
+SINCE 7 days ago
+```
+
+**Query block: Error rate comparison**
+```sql
+SELECT percentage(count(*), WHERE error IS true) as 'Error Rate %'
+FROM Transaction
+WHERE appName IN ('web-frontend', 'api-backend', 'auth-service')
+FACET appName
+TIMESERIES 1 day
+SINCE 7 days ago
+COMPARE WITH 1 week ago
+```
+
+**Markdown block: Analysis and recommendations**
+```markdown
+## Key Findings
+
+### Performance Improvements ✅
+- API backend P95 improved from 650ms to 420ms
+- Authentication service error rate down 50%
+
+### Areas for Attention ⚠️
+- Web frontend P95 increased 15% week-over-week
+- Database query timeouts up 25%
+
+### Action Items
+1. Investigate frontend asset loading delays
+2. Optimize top 5 slowest database queries
+3. Implement caching for user profile data
+```
+
+## Feature adoption tracking
+
+Monitor how users interact with new features and measure adoption success.
+
+### Structure
+
+**Markdown block: Feature overview**
+```markdown
+# New Dashboard Feature Adoption - 30 Days Post-Launch
+
+**Launch Date**: September 15, 2024
+**Analysis Period**: September 15 - October 15, 2024
+
+## Feature Description
+New interactive dashboard builder with drag-and-drop widgets...
+
+## Success Metrics
+- **Primary**: 25% of active users create at least one custom dashboard
+- **Secondary**: Average 3 widgets per custom dashboard
+- **Tertiary**: < 5% bounce rate on dashboard creation page
+```
+
+**Query block: Daily active users creating dashboards**
+```sql
+SELECT uniqueCount(userId) as 'Users Creating Dashboards'
+FROM PageView
+WHERE pageUrl LIKE '%/dashboard/create%'
+TIMESERIES 1 day
+SINCE 30 days ago
+```
+
+**Query block: Dashboard creation funnel**
+```sql
+SELECT funnel(userId,
+ WHERE pageUrl LIKE '%/dashboard/create%' as 'Started Creation',
+ WHERE pageUrl LIKE '%/dashboard/create%' AND eventType = 'widget_added' as 'Added Widget',
+ WHERE eventType = 'dashboard_saved' as 'Saved Dashboard'
+)
+FROM PageView, UserAction
+SINCE 30 days ago
+```
+
+## Security monitoring notebook
+
+Create ongoing security analysis to track potential threats and system vulnerabilities.
+
+### Structure
+
+**Markdown block: Security overview**
+```markdown
+# Weekly Security Review - October 21, 2024
+
+## Monitoring Scope
+- Failed authentication attempts
+- Unusual API access patterns
+- Database query anomalies
+- File system access violations
+
+## Alert Thresholds
+- Failed logins: > 100/hour from single IP
+- API rate limiting: > 1000 requests/minute
+- Suspicious queries: containing SQL injection patterns
+```
+
+**Query block: Failed authentication patterns**
+```sql
+SELECT count(*) as 'Failed Attempts',
+ latest(remoteAddr) as 'Source IP'
+FROM Log
+WHERE message LIKE '%authentication failed%'
+FACET remoteAddr
+SINCE 7 days ago
+HAVING count(*) > 50
+ORDER BY count(*) DESC
+```
+
+**Query block: API access anomalies**
+```sql
+SELECT count(*) as 'Request Count',
+ uniqueCount(userAgent) as 'Unique User Agents'
+FROM Transaction
+WHERE appName = 'api-gateway'
+FACET request.headers.x-forwarded-for
+SINCE 24 hours ago
+HAVING count(*) > 10000
+ORDER BY count(*) DESC
+```
+
+## Business metrics dashboard
+
+Track key business KPIs alongside technical metrics to understand the complete picture.
+
+### Structure
+
+**Markdown block: Business context**
+```markdown
+# Monthly Business & Technical Review - October 2024
+
+## Business Objectives
+- Increase user engagement by 15%
+- Reduce customer support tickets by 20%
+- Improve conversion rate to 3.5%
+
+## Technical Performance Targets
+- 99.9% uptime
+- < 2 second page load times
+- Zero security incidents
+```
+
+**Query block: User engagement metrics**
+```sql
+SELECT count(*) as 'Page Views',
+ uniqueCount(userId) as 'Active Users',
+ average(duration) as 'Avg Session Duration'
+FROM PageView
+TIMESERIES 1 day
+SINCE 30 days ago
+```
+
+**Query block: Conversion funnel**
+```sql
+SELECT funnel(userId,
+ WHERE pageUrl = '/signup' as 'Signup Page',
+ WHERE pageUrl = '/signup/verify' as 'Email Verified',
+ WHERE pageUrl = '/onboarding/complete' as 'Onboarding Complete',
+ WHERE eventType = 'subscription_created' as 'Converted'
+)
+FROM PageView, UserAction
+SINCE 30 days ago
+```
+
+## Template: Investigation starter
+
+Use this template as a starting point for any data investigation.
+
+### Structure
+
+**Markdown block: Investigation template**
+```markdown
+# Investigation: [ISSUE DESCRIPTION]
+
+**Date**: [TODAY'S DATE]
+**Investigator**: [YOUR NAME]
+**Priority**: [HIGH/MEDIUM/LOW]
+
+## Problem Statement
+[Describe what you're investigating and why]
+
+## Hypothesis
+[What do you think might be causing the issue?]
+
+## Investigation Plan
+1. [First thing to check]
+2. [Second thing to check]
+3. [Third thing to check]
+
+## Findings
+_[Update this section as you discover information]_
+
+## Next Steps
+_[What actions should be taken based on your findings?]_
+```
+
+**Query block: Initial data exploration**
+```sql
+-- Replace with your initial query
+SELECT count(*)
+FROM [YourEventType]
+WHERE [YourConditions]
+SINCE 1 hour ago
+```
+
+
+ Start each investigation with broad queries to understand the scope, then narrow down to specific areas based on your findings.
+
+
+## Best practices for notebook examples
+
+### Structure your story
+
+1. **Start with context**: Always begin with a Markdown block explaining the purpose
+2. **Follow logical flow**: Arrange queries in the order someone would naturally investigate
+3. **Provide conclusions**: End with Markdown blocks summarizing findings and next steps
+
+### Make queries reusable
+
+* Use variables for dates, application names, and thresholds
+* Comment your NRQL to explain complex logic
+* Choose appropriate time ranges for the analysis type
+
+### Visual design tips
+
+* Use consistent chart types throughout related queries
+* Choose colors that support your narrative
+* Add clear titles and labels to all visualizations
+* Use tables for detailed data, charts for trends and patterns
+
+## What's next?
+
+* Learn how to [add queries to notebooks](/docs/query-your-data/explore-query-data/notebooks/add-queries-to-notebooks)
+* Discover [sharing options](/docs/query-your-data/explore-query-data/notebooks/share-notebooks) for your notebooks
+* Explore [NRQL examples](/docs/nrql/nrql-examples) for more query inspiration
\ No newline at end of file
diff --git a/src/content/docs/query-your-data/explore-query-data/notebooks/share-notebooks.mdx b/src/content/docs/query-your-data/explore-query-data/notebooks/share-notebooks.mdx
new file mode 100644
index 00000000000..9ea99901d59
--- /dev/null
+++ b/src/content/docs/query-your-data/explore-query-data/notebooks/share-notebooks.mdx
@@ -0,0 +1,164 @@
+---
+title: Share notebooks with your team
+tags:
+ - Query your data
+ - Explore and query data
+ - Notebooks
+ - Collaboration
+translate:
+ - jp
+ - kr
+metaDescription: 'Learn how to share New Relic notebooks with your team members, collaborate on investigations, and distribute analytical insights across your organization.'
+freshnessValidatedDate: never
+---
+
+Notebooks are designed for collaboration. You can easily share your data-driven documents with team members to distribute insights, collaborate on investigations, or create reusable analysis templates.
+
+## Notebook sharing overview
+
+All notebooks created within your New Relic organization are automatically available to other organization members who have access to the notebooks feature. This enables seamless collaboration across your team.
+
+
+ Currently, notebooks do not have granular permission settings. Anyone in your organization with access to the notebooks feature can view, edit, and delete any notebook. We are working on introducing more detailed permissions in a future release.
+
+
+## Share a notebook URL
+
+The simplest way to share a specific notebook is by sharing its URL:
+
+1. Open the notebook you want to share.
+2. Copy the URL from your browser's address bar.
+3. Share the URL with your team members via email, chat, or your preferred communication tool.
+
+Team members who click the URL will be taken directly to the notebook (assuming they have access to your New Relic organization).
+
+## Find shared notebooks
+
+To discover notebooks created by your team members:
+
+1. Go to **[one.newrelic.com](https://one.newrelic.com)**.
+2. Open the **Query your data** console.
+3. Click on **Notebooks** to view the notebooks index.
+4. Browse all notebooks in your organization or use the search functionality to find specific notebooks.
+
+### Search for notebooks
+
+Use the search bar in the notebooks index to find specific notebooks by:
+
+* Notebook name
+* Keywords in the notebook title
+* Content within the notebook (if searchable)
+
+### Sort notebooks
+
+Sort the notebooks list by:
+
+* **Name**: Alphabetical order
+* **Last modified**: Most recently updated first
+* **Created date**: Newest or oldest first
+* **Favorites**: Your starred notebooks appear at the top
+
+## Collaboration best practices
+
+### Naming conventions
+
+Use clear, descriptive names for your notebooks to help team members understand their purpose:
+
+* **Good**: "API Performance Investigation - Oct 2024"
+* **Good**: "Weekly Error Rate Analysis Template"
+* **Good**: "Customer Churn Analysis - Q3 Results"
+* **Avoid**: "My Notebook" or "Test"
+
+### Organization strategies
+
+#### Create templates
+
+Build reusable notebook templates for common analysis tasks:
+
+1. Create a notebook with standard queries and structure
+2. Use variables for customizable elements
+3. Add Markdown instructions for team members
+4. Name it clearly as a template (e.g., "Template: Incident Investigation")
+
+#### Document your analysis
+
+Use Markdown blocks to provide context:
+
+* Explain the purpose of each query
+* Document your analysis methodology
+* Include links to related resources
+* Add conclusions and next steps
+
+#### Use descriptive visualizations
+
+* Add clear titles to your charts
+* Use consistent color schemes
+* Include axis labels and units
+* Add thresholds or baseline indicators where relevant
+
+## Collaborative workflows
+
+### Incident response
+
+Create collaborative incident investigation notebooks:
+
+1. Start with a standard incident template
+2. Add team members as the investigation progresses
+3. Document findings in real-time using Markdown blocks
+4. Include relevant queries and visualizations
+5. Summarize root cause and remediation steps
+
+### Weekly/monthly reporting
+
+Build recurring analysis notebooks:
+
+1. Create a notebook template with standard metrics
+2. Use variables for time ranges and filters
+3. Schedule regular reviews with your team
+4. Archive completed reports with date-specific names
+
+### Knowledge sharing
+
+Transform one-time investigations into reusable knowledge:
+
+1. Create detailed analysis notebooks
+2. Include methodology and reasoning in Markdown
+3. Add comments explaining unusual findings
+4. Share with broader team for future reference
+
+## Version control and history
+
+
+ Currently, notebooks do not have built-in version history. Consider duplicating important notebooks before making significant changes to preserve previous versions.
+
+
+To maintain version control:
+
+1. **Duplicate before major changes**: Create a copy of your notebook before making significant modifications
+2. **Use descriptive names**: Include version numbers or dates in notebook names
+3. **Document changes**: Use Markdown blocks to note what was changed and when
+4. **Archive old versions**: Move outdated versions to a separate folder or naming convention
+
+## Troubleshooting sharing issues
+
+### Notebook not visible to team members
+
+If team members can't see your notebook:
+
+1. **Check organization access**: Ensure they belong to the same New Relic organization
+2. **Verify feature access**: Confirm they have access to the notebooks preview feature
+3. **Try direct URL**: Share the specific notebook URL rather than expecting them to find it in the index
+
+### Performance with shared notebooks
+
+Large or complex notebooks may load slowly for all users:
+
+1. **Optimize queries**: Use appropriate time ranges and filters
+2. **Limit result sets**: Use `LIMIT` clauses in NRQL queries
+3. **Consider splitting**: Break very large notebooks into smaller, focused documents
+
+## What's next?
+
+* Learn about [visualizations in notebooks](/docs/query-your-data/explore-query-data/notebooks/visualizations-in-notebooks)
+* Explore [notebook examples](/docs/query-your-data/explore-query-data/notebooks/notebooks-examples) for collaboration inspiration
+* Check out [adding queries to notebooks](/docs/query-your-data/explore-query-data/notebooks/add-queries-to-notebooks) for advanced techniques
\ No newline at end of file
diff --git a/src/content/docs/query-your-data/explore-query-data/notebooks/visualizations-in-notebooks.mdx b/src/content/docs/query-your-data/explore-query-data/notebooks/visualizations-in-notebooks.mdx
new file mode 100644
index 00000000000..80059ddfc2c
--- /dev/null
+++ b/src/content/docs/query-your-data/explore-query-data/notebooks/visualizations-in-notebooks.mdx
@@ -0,0 +1,286 @@
+---
+title: Use visualizations in notebooks
+tags:
+ - Query your data
+ - Explore and query data
+ - Notebooks
+ - Charts
+ - Visualizations
+translate:
+ - jp
+ - kr
+metaDescription: 'Learn how to create and customize visualizations in New Relic notebooks, including chart types, formatting options, and best practices for data storytelling.'
+freshnessValidatedDate: never
+---
+
+Visualizations are a key component of effective notebooks, helping transform raw query results into clear, compelling charts that support your data narrative. Notebooks support all the same visualization options available in the New Relic query builder.
+
+## Available chart types
+
+Choose the right visualization for your data and story:
+
+### Line charts
+
+Perfect for showing trends over time and comparing multiple metrics.
+
+**Best for**: Time series data, performance trends, comparing metrics over time
+
+**Example query**:
+```sql
+SELECT average(duration) as 'Response Time'
+FROM Transaction
+WHERE appName = 'MyApp'
+TIMESERIES 5 minutes
+SINCE 6 hours ago
+```
+
+### Area charts
+
+Show volume and composition changes over time with filled areas under the line.
+
+**Best for**: Cumulative data, showing total volume with breakdowns, resource usage over time
+
+**Example query**:
+```sql
+SELECT count(*) FROM Transaction
+WHERE appName = 'MyApp'
+FACET host
+TIMESERIES 10 minutes
+SINCE 2 hours ago
+```
+
+### Bar charts
+
+Compare values across different categories or dimensions.
+
+**Best for**: Comparing values across categories, top N lists, error breakdowns
+
+**Example query**:
+```sql
+SELECT count(*) as 'Request Count'
+FROM Transaction
+WHERE appName = 'MyApp'
+FACET name
+SINCE 1 hour ago
+ORDER BY count(*) DESC
+LIMIT 10
+```
+
+### Pie charts
+
+Display proportional data and percentage breakdowns.
+
+**Best for**: Showing parts of a whole, percentage distributions, simple category breakdowns
+
+**Example query**:
+```sql
+SELECT count(*) FROM Transaction
+WHERE appName = 'MyApp'
+FACET httpResponseCode
+SINCE 1 hour ago
+```
+
+### Tables
+
+Present detailed data in rows and columns for precise values.
+
+**Best for**: Detailed data, exact values, lists with multiple attributes, debugging
+
+**Example query**:
+```sql
+SELECT timestamp, name, duration, httpResponseCode
+FROM Transaction
+WHERE appName = 'MyApp' AND duration > 5
+SINCE 1 hour ago
+ORDER BY duration DESC
+LIMIT 20
+```
+
+### Billboards
+
+Highlight single important metrics prominently.
+
+**Best for**: Key performance indicators, summary statistics, single important values
+
+**Example query**:
+```sql
+SELECT average(duration) as 'Avg Response Time (ms)'
+FROM Transaction
+WHERE appName = 'MyApp'
+SINCE 1 hour ago
+```
+
+## Customize your visualizations
+
+### Chart settings
+
+Access chart customization options by clicking the **Chart settings** icon in your query block:
+
+1. **Colors**: Choose custom colors for your data series
+2. **Axes**: Customize axis labels, ranges, and formatting
+3. **Legend**: Show/hide legend, adjust positioning
+4. **Thresholds**: Add horizontal lines for targets or alerts
+5. **Units**: Format numbers, percentages, time values
+
+### Color schemes
+
+Choose colors that support your narrative:
+
+* **Default palette**: Standard New Relic colors for consistency
+* **Custom colors**: Match your organization's branding
+* **Accessible colors**: High contrast for better readability
+* **Status colors**: Green for healthy, red for errors, yellow for warnings
+
+### Formatting options
+
+Format your data for clarity:
+
+* **Numbers**: Add thousands separators, decimal places
+* **Percentages**: Show as percentages rather than decimals
+* **Time values**: Display in hours, minutes, or seconds
+* **Bytes**: Show in KB, MB, GB as appropriate
+
+## Visualization best practices
+
+### Choose the right chart type
+
+
+ The chart type should support your story, not distract from it. When in doubt, simpler is usually better.
+
+
+* **Time series data**: Use line or area charts
+* **Comparisons**: Use bar charts
+* **Proportions**: Use pie charts (but limit to 5-7 categories)
+* **Exact values**: Use tables
+* **Key metrics**: Use billboards
+
+### Design for clarity
+
+#### Chart titles and labels
+
+Always add descriptive titles and labels:
+
+```sql
+SELECT average(duration) as 'Average Response Time (ms)',
+ percentile(duration, 95) as '95th Percentile (ms)'
+FROM Transaction
+WHERE appName = 'E-commerce API'
+SINCE 24 hours ago
+TIMESERIES 1 hour
+```
+
+#### Use consistent formatting
+
+* Keep similar charts using the same time ranges
+* Use consistent color schemes across related charts
+* Apply the same formatting rules throughout your notebook
+
+#### Highlight important information
+
+* Use thresholds to show targets or SLA boundaries
+* Choose colors that draw attention to problems (red for errors)
+* Size billboards appropriately for their importance
+
+### Context and storytelling
+
+#### Add explanatory text
+
+Use Markdown blocks to provide context for your visualizations:
+
+```markdown
+## Response Time Analysis
+
+The chart below shows a significant spike in response times at 2:30 PM,
+corresponding with the deployment of version 2.1.4. The 95th percentile
+reached 2.8 seconds, well above our 500ms SLA target.
+
+### What this means:
+- 5% of users experienced unacceptable delays
+- The issue was resolved by rolling back the deployment
+- We need better performance testing before releases
+```
+
+#### Tell a story with multiple charts
+
+Arrange your visualizations to build a narrative:
+
+1. **Overview chart**: Start with high-level metrics
+2. **Drill-down charts**: Show specific aspects or segments
+3. **Root cause charts**: Display underlying causes
+4. **Resolution charts**: Show improvement or fixes
+
+## Advanced visualization techniques
+
+### Using variables for dynamic charts
+
+Create reusable visualizations with variables:
+
+```markdown
+{{appName = "production-api"}}
+{{timeRange = "6 hours ago"}}
+```
+
+```sql
+SELECT count(*) as 'Requests',
+ average(duration) as 'Avg Duration'
+FROM Transaction
+WHERE appName = '{{appName}}'
+TIMESERIES 5 minutes
+SINCE {{timeRange}}
+```
+
+### Comparative analysis
+
+Show before and after or period comparisons:
+
+```sql
+SELECT average(duration) as 'Response Time'
+FROM Transaction
+WHERE appName = 'MyApp'
+TIMESERIES 1 hour
+SINCE 7 days ago
+COMPARE WITH 1 week ago
+```
+
+### Multi-faceted analysis
+
+Break down metrics by multiple dimensions:
+
+```sql
+SELECT count(*) FROM Transaction
+WHERE appName = 'MyApp'
+FACET host, httpResponseCode
+SINCE 2 hours ago
+```
+
+## Troubleshooting visualizations
+
+### Common issues
+
+**Chart shows no data**:
+* Check your time range includes data
+* Verify your WHERE clauses are correct
+* Ensure you have permission to access the data
+
+**Chart is too cluttered**:
+* Use LIMIT to reduce the number of series
+* Consider breaking into multiple charts
+* Use aggregation to combine less important categories
+
+**Data looks wrong**:
+* Check for timezone issues in time series
+* Verify your math in calculated fields
+* Look for filtering that might exclude expected data
+
+### Performance optimization
+
+* Use appropriate time ranges for your analysis
+* Add specific WHERE clauses to limit data volume
+* Use sampling for very large datasets
+* Consider using approximation functions for better performance
+
+## What's next?
+
+* Learn about [sharing notebooks](/docs/query-your-data/explore-query-data/notebooks/share-notebooks) with your team
+* Explore [notebook examples](/docs/query-your-data/explore-query-data/notebooks/notebooks-examples) for visualization inspiration
+* Check out the [chart types guide](/docs/query-your-data/explore-query-data/use-charts/chart-types) for detailed information about all available visualizations
\ No newline at end of file
diff --git a/src/nav/dashboards.yml b/src/nav/dashboards.yml
index 54f44f3051a..4e869483923 100644
--- a/src/nav/dashboards.yml
+++ b/src/nav/dashboards.yml
@@ -51,6 +51,12 @@ pages:
path: /docs/query-your-data/explore-query-data/dashboards/add-custom-visualizations-your-dashboards
- title: Troubleshooting chart errors
path: /docs/query-your-data/explore-query-data/dashboards/troubleshooting-chart-errors
+ - title: Notebooks
+ pages:
+ - title: Get started with notebooks
+ path: /docs/query-your-data/explore-query-data/notebooks/introduction-notebooks
+ - title: Blocks in notebook
+ path: /docs/query-your-data/explore-query-data/notebooks/add-queries-to-notebooks
- title: Grafana integrations
pages:
- title: Grafana support with Prometheus and PromQL
diff --git a/static/images/notebooks-navigation.webp b/static/images/notebooks-navigation.webp
new file mode 100644
index 00000000000..03487e1eb5f
Binary files /dev/null and b/static/images/notebooks-navigation.webp differ