Set a chat to Project, Restricted, or Private
A pill in the chat header now shows who can see the chat and opens the visibility modal in one click, and the API lets you set visibility, manage a chat's audience, and handle project membership.
You open a chat and want to know who else can read it. Until now the header only showed that when the chat was narrowed, so a chat shared with the whole project gave you nothing to look at and nowhere to click.
Visibility pill in the header
Every chat header now carries a pill showing the current level with a matching icon: a globe for Project, a users icon for Restricted, a lock for Private. Click it and the chat visibility modal opens, whatever the current state. If you cannot change the chat's visibility, you still see the pill as a label.
Three access levels
Project means every project member can read the chat. Restricted means the owner plus the people you name. Private means the owner alone. Moving to Restricted keeps the audience the chat already had; moving to Project or Private clears it.
Chat audience over the API
The API now lets you set a chat's visibility, then list, add, and remove the people in a restricted chat's audience by email. Audience membership only narrows who can read that chat and never grants project access, and the email has to belong to a current project member, so someone you just invited becomes addable once they accept.
Public share links
You can create, read, and revoke a chat's public share link through the API, including regenerating it when you want the old link to stop working.
Project commands
Projects gained create, rename, member listing, and invitation management over the API, so the audience you assign to a restricted chat and the project it lives in can both be managed from the same place.
Open any chat and click the pill in the header to check or change who can see it.