Skip to main content
Use the org switcher at the top of the sidebar to select a client — it scopes all navigation, content, and the Pi Agent to that organization. The selected org is pinned per browser tab, so keep one client per tab and open a second tab for a second client rather than toggling back and forth. Start a fresh Pi chat, in the right org, for each client, since a chat is bound to the org you had selected when you started it. Get this reflex right and you’ll never publish to the wrong site or ask Pi about the wrong company. See Driving Pi Agent well.

​
Switch client

The org switcher sits at the top of the sidebar. It lists every organization you’re a member of. Selecting one scopes all navigation, content, and the Pi Agent to that client.

​
Per-tab pinning (why tabs don’t bleed)

The selected org is pinned per browser tab. So you can have Client A open in one tab and Client B in another, and switching one won’t silently change the other. This prevents the classic mistake of “I switched clients in another tab, then published to the wrong one here.” The rule of thumb is one client per tab. When you need two clients at once, open a second tab and switch it there rather than toggling back and forth within one tab.

​
One client per Pi conversation

A Pi chat is scoped to the org you had selected when you started it, so don’t try to handle two clients in one thread. Start a fresh chat, in the right org, for each client. See Driving Pi Agent well.

​
Owner vs member views

You, the operator, see the full toolset. A client logging into their own org sees a reduced, client-safe menu. If you’re screen-sharing and they can’t find something you’re describing, that’s why: they’re on the member view. Next: Driving Pi Agent well