> For the complete documentation index, see [llms.txt](https://docs.openbuild.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbuild.io/working-with-the-framework/navigation/navigation-through-custom-states.md).
# Navigation through custom states
You can use custom states to navigate between tab menus for example. It's a perfect use case for simple sub-navigation in your groups.
When a tab is clicked, you can set a custom state of 'show' to the parent section or group. This 'show' is simply a text field. A custom state is arbitrary data that you can load into a page or element and use without having to store it in the database.
Setting a value to the 'show' state
Conditional on the UI element. The element is invisible on page load by default.
Here is a simplified diagram of what we're trying to accomplish. Let's say we have 3 tabs: Account, Billing, and Notifications.
Each time we click any of the tabs we set the custom state to the tab we clicked (eg. Account).
Each of the 3 tabs have a group with all the content inside. These are all hidden by default and have a condition that looks at the custom state.
When the custom state corresponds with one of the hidden groups, it shows.
