Have you ever built a Tableau dashboard and wished that clicking one chart could automatically update another? Or that selecting a bar in your sales chart could instantly filter your map to show only those regions? Or that clicking a customer name could open their profile page in your CRM without leaving Tableau?
In most cases, beginners handle this by building separate dashboards for each view, asking users to manually adjust filters, or adding so many filters to a single sheet that the dashboard becomes overwhelming and cluttered.
This is rigid, unintuitive, and makes your dashboards feel like static reports rather than interactive analytical tools.
Tableau Dashboard Actions solve this entirely. Actions are triggers that connect your visualisations together so that interacting with one view drives changes in another. Click a region on a map and your bar chart filters to that region. Hover over a product and related charts highlight matching data. Select a customer segment and every view on the dashboard responds simultaneously.
In this guide we will break down Tableau Dashboard Actions completely — what they are, how to configure each type step by step, real world examples for each action type, and when to use each one versus the alternatives.
What Are Dashboard Actions in Tableau?
Dashboard actions are interactive behaviours that you configure in Tableau to create connections between views, between dashboards, and between Tableau and external content. When a user interacts with a visualisation by clicking, hovering, or selecting, an action fires and produces a defined response elsewhere on the dashboard or in an external destination.
They answer the question: “When a user interacts with this view, what should happen next?”
Simple Analogy
Think of a Tableau dashboard action like a light switch connected to specific bulbs in a room. When you flip one switch (interact with a view), only the bulbs wired to that switch respond (the connected views update). Other bulbs stay as they are. You can wire multiple switches to the same bulb, or one switch to multiple bulbs — the wiring is the action.
Dashboard actions do exactly this for your visualizations. It connects user interactions to specific responses across your dashboard, regardless of how many views or sheets are involved.
The Six Types of Dashboard Actions
Tableau provides six action types, each producing a different kind of response:
| Action Type | What It Does |
|---|---|
| Filter Action | Filters other views based on a selection |
| Highlight Action | Emphasises matching marks across views without filtering |
| URL Action | Opens a web page or external link based on a selection |
| Go to Sheet Action | Navigates to another dashboard or worksheet |
| Change Parameter Action | Updates a parameter value based on a selection |
| Change Set Values Action | Adds or removes selected marks from a set |
Where to Find Dashboard Actions in Tableau
Dashboard actions live in the Dashboard menu at the top of the screen:
Dashboard menu → Actions → Add Action
You can also access actions from within a worksheet through:
Worksheet menu → Actions
Actions configured from the Dashboard menu apply at the dashboard level and can reference multiple source and target sheets. Actions configured from the Worksheet menu apply only to that individual sheet.
Step by Step: Your First Dashboard Action
Example 1: Filter Action Between a Bar Chart and a Map
Setup: A sales dashboard with two views side by side. Sheet 1 is a bar chart showing total sales by product category. Sheet 2 is a map showing sales by state. You want clicking a category bar to filter the map to show only sales from that category.
Step 1: Open the Actions dialog
With your dashboard open, go to Dashboard menu → Actions. The Actions dialog opens showing any existing actions. Click Add Action → Filter.
Step 2: Name your action
Give the action a descriptive name like “Category to Map Filter” so you can identify it easily when you have multiple actions configured.
Step 3: Set the Source Sheet
Under Source, select the sheet containing the bar chart (your category view). This is the sheet the user will interact with to trigger the action.
Step 4: Choose the Run Action On trigger
Tableau offers three trigger options:
Hover fires the action when the user moves their cursor over a mark without clicking. Select fires when the user clicks a mark. Menu fires when the user right clicks a mark and chooses the action from a context menu.
For this example choose Select so the filter applies when the user clicks a bar.
Step 5: Set the Target Sheet
Under Target, select the map sheet. This is the view that will respond to the interaction.
Step 6: Configure the Target Filters
Choose Selected Fields and map the Category field from the source sheet to the Category field in the target sheet. This tells Tableau exactly which field to use as the filter bridge between the two views.
Step 7: Set the Clearing Behaviour
This controls what happens when the user deselects or clicks on empty space:
Show all values restores the target view to its unfiltered state when the selection is cleared. Keep filtered values maintains the last filter even after deselection. Exclude all values shows an empty target view when nothing is selected.
For most dashboards choose Show all values so the map returns to its full view when the user clicks away.
Step 8: Click OK and test
Click a bar in your category chart. The map should immediately filter to show only states where that category has sales. Click on empty space and the map returns to showing all states.
How Dashboard Actions Work Internally
When you configure a dashboard action, Tableau stores the action definition as part of the workbook. When a user interacts with the source view at runtime, Tableau evaluates which marks were selected, extracts the field values from those marks, and applies those values as a filter, highlight, parameter update, or navigation instruction to the target.
The key concept to understand is the difference between the source and the target:
The source is where the interaction happens. The target is where the response appears. A single action can have one source sheet and multiple target sheets. Multiple actions can share the same source sheet and fire independently based on different user interactions.
Actions are evaluated in the order they are listed in the Actions dialog. If two actions conflict on the same target sheet, the one listed first takes precedence.
Real World Examples
Example 2: Highlight Action for Cross View Comparison
Goal: When a user hovers over a salesperson in a leaderboard table, highlight that salesperson’s bars across all other charts on the dashboard without filtering out other data.
Setup: A sales performance dashboard with a ranked table of salespeople, a bar chart of monthly performance, and a scatter plot of deal size versus close rate.
Configuration:
Dashboard → Actions → Add Action → Highlight
Set the source to the leaderboard table. Set Run Action On to Hover. Set the target sheets to the monthly bar chart and the scatter plot. Under Target Highlighting choose Selected Fields and select the Salesperson field.
Result: When the user hovers over a name in the leaderboard, that salesperson’s bars in the monthly chart turn full colour while all other bars fade. Their dot in the scatter plot stays highlighted while all other dots dim. Moving the cursor away restores full colour everywhere.
Highlight actions are ideal for comparison scenarios where you want to draw attention to a specific element without removing context. The user can see how one salesperson compares against the field, not just their isolated numbers.
Example 3: URL Action to Open a CRM Record
Goal: Clicking a customer name in a Tableau table opens that customer’s profile page in Salesforce in a new browser tab.
Setup: A customer overview dashboard with a table showing customer names, revenue, and last contact date.
Configuration:
Dashboard → Actions → Add Action → URL
Set the source to the customer table sheet. Set Run Action On to Select. In the URL field enter your CRM base URL and insert the customer ID field as a dynamic value using Tableau’s field insertion syntax:
https://yourcompany.salesforce.com/customer/<Customer ID>
Select the Customer ID field from the dropdown that appears when you click inside the URL field. Tableau wraps it in angle brackets automatically. Check Open in New Tab so the CRM opens without closing Tableau.
Result: A sales manager clicks a customer name and that customer’s full Salesforce record opens in a new browser tab instantly. The analyst never has to copy and paste an ID or switch to the CRM manually to find the record.
URL actions support any field value as a dynamic URL component. Common uses include linking to product pages, support tickets, Google Maps locations using latitude and longitude fields, internal documentation pages, or any system with URL based record access.
Example 4: Go to Sheet Action for Dashboard Navigation
Goal: Clicking a region on a summary map navigates to a detailed regional dashboard showing granular metrics for that region only.
Setup: A national overview dashboard with a filled map of regions. A separate detailed dashboard exists for regional analysis with deeper charts and tables.
Configuration:
Dashboard → Actions → Add Action → Go to Sheet
Set the source to the map sheet on the overview dashboard. Set Run Action On to Select. Under Target Sheet select the regional detail dashboard.
Step for passing context: To make the regional detail dashboard open pre filtered to the selected region, combine this with a filter action targeting the same destination. Configure both actions to fire on the same Select trigger. The filter action passes the region value and the Go to Sheet action handles the navigation. Both fire simultaneously when the user clicks.
Result: A user clicks the Southwest region on the map. Tableau navigates to the regional detail dashboard which opens already filtered to the Southwest. The user sees granular city level data, trend charts, and a product breakdown, all scoped to the region they selected from the overview.
Go to Sheet actions are the foundation of drill down dashboard design — broad overview at the top level, progressively more granular detail at lower levels, all connected by clicks.
Example 5: Change Parameter Action for Dynamic Metric Switching
Goal: Clicking a metric name in a legend panel updates a parameter that controls which metric is displayed across all charts on the dashboard simultaneously.
Setup: A KPI dashboard where a parameter called Selected Metric controls whether all charts show Revenue, Units Sold, or Profit Margin. A separate sheet contains a simple list of the three metric names acting as a clickable selector panel.
Configuration:
Dashboard → Actions → Add Action → Change Parameter
Set the source to the metric selector list sheet. Set Run Action On to Select. Under Parameter select the Selected Metric parameter. Under Value select the field in the selector sheet that contains the metric names.
Result: The user clicks Revenue in the selector panel. The Selected Metric parameter updates to Revenue and every chart on the dashboard that references that parameter recalculates immediately, showing revenue figures across all views. Clicking Profit Margin switches everything to margin data in a single click.
Change Parameter actions replace the need for parameter control widgets that sit awkwardly on dashboards. The selector panel itself becomes the control, styled to match the dashboard design, positioned wherever it makes the most visual sense.
Example 6: Change Set Values Action for Dynamic Comparison Groups
Goal: A user builds their own custom comparison group by clicking individual salesperson names, and all charts update to compare the selected group against everyone else.
Setup: A sales dashboard where a set called Selected Salespeople drives an IN/OUT calculation used across multiple charts. A list of salesperson names serves as the selection panel.
Configuration:
Dashboard → Actions → Add Action → Change Set Values
Set the source to the salesperson list sheet. Set Run Action On to Select. Under Target Set select the Selected Salespeople set. Choose Assign values to set so each click replaces the set contents, or Add values to set so clicks accumulate selections.
Under Clearing Behaviour choose Remove all values from set so deselecting clears the set and returns charts to their default unfiltered state.
Result: The user clicks Alice, then Bob, then Carol while holding Ctrl. All three names are added to the set. Charts immediately update to show Alice, Bob, and Carol highlighted or segmented against all other salespeople. Clicking an empty area clears the set and charts return to showing everyone equally.
Set actions are the most powerful action type for exploratory analysis because the user is dynamically defining comparison groups at runtime without any filter dropdowns or predefined segments.
Combining Multiple Actions on One Dashboard
The real power of dashboard actions emerges when you layer multiple action types together to create sophisticated interactive experiences.
Example: An executive sales dashboard with layered actions
Action 1 is a Highlight action triggered by hovering over the regional map. It highlights matching bars in the product category chart and matching rows in the customer table simultaneously.
Action 2 is a Filter action triggered by clicking a region on the map. It filters the product category chart and the customer table to show only data from that region.
Action 3 is a Change Parameter action triggered by clicking a metric button in a selector panel. It switches all charts between Revenue, Units, and Margin.
Action 4 is a URL action triggered by clicking a customer name in the table. It opens that customer’s CRM record in a new tab.
All four actions coexist and fire independently based on where the user interacts. The user can hover to explore without committing, click to filter, switch metrics mid analysis, and jump directly to the CRM, all without leaving the dashboard or adjusting a single filter control manually.
Dashboard Actions vs Tableau Filters and Parameters
All three of these tools shape what data appears on a dashboard but they serve different roles and work in different ways.
Tableau Filters (filter shelf and filter cards):
Filter cards are static controls e.g. dropdowns, sliders, and checkbox lists that the user adjusts manually. They apply to specific sheets and require the user to find and operate the correct control for each sheet they want to update. They are visible components that take up dashboard space. They are best for giving users direct manual control over specific dimensions.
Parameters:
Parameters are single value containers that drive calculated fields and reference lines across multiple sheets simultaneously. They require a separate control widget (slider, dropdown, or type in box) unless driven by a Change Parameter action. They are best for controlling display logic, metric switching, and threshold values across the whole workbook.
Dashboard Actions:
Actions are behaviour based, they fire in response to what the user does in a view rather than requiring them to find and operate a separate control. They are invisible as interface elements asthe visualisation itself becomes the control. They scale elegantly, one action can update many sheets simultaneously. They are best for creating guided analytical flows and drill down experiences.
| Feature | Filter Cards | Parameters | Dashboard Actions |
|---|---|---|---|
| Requires separate control | Yes | Yes | No |
| Updates multiple sheets | One at a time | Yes | Yes |
| Triggered by chart interaction | No | No | Yes |
| Visible on dashboard | Yes | Yes | No |
| Supports drill down navigation | No | No | Yes |
| Opens external URLs | No | No | Yes |
| Best for | Manual user control | Cross workbook logic | Interactive guided analysis |
Use filter cards when users need to freely adjust specific dimension values on their own schedule. Use parameters when a single value needs to drive calculated logic across many sheets. Use dashboard actions when the interaction itself e.g. clicking a mark, selecting a region, hovering over a data point should be the trigger.
Common Limitations of Dashboard Actions
Actions Cannot Fire on Calculated Field Values in All Cases
Filter actions pass field values from the source view to the target view as filter conditions. If the bridging field is a calculated field that exists only in the source sheet and not in the target sheet, the filter has nothing to apply to. Always use dimensions that exist natively in both the source and target sheets as the filter bridge, or use shared sets and parameters as intermediaries.
Hover Actions Can Interfere With Tooltips
When a Highlight or Filter action is set to fire on Hover, it competes with the standard Tableau tooltip that also appears on hover. On dashboards with many closely spaced marks this can cause flickering or unintended triggering as the cursor moves across the view. Use Select trigger for dense or complex views to give users deliberate control.
URL Actions Require Valid and Accessible URLs
A URL action is only as useful as the destination URL. If the URL requires authentication that the user does not have, or if the field value used to build the URL contains special characters that break URL formatting, the action will fail silently or open an error page. Always test URL actions with representative field values including those with spaces, symbols, and long strings.
Change Set Actions Require Published Sets
For Change Set Value actions to work in Tableau Server or Tableau Online published workbooks, the set must be defined in the workbook before publishing. You cannot create new sets dynamically at runtime. Plan your set structure during workbook design.
Go to Sheet Actions Do Not Preserve Scroll Position
When a Go to Sheet action navigates to a new dashboard, the destination opens at the top of the page regardless of where the user was on the origin dashboard. For long dashboards this can disorient users. Keep destination dashboards concise and design them to show the most relevant content at the top of the view.
Actions Apply to Entire Sheets Not Individual Marks by Type
You cannot configure an action to fire only when a specific type of mark is clicked within a sheet. If the source sheet contains both bars and a reference line, clicking anywhere in that view triggers the action. Design your source sheets to contain only the interactive elements you intend to be triggers, and use separate sheets for annotations or reference content.
Common Mistakes to Avoid
Setting all actions to fire on Select without thinking about clearing behaviour. If you leave clearing behaviour as Exclude All Values, clicking empty space after a selection makes all target views go blank. This confuses users who think the dashboard has broken. Always set clearing behaviour deliberately — Show All Values is the safest default for most use cases.
Using too many simultaneous actions on one source sheet. If clicking one mark triggers five different actions across five different sheets simultaneously, the dashboard can feel overwhelming and slow. Prioritise which views are most important to update on interaction and limit simultaneous action responses to two or three targets.
Not naming actions descriptively. Tableau names actions Action 1, Action 2, Action 3 by default. When you have eight actions configured and need to debug why something is not working, unnamed actions are nearly impossible to diagnose quickly. Name every action with its source, trigger, and target in the name field from the start.
Forgetting that filter actions require a shared field between source and target. If you use Category as the filter bridge but one target sheet does not include Category in its data source, the filter silently does nothing on that sheet. Verify that every target sheet contains the bridging field before configuring the action.
Building navigation with Go to Sheet actions without a Back button. When a user drills from an overview dashboard to a detail dashboard using a Go to Sheet action, they need a way back. Add a Navigation button or a second Go to Sheet action pointing back to the overview. Without this users get stranded on the detail dashboard with no obvious return path.
Using Hover trigger on mobile optimised dashboards. Hover does not exist as a concept on touchscreens. Any action configured to fire on Hover will never fire for users on tablets or phones. Use Select trigger for any dashboard intended for mobile consumption.
Dashboard Actions Cheat Sheet
| Task | Action Type | Trigger |
|---|---|---|
| Click chart to filter another chart | Filter | Select |
| Hover to preview related data | Highlight | Hover |
| Click to open CRM or external page | URL | Select |
| Click overview to open detail dashboard | Go to Sheet | Select |
| Click metric name to switch all charts | Change Parameter | Select |
| Click to build custom comparison group | Change Set Values | Select |
| Right click for optional filter | Filter | Menu |
| Combine filter and navigation | Filter + Go to Sheet | Select (both) |
| Cross dashboard highlight | Highlight | Hover or Select |
| Pass region context to detail view | Filter + Go to Sheet | Select (both) |
Tableau Dashboard Actions transform passive charts into active analytical tools — turning every mark, bar, dot, and row into a potential control that drives the rest of the dashboard.
Here is the simplest summary of everything we covered:
Filter actions connect views so that selecting data in one chart filters other charts to match. Highlight actions draw attention to related marks across views without removing any data from sight. URL actions bridge Tableau and external systems by building dynamic links from field values. Go to Sheet actions enable drill down navigation between overview and detail dashboards. Change Parameter actions let visualisations themselves serve as dynamic metric selectors. Change Set Values actions give users the power to define their own comparison groups at runtime.
All six action types are configured through Dashboard menu → Actions → Add Action. Every action needs a source sheet, a trigger, and a target. Clearing behaviour controls what happens when the user deselects and is one of the most important settings to get right.
Start with a single Filter action between two sheets on the same dashboard. Once that click to filter interaction feels natural, add a Highlight action for hover based exploration. Then combine a Go to Sheet with a Filter action to build your first drill down flow. From that point, dashboard actions become the foundation of every interactive Tableau workbook you build.
FAQs
What are dashboard actions in Tableau?
Dashboard actions are interactive behaviours that connect visualisations so that interacting with one view by clicking, hovering, or selecting drives a response in another view, navigates to another dashboard, or opens an external URL.
How do I add a dashboard action in Tableau?
Open your dashboard, go to the Dashboard menu at the top of the screen, click Actions, then click Add Action and choose the action type you want to configure.
What is the difference between a Filter action and a Highlight action?
A Filter action removes non matching data from target views so only the selected values remain visible. A Highlight action keeps all data visible but dims non matching marks while emphasising matching ones across target views.
Can one dashboard action update multiple sheets at the same time?
Yes. When configuring any action you can select multiple target sheets under the Target section. All selected target sheets will respond simultaneously when the action fires.
Why is my filter action not working on a target sheet?
The most common cause is that the bridging field used in the action does not exist in the target sheet’s data source or is not included in that sheet’s view. Verify that the filter field is present in both the source and target sheets.
Do dashboard actions work in Tableau Public and Tableau Server?
Yes. Dashboard actions work in Tableau Desktop, Tableau Public, Tableau Server, and Tableau Cloud. The configuration is the same across all platforms. Change Set Value actions require the set to be defined in the workbook before publishing to Server or Cloud.