Keep your content and credentials inside your own organization
Chief now checks ownership before it exports a deck, deletes integration credentials, saves a live transcript, or shows follow-up suggestions.
You share one Chief workspace with your team, and your organization sits alongside others. Several places where Chief handled content by reference now confirm the thing belongs to you before acting on it.
Google Slides exports
An export request could point at a presentation belonging to another organization and pull its slide text, titles and speaker notes into a deck in your own Google account. Chief now refuses any export of a presentation your organization does not own, and you get a not-found response instead.
Integration disconnects
Disconnecting Slack or Notion cleared stored credentials for whatever integration the request named, including one in another organization, which left that organization with a connection that failed on every call. Chief now clears credentials only when it removed one of your own connections.
Live session transcripts
A paired device could name where its transcript should be saved, so a meeting could stop saving while every save looked successful, or land on top of another session's transcript. Chief now writes each transcript to the place the session itself records, which is the same place you read it back from.
Follow-up suggestions
Follow-up suggestions quote the answer they came from, and anyone signed in to your organization could read them for any message, including chats in projects they are not part of. Opening suggestions now takes the same access as opening the chat.
Account status on sign-in
An account flagged for deletion, abuse or inactivity returned to good standing the next time that person signed in. Those accounts now stay in the state an administrator set, and only an administrator moves them out of it.
You do not need to change anything. If a disconnect reports that credentials could not be cleaned up, contact support rather than retrying.