Teammates keep their files, act in bulk

Two things a teammate should have been able to do and could not: reopen a file it saved, and act on a list of people in one step. “Message everyone tagged open house, then tag them and schedule a check-in” now works end to end.

Files a teammate can come back to

• List, read and edit — a teammate can browse its own folder, open a file by name and edit it in place. Before this, a saved file could never be reopened.
• Its own folder only — the server enforces the boundary on every read and edit; it is not something the teammate could be talked out of.
• Downloaded content stays fenced — anything a teammate saved from the web keeps its untrusted label when read back, so a downloaded page cannot smuggle instructions in through a file.
• One switch — Workspace files in the teammate’s Capabilities panel governs the whole bundle, on by default.

Lists in one step

• Tag, note and schedule accept a list — up to 100 Contacts per action. A run that used to take about 80 separate steps now takes three, and finishes in seconds.
• All or nothing — a batch that fails partway is rolled back, so a retry cannot double-post notes or create duplicate reminders that message real people twice.
• Bulk sends hand back their audience — the teammate knows exactly which Contacts were reached, so a follow-up tag lands on those people and no one else.
• Scheduling many asks first — recurring check-ins for a list of Contacts need an explicit confirmation with the count read back. Single-contact scheduling is unchanged.
• A Contact you cannot edit is reported per Contact — the rest of the batch still applies.