> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/tutorials/interactions/open-records-in-console-tabs-and-subtabs.md).

# Open records in Console tabs and subtabs

In a Lightning Console app, open the opportunity a rep clicks in a labeled subtab next to the flow, so the pipeline list stays one click away.

A sales rep works their pipeline in a Lightning Console app, with the flow open in a tab of its own. Clicking **View** on a row should not replace the list. With **Open Console Tab** on, the opportunity opens in a subtab labeled with its name, and the flow stays in the tab next to it.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FKNEilnmtPO4gryU5xaun%2Fnavigate-open-records-in-console-tabs-and-subtabs-result.png?alt=media" alt="Sales Console with the opportunity open in a subtab next to the tab that holds the flow"><figcaption><p>The opportunity opens in a labeled subtab and the flow stays in its tab.</p></figcaption></figure>

## Before you start

* A Lightning Console app, such as Sales Console, where the flow runs. Outside a console app the click does nothing.
* A Data Table with a **View** row action wired to **Navigate**, **Record Page**, `{{Record.Id}}`. [Open a record from a Data Table row](https://docs.avonnicomponents.com/flow/tutorials/interactions/how-to-create-an-interaction-to-a-record-page.md) builds it.

## Steps

{% stepper %}
{% step %}

### Turn on Open Console Tab

1. Select the Data Table, click **Open Component Builder** and open the **View** interaction in the **Interactions** tab.
2. Further down the panel, turn on **Open Console Tab**.
3. Turn on **Open Console Sub Tab** to open the record under the current tab instead of in a new tab of its own.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FhgpS7CUWwAjzeqTqv4Lm%2Fnavigate-open-records-in-console-tabs-and-subtabs-toggles.png?alt=media" alt="Open Console Tab and Open Console Sub Tab turned on in the Navigate interaction, with Focus on" width="320"><figcaption><p>Open Console Sub Tab opens the record under the tab that holds the flow.</p></figcaption></figure>
{% endstep %}

{% step %}

### Choose the parent tab

Leave **Parent Tab Id** empty: the subtab opens under the tab that holds the flow. If the rep is on a subtab, it opens under that subtab's parent.

Fill **Parent Tab Id** only when you have the Id of another console tab to attach it to.
{% endstep %}

{% step %}

### Bring the tab to the front

Turn on **Focus**. It is off by default, and then the tab opens in the background while the rep stays on the flow.

**Override Navigation Rules** opens the record in a tab even when the app's navigation rules say otherwise. It applies to tabs, not to subtabs.
{% endstep %}

{% step %}

### Label the tab

* **Label**: pick **Record: Name** in the list (it stands for `{{Record.Name}}`), so the tab reads the opportunity's name and not the object name.
* **Icon Name**: leave the source on **Custom** and type `standard:opportunity`.
* **Icon Alternative Text**: leave the source on **Custom** and type `Opportunity`, read by screen readers.

The group also has its own **Record Id** and **Url** fields. Leave them empty here: the record comes from the Record Page settings above.

All the console fields are listed in [Navigate: Open in a Lightning Console tab](https://docs.avonnicomponents.com/flow/component-builder/interactions-panel/navigate.md#open-in-a-console-tab).
{% endstep %}

{% step %}

### Save and test

Save the flow and add it to a page of the console app. Click **View** on a row: a subtab opens under the flow's tab, in front, with the opportunity's name and the opportunity icon. Click the flow's tab: the flow and its table are where the rep left them.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
To close, refresh or relabel a console tab from the flow, use the [Control Console Tab](https://docs.avonnicomponents.com/flow/component-builder/interactions-panel/control-console-tab.md) interaction.
{% endhint %}

## Troubleshooting

<details>

<summary>Nothing happens on click</summary>

The flow does not run in a Lightning Console app. **Open Console Tab** needs one and has no fallback. Turn it off when the flow also runs in a standard app.

</details>

<details>

<summary>The tab opens but the rep stays on the flow</summary>

**Focus** is off, so the tab opens in the background. Turn on **Focus**.

</details>

## Related tutorials

* [Open a record from a Data Table row](https://docs.avonnicomponents.com/flow/tutorials/interactions/how-to-create-an-interaction-to-a-record-page.md): the View and Edit actions this page starts from.
* [Send users to an external site or another Lightning page](https://docs.avonnicomponents.com/flow/tutorials/interactions/send-users-to-an-external-site-or-another-lightning-page.md): open a website or an app tab from the header.
* [How to setup an Open Flow Panel interaction](https://docs.avonnicomponents.com/flow/tutorials/interactions/how-to-setup-an-open-flow-panel-interaction.md): show a second flow next to the table instead.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avonnicomponents.com/flow/tutorials/interactions/open-records-in-console-tabs-and-subtabs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
