Release Notes

Executive reporting comes to Engineering Insights

This release centers on Custom Views, a new way to build and share company-level executive reports inside Engineering Insights. You can compose a report from live OKR, engineering, and capacity data, ask Bloomy to draft one from a short brief, and export the result to share with leadership. It also introduces a simpler, company-aware sign-in that starts from your work email.

What's new

Build executive reports with Custom Views

A new Custom Views tab in Engineering Insights lets you assemble shareable, company-level reports you can save, reopen, and hand to leadership.

• Compose reports from cards and rows backed by OKRs, engineering metrics, capacity and utilization, or values you enter yourself
• Compare groups side by side with a Metrics by groups view, choosing a dimension like department, team, division, or office and reading each metric per group
• Present each row as a table, KPI tile, progress bar, actual vs target, or gauge, then color-code cards and arrange them with drag and drop
• Scope any row to the right people by department, team, group, manager, employment type, or location
• Duplicate a report or start from a built-in template, set a default time range, and export to CSV or PDF

Custom Views that read consistently

Reports now hold steady regardless of what you change elsewhere in Engineering Insights.

• Each report runs on its own saved time range, so changing filters on Overview or Tech Usage no longer shifts the numbers in a report
• Column sorting on Metrics by groups cards is kept when you reopen the card settings to change which groups or metrics appear
• CSV and PDF exports now include the full Metrics by groups data, not just the card title

Ask Bloomy to build a report

Bloomy can now turn a description into a finished Custom View, so a report is one conversation away.

• Describe a report in plain language, or share a mockup, and Bloomy assembles the cards, rows, metrics, capacity, OKRs, and group comparisons
• Bloomy can create the underlying OKRs in the same flow, then hand back a one-click link to open the finished report
• Building a report through Bloomy follows the same access controls as the Custom Views builder, so only people with edit access can create one
• Bloomy can also search across your synced AI coding sessions when you ask, kept separate from in-app Bloomy chat

Sign in with your company account

Logging in now starts from your work email and routes you to the right place to sign in.

• Enter your work email on the login screen and Abloomify sends you to the correct sign-in for your organization
• Companies can connect their own single sign-on so everyone signs in through the same secure path, available first with Okta
• If single sign-on is not set up for your domain, the familiar email and password sign-in still works

Who benefits

• Engineering and product leaders: build executive reports from live OKR, engineering, and capacity data and reopen them each week without rebuilding spreadsheets
• Managers reviewing teams: compare departments, teams, and groups side by side and scope each row to the right people
• Admins: grant view or build-and-edit access to Custom Views and connect company single sign-on for the whole organization
• Anyone using Bloomy: turn a brief or mockup into a finished report and search synced AI coding sessions on request
• Everyone signing in: a simpler, company-aware login that starts from your work email

Try it

• Open Engineering Insights and select Custom Views to build or open a report
• Add cards and rows from OKRs, engineering metrics, capacity, or your own values, then export to CSV or PDF
• Ask Bloomy to draft a Custom View from a short brief or a mockup
• Set per-report access from the Custom Views and Build & Edit Custom Views permissions under Engineering Insights
• Sign in by entering your work email, and if your company uses single sign-on you will be routed automatically

Imported Rippling people are now visible, plus steadier GitHub knowledge syncs

This release brings imported Rippling employees into view inside Abloomify, lets admins run an employee sync whenever they need to, and keeps GitHub-sourced knowledge syncs steady through brief access interruptions. Teams that connected Rippling can now confirm their people and org-chart context before relying on the data. No action is required for teams that do not use Rippling or GitHub knowledge syncs.

What's new

See imported Rippling people in Abloomify

After connecting Rippling, the synced employees appear directly in the integration settings, so admins can confirm the import looks right.

• A synced employees table lists imported people inside the Rippling integration settings
• Each person carries org-chart context: department, division, team, and office
• Role context comes through too, including manager, role, career family, career track, and career level
• Teams can confirm employee data imported correctly before relying on it in Abloomify

Run a Rippling employee sync on demand

Admins can pull the latest Rippling people into Abloomify when they choose, with a connection that stays secure from setup onward.

• A manual employee sync brings the latest Rippling people into Abloomify on demand
• Reconnecting or reauthorizing Rippling completes cleanly
• The connection and employee sync run through a secure setup

More reliable GitHub knowledge syncs

GitHub-sourced knowledge syncs now recover from brief access interruptions instead of failing.

• GitHub knowledge syncs that hit a brief access interruption now recover on their own
• Valid syncs that previously stalled on a passing error now complete
• When access is genuinely changed or revoked, the sync still reports the issue clearly

Who benefits

• Admins connecting Rippling: a synced employees table to confirm imported people before relying on the data
• People and HR operations teams: org-chart context, including department, team, manager, and career level, visible in Abloomify
• IT and security reviewers: Rippling connection and employee sync run through a secure setup
• Teams using GitHub knowledge: fewer failed knowledge syncs when access is briefly interrupted

Try it

• Open Integrations and select Rippling to review the synced employees table after setup
• Trigger a manual employee sync from the Rippling integration settings to pull the latest people
• Confirm org-chart fields like department, team, and manager imported as expected
• Reconnect Rippling from Integrations if a prior setup attempt needs reauthorization

Native Rippling connection support

This release adds native Rippling connection support to Abloomify. Admins can authorize Rippling as an HR source of truth directly from Integrations, and the connection lays the groundwork for HR-driven user management. No action is required for teams that do not use Rippling.

What's new

Connect Rippling as an HR source

Admins can now connect Rippling to Abloomify from the integrations library, using Rippling's App Shop authorization.

• A new Rippling option in Integrations routes admins through Rippling's official App Shop authorization screen
• Authorization uses Rippling's approved path, so the connection stays secure from setup onward
• Connecting establishes Rippling as a source of truth for employee data in Abloomify
• Reconnecting or retrying setup keeps the integration cleanly linked, with no duplicates

Groundwork for HR-driven user management

This is the first step toward managing the employee lifecycle from Rippling data.

• Lays the foundation for automated user provisioning driven by Rippling records
• Prepares Abloomify to reflect employee changes, including offboarding, from your HR source
• Gives companies that manage employees in Rippling a cleaner path to keep Abloomify aligned

Who benefits

• Admins connecting HR systems: a direct path to authorize Rippling from Integrations
• IT and security reviewers: authorization runs through Rippling's approved App Shop path
• People and HR operations teams: groundwork for keeping Abloomify aligned with Rippling records
• Leaders planning HR automation: the first step toward HR-driven user provisioning and offboarding

Try it

• Open Integrations and select Rippling to start the connection
• Approve the connection through Rippling's App Shop authorization screen
• Confirm Rippling appears as a connected HR source in Integrations after setup

Steadier behavior for meeting RSVPs and AI-assisted matching

This release improves how meeting RSVP emails get processed and widens the conditions under which AI-assisted matching keeps running. Both changes show up as fewer dead ends in everyday workflows, with no new setup required.

What's new

Smarter recognition of meeting RSVP emails

Inbound emails that are meeting responses are recognized more reliably, even when the full message details are not readily available.

• Common meeting-response subjects like "Accepted", "Tentative", or "Declined" are recognized on their own
• A clear sense of the response carries through to downstream summaries
• Fewer meeting RSVPs slip past as unstructured noise

Steady output when meeting details are sparse

When a meeting RSVP arrives without full details, processing now produces a useful summary instead of stalling on the gap.

• A useful summary still appears when meeting details cannot be fully retrieved
• Edge cases that previously stalled on missing context now resolve cleanly
• Less manual follow-up to interpret thin RSVP messages

Broader resilience for AI-assisted matching

AI-assisted matching now stays steady across a wider set of brief service interruptions, building on the steadier path shipped earlier this month.

• More types of momentary service hiccups resolve without surfacing as failures
• Weekly digest generation benefits from the same broader coverage
• Fewer one-off interruptions for teams running AI-assisted flows at peak periods

Who benefits

• Teams whose calendars route through Abloomify: more accurate context from inbound RSVP emails
• Operations staff reviewing meeting outcomes: fewer thin summaries to chase down manually
• Leaders relying on AI-assisted insights: matching and the weekly digest keep running through more types of brief service hiccups
• IT and admins overseeing AI workflows: fewer one-off interruptions to investigate

Try it

• Review the next meeting summary or digest; RSVP context flows in more cleanly from inbound emails
• Check the weekly digest after a peak period; AI-assisted matching should continue producing results
• Continue running AI-assisted matching workflows without changes; coverage now extends to a wider set of brief service hiccups

Notion connections, sharper GitHub identity matching, clearer billing context

This release brings direct Notion workspace connections to Abloomify, sharpens how GitHub activity maps to your team, clarifies billing and subscription context for admins, and keeps AI-assisted matching steady when underlying models are briefly busy.

What's new

Connect Notion workspaces

Admins can now connect a Notion workspace to Abloomify from the integrations library.

• A new Notion option in Integrations routes admins through Notion's official authorization screen
• Reconnecting or retrying setup keeps the workspace cleanly linked, with no duplicates
• The flow is ready for the next phase of Notion-powered Bloomy knowledge experiences

Stronger GitHub identity matching

GitHub setup is steadier on retry, and identity matching now picks up more of your team from recent repository activity.

• GitHub setup completes cleanly even when admins retry or finish the flow from another browser tab
• Identity matching now draws on recent commit activity, not only pull requests and issues, for broader contributor coverage
• Edge cases that block matching for a specific repository surface more clearly for operators

Clearer billing context and quicker recovery

Admins get the most current plan and invoice details in Settings, billing and plans, plus a recoverable path when a subscription status briefly looks blocked.

• Settings, billing and plans shows the most current plan and invoice context after a subscription change
• Subscription access stays accurate around renewal and end dates
• A retry option clears a temporarily blocked status without forcing admins to reload

Steadier AI-assisted matching

AI-assisted matching and the weekly digest keep running when underlying models are briefly busy or unavailable.

• AI-powered matching keeps running when an underlying model is briefly busy or unavailable
• Weekly digest generation benefits from the same steadier path

Who benefits

• Admins connecting Notion: a smoother setup path that completes cleanly the first time
• Admins managing GitHub: fewer interruptions when setup runs across multiple browser tabs
• Leaders relying on GitHub insights: broader contributor coverage drawn from recent activity
• Billing owners: clearer plan and invoice details, with a retry path after recent billing changes
• Teams using AI-powered automation: fewer interruptions when underlying models are briefly busy

Try it

• Connect a Notion workspace from Integrations and approve the content Abloomify can see
• Reconnect GitHub from Integrations if a prior setup attempt was interrupted
• Open Settings, billing and plans to review current subscription context after a billing change
• Use the retry action on a temporarily blocked status instead of reloading the page
• Continue running AI-assisted matching and weekly digest workflows; the path stays steady when models are briefly busy

Capacity trends and smarter Bloomy options

This release makes Usage Insights more useful for capacity planning and gives Bloomy users access to a refreshed model catalog. Teams also get steadier meeting transcript imports from Google Calendar recordings.

What's new

Capacity utilization trends

Managers can now open a deeper capacity view from Usage Insights to understand how utilization changes over time.

• See capacity patterns across the selected reporting range
• Spot workload changes before they become team health issues
• Review capacity with clearer context for planning discussions

Weekday focus and productivity comparisons

Usage Insights now helps teams compare weekday patterns for focus and productivity within the selected range.

• Identify which days carry heavier or lighter focus patterns
• Understand how meeting distribution affects productivity signals
• Support better weekly planning with clearer activity context

GPT-5.5 in Bloomy

Bloomy's model catalog is refreshed so eligible deployments can choose GPT-5.5 where it is available.

• Model options stay current for admins and power users
• Deprecated choices are removed from the catalog
• Selection guidance is cleaner when choosing a Bloomy model

More reliable Google Calendar recording imports

Meeting transcript ingestion is improved for recordings connected through Google Calendar.

• Fewer failed or empty transcript pulls from supported calendar recording flows
• Better coverage for historical meeting review
• More dependable context when teams rely on recorded meetings

Who benefits

• Leaders reviewing capacity: get a clearer read on workload and utilization movement
• Managers planning the week: compare focus and productivity patterns by weekday
• Bloomy admins and power users: see a cleaner, more current model list
• Teams using meeting transcripts: get more reliable context from Google Calendar recordings

Try it

• Open Usage Insights and review the capacity section
• Use the trend view to compare utilization movement over time
• Check weekday focus and productivity patterns for the selected range
• Review Bloomy's model selector if your workspace exposes GPT-5.5