November 2, 2026
48 changes across 6 repo s
New
- Sales commentary tools available via MCP #184 Four new MCP tools — find, get, search, and report usage for sales commentary — are now available to users with the sales commentary entitlement. They surface automatically once the entitlement is active; no configuration is required.
- Document table search, export, reprocess, and delete now live in the provider portal #385 The provider content document table now supports filename search, status filtering, bulk export, bulk delete, and bulk reprocess, all connected to the backend. Search and filter selections are preserved in the URL, and export completion is delivered through the existing notification system.
- Documentation share-link validation endpoint #735 A new endpoint allows documentation sites to validate a share-link token on page load, enabling guest access to gated documentation without requiring an account. Invalid, expired, and revoked tokens all return the same response to prevent probing.
Improvements
- Bulk CSV user upload now reports all validation errors at once #81 When uploading a CSV to update users in bulk, all row-level errors — including duplicate emails and missing fields — are now shown together in a scrollable list rather than stopping at the first problem.
- Org admin API key visibility restored for same-organization users #768 Organization admins can once again view API keys for users within their own organization in the dashboard and Developer Platform, consistent with the existing v2 behavior. Access remains limited to the admin’s own organization.
- MCP server now rejects unrecognized arguments on strict tools #184 For research and sales commentary search and find tools, the MCP server now returns a clear validation error when an unrecognized parameter is passed, rather than silently ignoring it. Other tools remain permissive for compatibility with third-party clients.
- Client search type filter now correctly matches affiliated clients #958 Combining a name or email search with a client type filter now returns affiliated clients whose organization matches the selected type, in addition to unaffiliated clients.
- Impersonation sessions are now more precisely tracked #954, #962 Each support staff impersonation session now carries a unique identifier, so replaying an old session token after a session ends is no longer possible. Audit records now also include the impersonating user’s organization for clear attribution.
- Research accessibility improvements for keyboard and screen reader users #790 The Research access lock in search filters, company documents, and the chat source picker now has a descriptive accessible label. The Research chip in the search filter popover is clickable, and Document Type and Event Type chips are reachable and activatable by keyboard.
Fixes
- Organization activity log search now matches only visible information #752 The organization-level token activity log now consistently shows all chat entries as “Chat [id]” in both the UI and CSV export, and search matches only what is displayed. Individual users’ own activity views continue to show and search full chat titles.
- Organization admins can now access token usage and analytics as expected #759 Users promoted to organization admin through the dashboard now have full access to their organization’s token usage and analytics views, consistent with how the platform displays their role.
- API key sync now reaches users with mixed-case email addresses #757, #761 Users whose account email contains uppercase letters now receive updated API keys correctly during identity synchronization, resolving an issue where the case-sensitive account lookup did not find their record.
- XML preview error messages now reflect the actual API responses #405 The XML preview modal in the provider portal now shows accurate error messages for unavailable, unsupported, or temporarily inaccessible files, replacing several message branches that were never reachable.
- Validation error responses no longer expose field-level detail to unauthenticated callers #766 Unauthenticated API requests that fail validation now receive a generic response instead of a detailed per-field error breakdown. Authenticated users continue to see structured validation feedback.