September 28, 2026

43 changes across 6 repo s

New

  • Product seat usage and per-user research access on the developer portal homepage #64 The homepage now shows who can use each product — admins see org-wide seat counts with a link to the filtered users table, and members see their own access. The users table gains a Product Access column and per-product filters.
  • Document library search and type filtering for providers #889 The provider content listing can now be filtered by document type and searched by title, including typo-tolerant matching. Results return only documents matching the specified criteria.
  • Readership metrics export via the public API #873 A new public API endpoint lets integrators export readership metrics data programmatically.
  • Hedgineer integration enabled for Palestra Capital MCP authentication #132 Palestra Capital users can now authenticate to the Aiera MCP through the Hedgineer platform.
  • First usage month added to token usage summary responses #674 Both the organization and user token usage summary endpoints now include a first_usage_month field (YYYY-MM format), so clients can bound historical lookback windows without over-fetching monthly series data.
  • Per-person address support during batch onboarding #651 Each person in an onboarding batch now receives the address from their own worksheet row. The organization address is used only as a fallback when a person’s row carries none. Batches with unrecognizable country values are now rejected up front with a clear error naming the offending entries.
  • Organization consolidation for admins #671 A new admin-only endpoint allows multiple organizations to be merged into a single surviving organization. Each folded organization can optionally become a named department, and the operation is previewable as a dry run before any data is written.

Improvements

  • Workflow output notification preference hidden for users without workflow access #743 The “Workflow output” row in Notification Settings is now shown only to users with workflow access, matching the visibility rules applied to all other workflow surfaces.
  • Org creation script now rolls back fully on failure #879 All steps of the org creation process are wrapped in a single transaction, so a failure at any step leaves no partial records. An interactive quit-confirmation prompt is also shown when the process is interrupted.

Fixes

  • Company documents now display publish date only #744 Document dates in the doc viewer, drilldown, and global search results now reflect the publication date exclusively. Documents without a publish date show no date rather than an internal processing timestamp.
  • Dashboard access now correctly determined by seat type #745 Audio playback, live transcripts, and the chat prompt now gate correctly on whether a user holds a Dashboard seat. Users with both an MCP and a Dashboard seat are no longer incorrectly locked out of dashboard features.
  • Developer portal renders correctly in Safari and WebKit-based browsers #69 The developer portal now loads fully in Safari and all WebKit-based browsers when running in local development mode.
  • SFTP bulk feed directories now list content correctly #885 SFTP feed directory listings now resolve to the correct storage paths, so bulk feed folders display their expected contents rather than appearing empty.
  • Sales contact email entered at client creation is now saved correctly #868 A sales contact email typed while creating a new client is now preserved. Previously it was overwritten by the linked organization’s default.
  • Research provider routes now respond correctly for all account types #659 Routes backed by entitlement checks now return appropriate responses for all user account types, including machine and service accounts.
  • Vendor authentication key updates now take effect immediately #676 Updating a vendor’s key material now correctly invalidates the cached credentials so the new keys are used right away.
  • Invalid field types in onboarding requests now return a clear validation error #676 Submitting non-string values for fields such as address or email in onboarding requests now returns a field-specific 422 validation error rather than a 500.

← All updates