# Connector views inside a chat

When a workspace connector provides its own view, GPTree can show it inside the reply after you approve the action. The view is sealed off from your account and can read but never change anything on its own.

Some connectors can do more than return text. They can supply their own view of the result: a board, a list you can filter, a small dashboard. Where a connector in your workspace provides one, GPTree can show it inside the assistant's reply.

## How it works

1. In a conversation that belongs to a workspace, you ask for something the workspace's connector can do, naming the connector or the thing it manages.
2. The assistant proposes the action. Nothing runs yet: you see an approval card that names the action.
3. You approve it. The connector runs, the assistant gets the result, and if the connector supplied a view, it appears in the reply.

The view sits in a card tagged "From" followed by the connector's name, so it is always clear that this part of the reply comes from the connector and was not written by GPTree or the assistant.

## You approve first, every time

In chat, a connector action never runs on the assistant's say-so. Each one waits for your approval, including actions the connector describes as read-only.

## What the view itself can do

A view is the connector's own code, so GPTree keeps it in a sealed frame. It cannot see your GPTree account or your conversations, and it can make web requests only to the addresses the connector declared. These rules do not close every route a browser offers, so do not type passwords or other secrets into a view.

Inside that frame a view can refresh itself by calling tools of its own connector, with one firm limit: only tools the connector marks as read-only. A view cannot make a change by itself. Anything that changes something goes back through the chat and its approval card.

A view can also suggest a message, which is placed in your message box for you to send or discard, and ask to open a link, which GPTree confirms with you first.

## Who can use it

Connector tools are offered in a conversation only when the conversation belongs to the workspace that owns the connector, and you are a member of that workspace. Someone a conversation is shared with can see a view that is already in it, but cannot operate the connector through it unless they are a member too.

## What is kept in the conversation

The reply keeps one line of text naming the connector. That line is what appears on shared links, in Compare, on the Merge Board and in exports. The live view is not included there.

## Availability

Connector views need a workspace with a connector that provides views, and a plan that includes workspace connectors and visuals in chat.
