# Browsing namespaces

**URL:** https://community.pinecone.io/t/browsing-namespaces/7935
**Category:** Support
**Tags:** namespace
**Created:** [May 5, 2025, 4:29pm UTC](https://community.pinecone.io/t/browsing-namespaces/7935 "2025-05-05T16:29:57Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![outbound](https://sea2.discourse-cdn.com/flex020/user_avatar/community.pinecone.io/outbound/32/4194_2.png) [@outbound](https://community.pinecone.io/u/outbound)
#### Post date: [May 5, 2025, 4:29pm UTC](https://community.pinecone.io/t/browsing-namespaces/7935/1 "2025-05-05T16:29:57Z")

</div>

Hi there,

I’m using the pinecone web browser to check the records in my index. However I can only browse one namespace - the first one that’s created.

If I switch to a second namespace, using the pulldown, it does not show any hits. Even though I see the second namespace has records, when I check the Namespaces tab.

How do I browse records in a different namespace in the same index?

I want to do this to ensure that the records have been properly upserted in the second namespace.

Not a developer, but technically inclined.

TIA

---

<div class="post-metadata">

### Author: ![zeke](https://sea2.discourse-cdn.com/flex020/user_avatar/community.pinecone.io/zeke/32/4257_2.png) [@zeke](https://community.pinecone.io/u/zeke)
#### Post date: [May 6, 2025, 1:02pm UTC](https://community.pinecone.io/t/browsing-namespaces/7935/2 "2025-05-06T13:02:32Z")

</div>

Hi @outbound, thanks for your post! After changing the namespace using the dropdown, are you running an operation? After changing the namespace, the **Search** button should change colors and become active. Upon pressing it, the records in your newly selected namespace should populate.

 ![Screenshot 2025-05-06 at 8.55.56 AM](https://us1.discourse-cdn.com/flex020/uploads/pinecone/original/2X/7/72eac5f7653ad8e05de62b3026a9838f140be1f1.png)

Generally, we encourage all users to note that the console is intended to be a playground for our APIs — all data representations in the index detail view result from a direct API call. Therefore, when you change a parameter, you’ll need to trigger a new operation to refresh the displayed data.
