Notion changed its API changelog

===================================================================
--- before
+++ after
@@ -11,8 +11,14 @@
 ATOMIC BATCHED CONTENT UPDATES IN NOTION MCP
 
 notion-update-page calls that use the update_content command now apply every content-changing replacement in the batch or none of them. Previously, when one old_str matched no page content and another one in the same call did, the matching replacements were saved and the call returned success — so a batch that removed content in one operation and reinserted it in another could drop that content. These calls now return a validation_error naming the old_str that wasn’t found, and the page is left unchanged. Operations whose old_str and new_str are identical are ignored without checking for a match. See Supported tools for the tool’s matching rules.old_str must also be a non-empty string. Empty values were previously ignored, which silently skipped the replacement; they now fail validation on both notion-update-page and Update a page’s content as markdown.
 
+August 24, 2026
+
+ADMIN API REFERENCE FOR USERS AND PERMISSION GROUPS
+
+The Admin API reference now covers listing workspace users and managing workspace permission groups and direct memberships. These endpoints require the new user:read, permission-group:read, and permission-group:write scopes and are available to eligible Enterprise organizations.
+
 August 20, 2026
 
 NOTION AGENT APIS IN PUBLIC BETA