Share links and chat content now follow who can open the chat

When you make a chat private, narrow it to a named audience, or delete a project, you expect the content that came out of it to close behind you. Four reads now check the viewer's access to the chat or project first.

Public chat links

Creating or regenerating a public link used to take the chat ID at face value, so someone who could create links in one project could mint a link for a chat elsewhere and read the conversation through it. You can now only create, regenerate, revoke, or check the link status for a chat you can open yourself. Anything else comes back as not found.

Chat charts and documents

Any project member could previously ask for the artifacts of any chat in the project, including chats their owner had made private, and get back titles, descriptions, and working download links. Someone who had saved those artifact IDs while a chat was open to the project could keep minting fresh download links after you narrowed it. Both the artifact list and the download links now serve only chats you are allowed to open.

Follow-up suggestions on a paired device

Follow-up suggestions quote the assistant's answer, and the paired-device route served them without checking the chat behind them, so a chat in another project of the same organization would answer. Suggestions now go through the same chat check the web app already applied.

Guest links after a project delete

Deleting a project left guest share links for its live sessions working, with the transcript, the summary, the link preview title, and the running event stream still open to anyone holding the URL. Deleting a project now removes those sessions and closes their guest links.

Nothing changes in how you share. Links you create keep working for the people you meant them for, and the ones you close stay closed.