1Password SaaS Manager

by 1Password SaaS Manager Team
1Password SaaS Manager Team
Updated to #1358 on
SaaS Manager
 
1Password SaaS Manager #1358

New

  • AI Spend and Consumption: You can now edit API key details directly from the dashboard. Table columns have also been adjusted to make usage data easier to scan.
  • Claude Console: SaaS Manager now imports consumption data from Claude Console, including message and Claude Code usage.
  • Workflows: Custom person fields can now trigger workflows, giving teams more options for automating actions based on people data.
  • Lark: The Lark “Frozen” status is now available as a dedicated person field. This makes it easier to distinguish temporary leave from suspension and use the status in workflows.
  • BambooHR: Added custom-field mapping support for Pathify, including the BambooHR “Division” field.

Fixed

  • BambooHR: Improved custom-field handling during the Datasets API migration. SaaS Manager now provides a clearer warning when it can’t access the employee dataset.
  • WPS Office: Provisioning now sends an invitation after creating a user. It also handles usernames that contain characters WPS doesn’t support.
  • SAP Ariba: Fixed an issue where contract imports didn’t use the selected import date range correctly.
  • Claude Console: Fixed incorrect cache write token counts and duplicate usage records for Claude Code API keys.
  • OpenAI Platform: Added clearer reconnect errors when an administrator key belongs to a personal organization instead of an enterprise organization.
  • Contracts: Fixed an issue where batch processing could record a per-period value as the total contract value.
  • Similar apps: Fixed app matching so exact-name matches are considered correctly.
  • App labels: Fixed the “Part of” label so it shows the correct instance.
  • AI spend alerts: Fixed an issue that could create duplicate spike alerts during the alert cooldown period. The cooldown now suppresses repeated alerts as expected.
  • Integration jobs: Fixed an issue where cancelling a job could leave the integration stuck in a loading state. Scheduled scans can now run normally after a cancellation.