Surfaces answer to the conversation

A surface is a tool view associated with a channel. Docs shows documents, Project shows mounted files and Review shows proposed changes. The conversation explains the work; a surface lets you inspect the object under discussion.

Open the relevant view #

A link in a message can point to a document, issue or proposed change. Follow it to inspect the object itself. A message describing an edit does not establish that the edit has saved, and a link to a pull request does not mean its checks have passed.

Available surfaces open in workbench tabs. Their availability depends on the channel and the tools the application offers. A planned surface name does not establish an available tool. The surface references describe the controls and limits for each view.

Keep the discussion with the work #

You can inspect a surface while participating in the channel conversation. Use the pane controls to give the conversation or surface more space when those controls are available. Changing the layout changes what you see; it does not complete a task or change an object’s permissions.

Decisions recorded in an issue, document or pull request have their own context. Explain an outcome in the conversation when other participants need it. The application does not promise that every action in another tool becomes a conversation message.

Check the result #

A surface can show loading, access and failure states independently of the conversation. Earlier content can remain visible after a refresh fails. Read the view’s status before treating the displayed result as current.

A document link still needs document access. A repository view still needs repository access. Opening a surface does not grant those permissions.